Ice’s Falcon BMS Profile Updated for BMS 4.37
-
@linknet where do those files go? my Bin folders files are called UpdateKneeBoards not KneeBoardsUpdate
-
@zeek said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@linknet where do those files go? my Bin folders files are called UpdateKneeBoards not KneeBoardsUpdate
The Bin folder. You must be using a previous version, KneeboardsUpdate.exe is correct for version 4.35-12 of the profile. I’m afraid you probably need to update to 4.35-12 and then hack that as you require for it all to work.
-
@Todd1215
The problem is how do you determine in the profile which version of BMS is running?
Perhaps by accessing the running BMS running process and using it’s path, but since I can’t run BMS here it’s a no go to see if it’s possible.
Unless you have any other ideas on how to determine which version of BMS is running.
Otherwise you just need a simple cmd file to copy the relevant copies of DataAutoUpdate.exe and KneeboardsUpdate.exe to the bin folder.
-
@linknet I was worried you were going to say that… It was working fine with the older version in 4.35 so I never updated in the past due to key file changes and other minor additions. Will continue to use the 4.35 directory for now until I can motivate myself to update and get it all working again. The inconvenience of using the 4.35 directory isn’t worth the time to get it working on the new version… yet.
Thanks.
-
@zeek No problem.
-
@linknet Don’t you read pathnames.ini using loa code somewhere in the CENTER PEDASTAL DISPLAY Panel? I did it in a older version of the profile where I would create a second section [FALCON_BMS436_PATH] and set the luau code in the profile to read the pathnames.ini and read that section by name. this way I could set the profile for a specific version. I haven’t done that hack in awhile so I’m not sure your newer binaries would work the way they used to. I know you changed that awhile back.
We could expose selected falcon version as a binding so it can be used by utilities maybe.
-
@Todd1215
I think the way to run both 4.35 and 4.36 versions of BMS would be to have two profiles, the original one for 4.35 and the new one modified for 4.36. Then I would have the original DataAutoUpdate.exe and KneeboardsUpdate.exe in the Bin folder together with the latest DataAutoUpdate.exe and KneeboardsUpdate.exe renamed to say DataAutoUpdate2.exe and KneeboardsUpdate2.exe. Then edit the 4.36 profile so that it opens the renamed xxxxx2.exe files.
So now whichever profile you start the PathNames.ini should get the correct paths written to it and the lua files in CPD should read that path and work correctly.
You would need to close the Control Center when swapping and make sure that the current DataAutoUpdate process has exited before restarting the Control Center.
Or you could just put a DataAutoUpdate process kill command in each profile to kill the opposite DataAutoUpdate before starting the new one.
I think!!!
-
@linknet - Just ran my 1st 4.36 KTO campaign mission, my old 4.35 Helios-12 profile converted to 4.36 and the extraction works the same, but the exported MFDs are stuttering again and there is a delay when I press an OSB. I’m getting 110-130FPS in game, the BMS MFDs are smooth as silk and OSB response is instantaneous. Any ideas other than resort back to RTT?
EDIT: If I try to enable RTT through Helios I do not get MFDs and it removes all the MFD X/Y settings (sets them back to 0) in the RTTClient.ini file it creates. If I run RTTClient standalone it works well… likely something i’m missing in Helios.
-
@Icer What is your g_nRTTExportBatchSize value set at in Falcon BMS.cfg or Falcon BMS User.cfg
-
@zeek Yes it did, do you have a updated keyfile to go with it?
-
@Todd1215 said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer What is your g_nRTTExportBatchSize value set at in Falcon BMS.cfg or Falcon BMS User.cfg
set g_nRTTExportBatchSize 2
-
@Todd1215
I do have a keyfile that works with it, but I wouldn’t recommend using it as it was from an older version of Ice’s profile and then updated to 4.36 and then modified for these latest changes. I will send a link in a bit but I recommend just mapping the missing callbacks as what I have in my keyfile may conflict with what you have in yours.
-
@zeek yeah…I’m just lazy LOL… I know I should use my own !
-
@Todd1215 here is the Keyfile I use, again use at your own risk as it is a ICE’s old 4.35 Keyfile manually changed to 4.36. I haven’t had any issues with it yet but have only done one flight thus far. I don’t use the keyboard for anything so some of the default keys you may have mapped before may not work anymore.
https://www.dropbox.com/s/kjre4503bhbv4ev/BMS - Auto.7z?dl=0
-
@zeek thanks… I was working on updating my Ice 4.35 to a 4.36 keyfile but I must have done somthing wrong as stuff is getting triggered that shouldn’t be. I’ll see if yours works any better.
-
Ok, have identical profiles for 4.35.3 and 4.36 (of course each points to the proper executable) . The 4.35.3 profile runs perfectly smooth with no hesitations or stutters. Same profile in 4.36 is a stuttery mess with all gauges and the MFD s and the OSB buttons even have a delayed reaction on the exported screens. Looking at the cockpit itself everything is smooth and external OSB response is instantaneous. Using RTT for MFD extraction all displays perfectly but no matter what I try the gauges are not smooth at all. I have tried with and without the updated C:\Bin files, same results. I can try building a new profile from scratch but it has to be something in 4.36 causing this, just have no idea what? Goint to toss it into the Tech issues area also, but no one else running Helios seeing this?
-
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
@linknet the profile was taken from 4.35-12 but i’m going to make a new one and see what happens. Again, the same profile in BMS 4.35 works perfectly…
-
After pulling (what’s left of) my hair out I decided to drop a nuke and uninstall 4.36 completely and do a reinstall from scratch. No add-on theaters, nothing (though I did all my testing in OEM KTO anyway). Works perfectly now. Wish I could say what the issue was…
-
@Icer said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
@linknet the profile was taken from 4.35-12 but i’m going to make a new one and see what happens. Again, the same profile in BMS 4.35 works perfectly…
@Icer Are you saying the ‘BMS - Full.key’ works fine in Helios, we don’t need copy the content of ‘BMS - Ice’s Helios Profile.key’ into it?!