Ice’s Falcon BMS Profile Updated for BMS 4.35
-
With Helios installed you can edit any profile yourself. Read the whole thread copying modifying only parts of the profile has already intensively discussed. No need to start that over again
Gesendet von meinem SM-G930F mit Tapatalk
Thks Oak
-
Hi Oak,
Is there any way to run and old version of Helios, which currently has my personalised profile on it, along side, in parallel, with the new version of Helios and you 4.35 profile?
Why do I ask? I would like to transition from mine (old) version and profile to your (new 4.35) version which is a fantastic leap forward.
Why Transition? I have my profile, using MFDE, running across 5 touch screens, so its not a simple matter as it would be if it was just 1 touch screen and to be honest I could not fly very effectively without HELIOS.
Anyway - is there any way to run both at least in the short term?
Ironman.
-
Linknet
I have been flying DCS with CZ’s Helios profiles for some years. While I used to fly BMS, I stopped several years ago. Out of curiosity, I decided to see what has been created by Helios profile makers with the latest version of BMS.
When I found your site, I loved what you did to improve Ice’s old profile and immediately installed your profile and BMS. Everything seems to be working OK, but I do have some questions on the key file kerfuffle. The issue of key files in BMS seems to be a little more confusing than in DCS.So here are my questions:
First, my basic setup:
Warthog stick and throttle (with a Virpil stick base so no target files work)
TM MFD’s but I probably will not use them as I prefer the Helios profile
CH rudder pedalsSecond, my questions:
In your readme file, you state:
Falcon BMS 4.35 Installation
3. Depending on which HOTAS profile you intend to use copy the relevant keyfile from the Setup \FalconBMS Keyfiles folders to the Falcon BMS 4.35\User\Config\ folder.
4. Load and save the chosen keyfile in Falcon BMS 4.35 Setup.Which key files are you referring to? In the BMS folder, under 01 Input Devices>03 HOTAS setup>TM Warthog there is a file “BMS-Basic TM Warthog.key.” Is this the correct one?
Next, in Helios, in the Falcon setup, the only Falcon version allowed is BMS 4.34. Is that ok?
In the Falcon key callbacks>key file, I put "E:\Falcon BMS 4.35\User\Config\BMS - Full. Key” Is that ok?Am I correct that the key profiles for what is used for the Falcon BMS 4.35 Setup in the game does not have to be the same as the callbacks key file in Helios?
Two other minor issues. How does the new anti-skid switch work? I cannot seem to find the button for it under the label. In your Rotary Switch Touch Zones, you have a picture of the Aux Comm panel. I could not find it the profile.Once I get the above sorted out, I will then try to understand the issues with your stuff and the Alternative Launcher, but that is for another day.
-
Linknet
So here are my questions:
First, my basic setup:
Warthog stick and throttle (with a Virpil stick base so no target files work)
TM MFD’s but I probably will not use them as I prefer the Helios profile
CH rudder pedalsSecond, my questions:
In your readme file, you state:
Falcon BMS 4.35 Installation
3. Depending on which HOTAS profile you intend to use copy the relevant keyfile from the Setup \FalconBMS Keyfiles folders to the Falcon BMS 4.35\User\Config\ folder.
4. Load and save the chosen keyfile in Falcon BMS 4.35 Setup.Which key files are you referring to? In the BMS folder, under 01 Input Devices>03 HOTAS setup>TM Warthog there is a file “BMS-Basic TM Warthog.key.” Is this the correct one?
Next, in Helios, in the Falcon setup, the only Falcon version allowed is BMS 4.34. Is that ok?
In the Falcon key callbacks>key file, I put "E:\Falcon BMS 4.35\User\Config\BMS - Full. Key” Is that ok?Am I correct that the key profiles for what is used for the Falcon BMS 4.35 Setup in the game does not have to be the same as the callbacks key file in Helios?
Two other minor issues. How does the new anti-skid switch work? I cannot seem to find the button for it under the label. In your Rotary Switch Touch Zones, you have a picture of the Aux Comm panel. I could not find it the profile.Once I get the above sorted out, I will then try to understand the issues with your stuff and the Alternative Launcher, but that is for another day.
The keyfiles the Setup Guide is referring to are included in the download in the “FalconBMS Keyfiles” folder. You need to copy one of those to the BMS config folder, add any HOTAS bindings to the end of it, and point BMS to that keyfile. If you have your own HOTAS bindings then use the one marked “With no HOTAS profile” and add your HOTAS bindings. The ones with HOTAS bindings already attached are there only to serve as initial templates if you don’t have your own HOTAS bindings.
Quote: In the Falcon key callbacks>key file, I put "E:\Falcon BMS 4.35\User\Config\BMS - Full. Key” Is that ok?
No, see above.
Quote: Am I correct that the key profiles for what is used for the Falcon BMS 4.35 Setup in the game does not have to be the same as the callbacks key file in Helios?
No, they can be two separate files but the callback section must be identical except that the one in the game needs to have the HOTAS section added. Or you can just use the one in the game and point both BMS and the Helios profile to it.
Anti-Skid is the central position on the parking brake 3 position switch on the landing gear panel and according to the manual is the recommended mode to land with.
Quote: Next, in Helios, in the Falcon setup, the only Falcon version allowed is BMS 4.34. Is that ok?
Yes.
The Aux Comm/IFF changeover button is one of the buttons on the centre console.
-
Hi Oak,
Is there any way to run and old version of Helios, which currently has my personalised profile on it, along side, in parallel, with the new version of Helios and you 4.35 profile?
Why do I ask? I would like to transition from mine (old) version and profile to your (new 4.35) version which is a fantastic leap forward.
Why Transition? I have my profile, using MFDE, running across 5 touch screens, so its not a simple matter as it would be if it was just 1 touch screen and to be honest I could not fly very effectively without HELIOS.
Anyway - is there any way to run both at least in the short term?
Ironman.
You could try running each version of Helios in a separate Windows account and then use switch user to leave both running with their outputs directed at different monitors. Might be worth a try. Although one of them probably, almost certainly, wouldn’t see the BMS callbacks etc.
By the way you’ve attributed the 4.35 Helios profile update to the wrong guy.
-
Installation of keyfiles for Ice’s Updated Profile for Falcon BMS 4.35
1. If not using Alternative Launcher and not needing to change keyfile bindings.
The profile is preconfigured to use the keyfile in the C:\Bin\Keyfiles folder, leave this as is.
Copy the identical “BMS - Ice’s Helios Profile.key” file from the “Setup \FalconBMS Keyfiles\FalconBMS with no Hotas Profile” folder to the “Falcon BMS\User\Config” folder.
Add your HOTAS bindings to the end of the “BMS - Ice’s Helios Profile.key” file and point BMS to it.
If you don’t have your own HOTAS bindings then there are two alternative key files in the “Setup \FalconBMS Keyfiles” folder with HOTAS bindings to use as a guide.
2. If using Alternative Launcher and/or needing to change keyfile bindings.
Copy the “BMS - Ice’s Helios Profile.key” file from the “Setup \FalconBMS Keyfiles\FalconBMS with no Hotas Profile” folder to the “Falcon BMS\User\Config” folder.
Add your Hotas bindings to the end of this file and rename it to “BMS - Full.Key” AFTER renaming the existing “BMS - Full.Key” to “BMS - Full - Backup.Key” or something similar.
Now point BOTH the Helios profile and BMS to the “BMS - Full.Key” file in the “Falcon BMS\User\Config” folder.
Note: If there are any errors in the above please let me know (by PM preferably) and I’ll update it, otherwise, hopefully, we can move the topic on from the keyfile issue.
-
Hi Oak,
Is there any way to run and old version of Helios, which currently has my personalised profile on it, along side, in parallel, with the new version of Helios and you 4.35 profile?
Why do I ask? I would like to transition from mine (old) version and profile to your (new 4.35) version which is a fantastic leap forward.
Why Transition? I have my profile, using MFDE, running across 5 touch screens, so its not a simple matter as it would be if it was just 1 touch screen and to be honest I could not fly very effectively without HELIOS.
Anyway - is there any way to run both at least in the short term?
Ironman.
Fisrt again credits for the profile don’t go to me it’s the work of @linknet
Technically you could have both a 1.4 and 1.6 version running in parallel but not by using the installer. If you install 1.6 you overwrite your old 1.4 installation.
I personally have both 1.4 and 1.6 but I build Helios from the source code so I don’t use the “normal” user version. If you know how to handle git checkout, and Building an application from source in case of Helios with VisualStudio it would be achivable -
Apologies - linknet.
And thankyou both for your responses
-
It has been a long time since I played BMS and I no longer can use Target so how I would like to be able to implement the shift function when using Ice’s key profile and this Helios profile. Any thoughts?
-
The shift function has in the first place nothing to do with Helios at all and the ICE key file.
The question is which tool do you use to set your DX Bindings for the HOTAS?
In BMS UI you can’t directly set the shift layer you would have to add your shift layer bindings in the keyfile manually
Tools that kan be used to make the DX shift layers are eihter the Excel keyfile editor. Or the easiset and most user friendly way is to use the alternate Launcher for all of your HOATS bindings -
oakdesign: I know that the shift function has nothing to do with Helios, I just didn’t want to screw things up. Therefore, I will try the Alternative Launcher and your 2. If using Alternative Launcher and/or needing to change keyfile bindings method.
-
I have the profile working fine and my warthog HOTAS has been programed with the new ICE key file. However, I have only used the first layer of each button for commands. I tried to understand the shift function in the Ice key file but could not figure out how to work it. I noticed that in Section 5.11 of the key file in the game there is a command for STICK: PINKY SWITCH (DX SHIFT). Is that how I implement the shift function? If so, how do I indicate which other commands that will use the shift function?
-
This post is deleted! -
I have the profile working fine and my warthog HOTAS has been programed with the new ICE key file. However, I have only used the first layer of each button for commands. I tried to understand the shift function in the Ice key file but could not figure out how to work it. I noticed that in Section 5.11 of the key file in the game there is a command for STICK: PINKY SWITCH (DX SHIFT). Is that how I implement the shift function? If so, how do I indicate which other commands that will use the shift function?
If you set a button to the STICK: PINKY SWITCH (DX SHIFT) callback then pressing this button shifts the DX values seen by BMS by a default 256. So for example this shifts the original 0-31 range to 256-287. Therefore if you assign DX callbacks in the keyfile to the 256-287 range then holding the DX shift button and pressing any of the buttons mapped to the original 0-31 range will give you the callbacks in the 256-287 range, hence a new layer.
So with the default value of g_nHotasPinkyShiftMagnitude of 256 you can shift up to 8 separate DX devices giving a possible 8 shifted layers with a maximum total of 512 DX buttons. Check out the Falcon BMS Key File Manual if you need more information.
-
Options for Next Update - Version 4.35-2
Is anyone actually using the YAME64 option on the Centre Panel Display for the moving maps?
If this is not being used I’m considering removing it for this next update.
If you’re still using it I’ll leave it in.
-
I personally prefer the integrated CPD over the YAME CPD as a it integrates with WDP and I can use my “own” MAP. ie save from WDP as white map with flightplan. BE is dynamcially read. In Yame you would have to set BE manually in Yame. Your version has automatic briefing file reading, Ymae hasn’t. Apart from CPD as long as YAME doesn’t get fixed it can’t be used for MFD extraction on most nvidia GPU.
To be honsest don’t see any advantages in using Yame CPD -
I personally prefer the integrated CPD over the YAME CPD as a it integrates with WDP and I can use my “own” MAP. ie save from WDP as white map with flight plan. BE is dynamically read. In Yame you would have to set BE manually in Yame. Your version has automatic briefing file reading, Yame hasn’t. Apart from CPD as long as YAME doesn’t get fixed it can’t be used for MFD extraction on most Nvidia GPU.
To be honest don’t see any advantages in using Yame CPDAnd Yame64 can’t put the CPD (or anything else AFAIK) up as an overlay on your main BMS 3D screen either! One question I have since I am (as of yesterday) 100% using Helios to display MFDs and gauges on my 8" Lilliputs and the CPD on my main screen, is there a way to change the refresh rate for the MFDs in Helios? Using YAME64 or RTT the MFDs are silky smooth but I detect a bit of a low frame rate/mild stutter using Helios to display them. The CPD on my main screen seems good, though the Data Tab did not have the correct flight data showing for me.
-
The CPD on my main screen seems good, though the Data Tab did not have the correct flight data showing for me.
Which flight data was incorrect? If you’ve extracted the CPD from the full profile then you may be missing some or all of the Lua code which is in the full profile and sets up the CPD pages correctly.
-
Which flight data was incorrect? If you’ve extracted the CPD from the full profile then you may be missing some or all of the Lua code which is in the full profile and sets up the CPD pages correctly.
I want to say all of it, and yes, I just copied/pasted the gauges over from the full profile so i’m sure i’m missing something. As all the data I need is on my kneeboards its not really an issue but if its an “easy” fix ill do it. Reality is once I set the CPD to 60Nm/Bullseye/Moving MAP view once in 3D (I have to Alt-Tab to use the mouse, main screens are not touch) I don’t normally touch it anyway. This is a pic of my setup -
And THANK YOU for your work on this linknet!!
-
I want to say all of it, and yes, I just copied/pasted the gauges over from the full profile so i’m sure i’m missing something. As all the data I need is on my kneeboards its not really an issue but if its an “easy” fix ill do it. Reality is once I set the CPD to 60Nm/Bullseye/Moving MAP view once in 3D (I have to Alt-Tab to use the mouse, main screens are not touch) I don’t normally touch it anyway. This is a pic of my setup -
And THANK YOU for your work on this linknet!!
As I said with the help of JoystickGremlin and VJoy you could handle button presses on a Helios profile with keyboard commands as well.
Assing a free (not used in BMS) keyboard combination in JG to a VJoy Virtual Button
Add the VJoy device is interface to the Helios Profile (if you have multiple VJoy Devices they are in order so VJoy Device#1 is first )
Assing the Vjoy Button press as input to the Helios Button you wan’t to be pushed with the keyboard. No need for alt-tab