Ice’s Falcon BMS Profile Updated for BMS 4.37
-
How are determine between Ramp and Hot Start through Shared mem? For Airstart WoW would be sufficient enough. But on the ground even so someone might select Ramp Start and TO time is less than configured Ramp Start but more than configured Taxi Start time the jet might be in an intermediate state with some systems already powered up.
Good point. Currently for Air Start versus Ramp/Taxi/Runway Start using OnGround only. For Ramp Start versus Taxi/Runway Start using RPM > 0. Which, so far, is working correctly with no problems.
For the two test dll’s I tried using Power_Off to differentiate between Ramp Start and Taxi/Runway Start with inconclusive results. Possibly what you suggested might have been the cause.
-
-
My little problem. With Ramp all controllers are in position zero, only MSL; Threat and intercom in full position. Where is the mistake?
Thanks again for this great Ice’s Falcon BMS Profile 4.35-10
best regards
Nik
-
@nik:
My little problem. With Ramp all controllers are in position zero, only MSL; Threat and intercom in full position. Where is the mistake?
Thanks again for this great Ice’s Falcon BMS Profile 4.35-10
best regards
Nik
At the moment the positions are set as follows for all start modes:
Missile = 6/9
Threat = 8/9
Intercom = 9/9This is according to the default settings in Section 4.4.3 Sound Page of the BMS 4.35 Manual for Sidewinder, RWR and Intercom. There isn’t any feedback via shared memory for these so there really isn’t any point in setting them to anything other than the default values for all of the start modes.
Edit: The value could probably be read from the BMS Config file but that involves a lot of Lua code, and more possibility for errors, for each rotary switch just to extract the initial position.
-
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
Ice’s Falcon BMS Profile Updated to 4.35-11
Updated 07 Nov 2021:
The first post has been updated with the latest version.
Please note the requirement for Helios Version 1.6.5100.0 or later.
Thanks Linknet (and all involved), this is fantastic work!!
-
Thank You, Sir.
-
I have a question relating to overall FPS impact using Helios and/or Ice’s Profile.
All is working great (BMS, Helios & Ice’s Profile) but have seen a 12~14 FPS drop when using Helios and BMS 4.35-U3. The comparison was done with a quick load of the 01-Ground Ops training mission and watched the FPS counts while sitting in 3d cockpit shows:
- No Helios/Ice = 63/64 avg FPS
- With Helios/Ice = 49/50 avg FPS
I’ve played around extensively with changing all the go-to Nvidia control panel settings and BMS graphic options. Safe to say, the “No Helios” averages are the best I’ll get (flying with 4k G-sync wide screen) so I’m fairly certain the big drop is directly related to running the profile. On a side note, the Benchmark_Test mission averages 28-30 FPS sitting in the cockpit on the ramp.
Main thing I’m asking…is that -12/15 FPS a normal drop to expect when using Helios profiles? Just want to make sure I’m not missing a parameter or “tweak” somewhere.
-
@slick8791-0 said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
Main thing I’m asking…is that -12/15 FPS a normal drop to expect when using Helios profiles? Just want to make sure I’m not missing a parameter or “tweak” somewhere.
Open the profile in the profile editor and in the Falcon Interface settings, select the gear wheel, under Falcon Texture Refresh check the Use Legacy Refresh box and save the profile. That will reduce the texture extraction rate and should improve things, your MFD displays may not be as smooth but if that is a problem then you would need to set up RTT for the MFD displays on the centre console.
-
Many thanks for that Linknet! A noticeable improvement with that checkbox on my end. Ramp avg FPS improved to 57. In-flight FPS was improved even better.
If the display’s smoothness took a hit, it wasn’t very much as far as I could tell. Will give it a better run through this weekend.
-
PS Just curious, would there be any benefit to raising the RTT FPS setting from 30 to say 60? My touchscreen monitor refresh rate is set to 60-Hz so just wondering if there was a possible connection.
-
@slick8791-0 said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
PS Just curious, would there be any benefit to raising the RTT FPS setting from 30 to say 60? My touchscreen monitor refresh rate is set to 60-Hz so just wondering if there was a possible connection.
This only applies if you’re actually using RTT, it sets its polling rate, it has no effect on the Helios texture extractions.
-
Hi @linknet,
I’ve just created a new profile where I’m copying the MFDs onto two iPads (left and right) but retaining the main profile on a central (android) tablet.
When I load up the profile and test it by clicking “buttons” the corresponding items highlighted in the Falcon setup screen, but when I go through to 3D the iPads no longer seem to send callbacks to Falcon, the textures update OK (though a little slowly). Also, buttons pressed on the android tablet register callbacks in Falcon.
I’m using the US keyboard (I’m from the UK) from the instructions.
Any idea what I might be doing wrong?
I appreciate I have edited your profile so this request is probably not your issue but I would be interested to see if you had any thoughts.
TANX
Critical -
It sounds as though the main 3D screen is losing focus when you’re using the iPads although since I’ve never used that type of setup I suggest you try and contact @oakdesign who I believe uses iPads in his setup.
By the way, you can use the UK keyboard with no problems as I designed the profile using a UK keyboard and just avoided adding callbacks to any of the few keys where the UK and US keyboards differ.
-
<p>I’ve noticed that Helios (BMS Profile 4.35-11) works great when I click on a button or switch <u>on the touch screen</u> and it activates the button or switch on the main “BMS” screen. <br />However, if I click on the same button or switch, <u>with the mouse</u>, on the <u>main </u>“BMS” screen, the corresponding switch or button on the touch screen <u>does not change it’s status</u>.<br /><br />For example, if I use the Helios touch screen to turn on the landing lights, the lights come on and both on-screen toggles are “up” . However, <u>if I use the mouse on the main screen</u> to turn on the lights, the main screen toggle goes up but the touch screen toggle doesn’t change. <br />It seems that it should work <u>both </u>ways. <br />Is this the way it’s ‘supposed’ to work or have I got a setting wrong in the stock “BMS Ice’s Helios Profile.key” or the stock Helios profile? <br /><br />I’ve been using the mouse for so long, when I accidentally use the mouse, instead of the touch screen, the status of the switches between the touch screen and the main screen change and it creates havoc when the switches don’t match!<br />I realize that I can disable the mouse “on-the-fly” with the on-screen mouse button, as a workaround solution, but I’ve often forgotten this and have had to start the flight all over again! (really annoying when you’re half-way through a mission!)<br /><br /><br /></p>
-
<p>@Dan BMS only exports a few of the button, knob and switch positions, unfortunately this means that the majority are one way only. It’s a problem with BMS not the Helios profile. All of those that can be mapped as two way are mapped as two way in the profile.<br /><br />For example, from memory, the NavMode Knob, the Auto Pilot switches and the Parking Brake switch are two way just to name one or two. , </p>
-
<p>@linknet,<br />Thanks, that explains it!<br />Is it possible in the future, for BMS to export <u>all </u>of the button and switch positions to make them all two or three-way, perhaps in 4.36 or 4.37?</p>
-
<p>@Dan You’d need to raise that point with the BMS Developers, although the request list is miles long already, everyone wants something different.<br /></p>
-
<p>Greetings Helios team - <br /><br />I just updated to Helios v1.6.5102 (not sure if this is the cause) and I keep getting the “Pilot Callsign not set” error. (See error message below). As I know all that’s needed to do is run BMS and it updates. Is this no longer the case? And just out of curiosity, what “looks” for the callsign? Is it something in Helios? or is it in the profile??<br /></p><blockquote>{<br /> “product”: “Helios”,<br /> “version”: “1.6.5102.0”,<br /> “items”: [<br /> {<br /> “report”: [<br /> {<br /> “timeStamp”: “03/08/2022 05:07:14.890 PM”,<br /> “status”: “Loading Profile…”<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “status”: “Selected Falcon interface driver is ‘BMS’ version ‘Falcon BMS 4.35’”,<br /> “flags”: 2<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “status”: “The key file configured in this profile is ‘C:\Program Files\Games\Falcon BMS 4.35\User\Config\Jolly’s Cougar Helios Profile.key’\n”,<br /> “flags”: 2<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “severity”: 2,<br /> “status”: “Pilot Callsign not set in BMS”,<br /> “recommendation”: “Run Falcon and set your pilot callsign”<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.665 PM”,<br /> “severity”: 2,<br /> “status”: “Failed preflight check.”,<br /> “recommendation”: “Please resolve problems or disable preflight check in preferences.”<br /> }<br /> ],<br /> “name”: “Control Center Console”<br /> }<br /> ]<br />}</blockquote>
-
<blockquote>Greetings Helios team - <br /><br />I just updated to Helios v1.6.5102 (not sure if this is the cause) and I keep getting the “Pilot Callsign not set” error. (See error message below). As I know all that’s needed to do is run BMS and it updates. Is this no longer the case? And just out of curiosity, what “looks” for the callsign? Is it something in Helios? or is it in the profile??<br /><br />{<br /> “product”: “Helios”,<br /> “version”: “1.6.5102.0”,<br /> “items”: [<br /> {<br /> “report”: [<br /> {<br /> “timeStamp”: “03/08/2022 05:07:14.890 PM”,<br /> “status”: “Loading Profile…”<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “status”: “Selected Falcon interface driver is ‘BMS’ version ‘Falcon BMS 4.35’”,<br /> “flags”: 2<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “status”: “The key file configured in this profile is ‘C:\Program Files\Games\Falcon BMS 4.35\User\Config\Jolly’s Cougar Helios Profile.key’\n”,<br /> “flags”: 2<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.664 PM”,<br /> “severity”: 2,<br /> “status”: “Pilot Callsign not set in BMS”,<br /> “recommendation”: “Run Falcon and set your pilot callsign”<br /> },<br /> {<br /> “timeStamp”: “03/08/2022 05:07:16.665 PM”,<br /> “severity”: 2,<br /> “status”: “Failed preflight check.”,<br /> “recommendation”: “Please resolve problems or disable preflight check in preferences.”<br /> }<br /> ],<br /> “name”: “Control Center Console”<br /> }<br /> ]<br />}</blockquote><p>This isn’t new to 1.6.5102.0. For BMS there isn’t anything new in this version. If you fly DCS then you’ll want this update. With that said, Helios initially reads the pilot callsign out of the windows registry (just like your Falcon BMS install locations). Unless you are using the Force Key File feature of the Falcon Helios Interface then just ignore it. If you are using that feature I would do some investigating of your registry entries for Falcon BMS and see if you callsign is setup correctly.<br /></p>