Ice’s Falcon BMS Profile Updated for BMS 4.37
-
So… I have the updated lighting panel, canopy and com menu for JTAC working with no issues. I can send it to you guys if you want, I just dont know the best way to share the changes other than just screenshots which doesn’t seem the best way. Do you guys know what files I could share for others to get those updates? I run a hacked up version of Ice’s with several custom changes (ie - Idle Detent button as you can see in the screenshot below) so just sending the whole package probably wont work well.
My question is with the kneeboards, I am not able to get them to update using 4.36 WDP. The only thing I can think is I am missing a step in updating a path as it seems like Ice’s UpdateKneeBoards.EXE isn’t getting the updated files WDP saved. Does anyone use the kneeboards and know what I may be missing?
Also if there is a way I can share the lighting panel let me know if that will help anyone out.
-
I always find that the best way is to copy from one complete profile to another. So if you send the complete profile then that can be opened up side by side with the target profile and the relevant parts copied across. Another way is to copy the panel you want to share to an xml file but I’ve never found that very successful. A third way if you don’t want to share your complete profile is to copy your profile to a different name and then delete everything other than the parts you want to share, that way the shared part of the profile can be opened up side by side with the target profile and the relevant parts copied across.
For your other question it would seem that I’ve hard coded the kneeboard updater for 4.35, I’ll see if I can modify it and post a new version.
-
Here’s a temporary fix for the DataAutoUpdate.exe and the KneeboardsUpdate.exe for 4.36.
Hopefully they should work but I haven’t any means of testing.Link removed, use latest updated profile.
-
-
@linknet just tested you update and it works. What would be nice if you could define multiple BMS versions in the ini file so that you could use the profile fully against older versions and the latest and greatest BMS version. my VFW doesn’t move to the new version until its properly vetted so I end up having two version at some point side by side (install wise).
-
@Todd1215 I think you need more than just the profile as there was an image file that needed to be updated also. I hacked that together in paint. looks like I cant upload a file here. Will try and get it loaded to a fileshare and send the link.
@linknet that explains why it was still working if I updated the 4.35 directories with WDP for 4.35. I haven’t tried out with your update but sounds like it worked for Todd
@Todd1215 @linknet does this link work for you?
https://www.dropbox.com/s/ablc9wmhd9ad7c1/Helios zeek updated.7z?dl=0 -
@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