Ice’s Falcon BMS Profile Updated for BMS 4.37
-
The extracts work - funny, how things work, when you do them right:)
What “new copy” are you referring to? Please provide download / file size. I’ll try itThis is the new copy of the HeliosFalcon.dll I’d like you to test:
https://www.mediafire.com/file/djiuwervtmauney/HeliosFalconTest.zip/file
Size is the same as the file in the download but date and time are different: 48,635,904 03/09/2021 16:15:14
Again remove any other HeliosFalcon.dll’s, whether renamed or not, so that this is the only one in the plugins folder.
Please check that Ramp goes to Ramp Start and Taxi/Runway go to Hot Start and that I haven’t got them reversed.:)
-
Your latest HeliosFalcon.dll does NOT give a ramp start, but the Hot Start profile. The previous .dll works however.
I even entered the 3d world first with ramp start and then started the profile - it shows the correct ramp profile - good show!All in all, it seems as if your latest .dll does not do the trick, the previous one doess. It also starts with the air start profile when entering the 3d world in the air correctly.
-
Your latest HeliosFalcon.dll does NOT give a ramp start, but the Hot Start profile. The previous .dll works however.
I even entered the 3d world first with ramp start and then started the profile - it shows the correct ramp profile - good show!
with this
All in all, it seems as if your latest .dll does not do the trick, the previous one doess. It also starts with the air start profile when entering the 3d world in the air correctly.Thanks for testing it, if you could do one last test for both Ramp and Taxi/Runway with this:
https://www.mediafire.com/file/5dsgk6z7bk9d4sn/HeliosFalconTest2.zip/file
This is just to test an alternative method, I know that the dll supplied in the download is working with no problems.
-
Nope, your latest doesn’t work: Ramp–> Hot Start profile, same for Air start
-
Nope, your latest doesn’t work: Ramp–> Hot Start profile, same for Air start
OK, thanks for testing it anyway, it proves that one of the shared memory variables I had intended to use doesn’t perform as expected, it’s not a problem, I can sort out what I was trying to achieve at a later date.
-
Question regarding you key file though: switching to IFF Master Low blanks the screen for 1 or 2 seconds. It comes back but I wanted to let you know anyway.
-
OK, thanks for testing it anyway, it proves that one of the shared memory variables I had intended to use doesn’t perform as expected, it’s not a problem, I can sort out what I was trying to achieve at a later date.
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.
Gesendet von meinem SM-G930F mit Tapatalk
-
Question regarding you key file though: switching to IFF Master Low blanks the screen for 1 or 2 seconds. It comes back but I wanted to let you know anyway.
IFF Master Low only sends the key combination Ctrl-Alt-F8, nothing else, so something on your system must be picking that up as a hotkey combination or even just responding to F8 alone. Either change the system hotkey or change the keyfile callback combination.
-
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.