Ice’s Falcon BMS Profile Updated for BMS 4.35
-
I was thinking the profile needs a switch for the RPM gauge - to switch between GE and PW, simpler than the Aux Comm/IFF panel I imagine (took a look at doing it, but the LUA script baulked me).
The RPM gauge is already on a panel so copy the complete panel. Set the second panel to hidden and create a full size transparent button on each panel to hide its own panel and show the other panel. So now a tap on the RPM gauge will switch between the two gauges. On the second panel change the gauge image, the lua code and the gauge needle rotation range.
The current lua code is:
if TriggerValue < 70 then return TriggerValue * 50/70 else return ((TriggerValue - 70) * 50/30) + 50 end
The code you would need on the second panel would be something like this:
if TriggerValue < 60 then return TriggerValue * 50/60 else return ((TriggerValue - 60) * 50/40) + 50 end
But you would then have to establish the correct value for the midpoint (scale changeover point) of the actual gauge dial image, on the current gauge image it just happens to be approximately 50%, hence the values of 50 in the lua code. The next update will include a more accurate version with two changeover points instead of one.
Then in the gauge needle settings change the rotation range maximum value until the needle points to the maximum value on the gauge dial.
-
On his first flight he realized that there is no touch representation of the Ejection handle in the profile.
https://up.picr.de/40502589vd.gifThat looks like it’s straight out of Weepops’ profile, or maybe he copied it from elsewhere.
-
https://up.picr.de/40502589vd.gif
That looks like it’s straight out of Weepops’ profile, or maybe he copied it from elsewhere.
that is my personal profile an yes i took the images from weepop profile to implement it into my peronal profile. The handle image in to up state I would say is taken from the cockpit.dds directly out of BMS
-
I was thinking the profile needs a switch for the RPM gauge - to switch between GE and PW, simpler than the Aux Comm/IFF panel I imagine (took a look at doing it, but the LUA script baulked me).
To go with my previous post on this here is an image for the 100% RPM Gauge taken from an actual cockpit photo and tweaked extensively with photoshop. The changeover point on this is at approximately 39% of the gauge image.
So the lua code for that would be:
if TriggerValue < 60 then return TriggerValue * 39/60 else return ((TriggerValue - 60) * 61/40) + 39 end
I’ll add it to the next update.
-
Hi Linknet
This is a very outstanding work, indeed.
I am planning to use your profile in my second monitor but, there are too much information for me. Besides, I don’t have Touch screen monitors here.
I was thinking about to have the Lateral consoles and the moving map only in this second monitor, maybe workin with mouse.
I am rookye level -01 with Helios :smash: so I may ask you 2 things:
first if you allow me to modify your profile for my needs and
second: How dificult would be for a noob like me to leave just the lateral consoles and the moving map working in your profile?cheers
-
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
-
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.