Ice’s Falcon BMS Profile Updated for BMS 4.37
-
Linknet, thank You for the updated profile!
Everything is working fine. -
@linknet I’ve got a few physical toggle switches now and noticed that the Helios switches do not sync to the physical switch when I throw these physical switches. Is this something that would be easy to implement or is it something impossible for Helios to do?
-
@Atlas said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet I’ve got a few physical toggle switches now and noticed that the Helios switches do not sync to the physical switch when I throw these physical switches. Is this something that would be easy to implement or is it something impossible for Helios to do?
BMS only provides position data for very few of the switches, all of the switches which do provide position data are mapped to the corresponding switches in the profile.
For the rest of the switches it can be done but it depends on exactly how your physical switches interface with BMS. That’s as far as I can go since I don’t have any experience in this area. Try asking @Wheelchock
-
@linknet How do you know which switches have position data and which ones don’t?
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@zeek said in Ice’s Falcon BMS Profile Updated for BMS 4.36:
@linknet I am having the problem again with the kneeboards updating. It looks like it is that same problem as last time where the KneeBoardsUpdate.exe is hardcoded to the 4.36 directory. Is it easy to provide a quick update to that exe? If not as a workaround I can just run an older version of WDP that is pointed to 4.36 to update the kneeboards so Helios can pull it from the 4.36 directory.
In the latest 4.36-05 version of the profile the kneeboard updater path isn’t hard coded, the profile passes the most recent BMS path as a parameter to the updater. I’ve just tested the 4.36-05 version of the profile with BMS Falcon 4.37 and the kneeboard update is working fine. If you’re running this latest version of the profile and it still isn’t working just let me know.
I am having the same problem since 4.37. The kneeboard updater by way of Falcon/Briefing/Print worked fine. Now it doesn’t anymore even though the Falcon path in C:\bin\PathNames.ini is set to 4.37.
-
@Atlas said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet How do you know which switches have position data and which ones don’t?
Good question. You’d have to work through every section of the Falcon interface in the Profile Editor to create a list. Simple way is to enter 3D, select Freeze and the 2D View, and then operate any control that you’re concerned about. Then check If the corresponding control in the profile operates.
-
@Atlas How do you do that please? I cannot change it in the keymapper screen. Thanks
-
@zeek I had this and when I reinstalled helios and restarted pc it started to work. Try it
-
@Bikeman There isn’t a Pathnames.ini file in version 4.37-01, try completely deleting the C:\Bin folder and using the latest one.
-
@maverick007 said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@Atlas How do you do that please? I cannot change it in the keymapper screen. Thanks
How do I do what? Or was that question for @linknet ??
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
Good question. You’d have to work through every section of the Falcon interface in the Profile Editor to create a list. Simple way is to enter 3D, select Freeze and the 2D View, and then operate any control that you’re concerned about. Then check If the corresponding control in the profile operates.
Thanks!
-
@linknet Hi. What I recall it was conserning the process tab. Data auto update. Helios Control Center throwed some error that the file does not exist in bin although it was there. I deleted the commands “%BMSFalconPath%” “%HeliosPath%” and it worked. Maybe I messed up something. I dont know.
In the guide i would also add a sentence to tell newbies how to exactly point to the new keyfile in falcon bms. Something like open bms, go to settings, click controllers, click load, select desired key file. Preferably with screenshots. I did not know that and I had to fiddle with the user controls a bit to find out. I think this is very importat as you can do all the settings right in helios but it wont work without pointing to the new keyfile.
Also strange thing I have to point exachtly to your keyfile calle Ice, cause if I rename ice keyfile to full and point to it in bms it just doesnt work. Maybe because in helios I have to also point to the new full key file. But when I did that helios started screaming that there are missing callbacks. Strange…
-
This post is deleted! -
@Bikeman said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@Bikeman There isn’t a Pathnames.ini file in version 4.37-01, try completely deleting the C:\Bin folder and using the latest one.
I followed your instructions. The data are updated in the CPD/PLAN screen, the auto-updater kneepads unfortunately not. Any other steps I have to take besides PRINT in the briefing screen?
@Bikeman said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@Bikeman There isn’t a Pathnames.ini file in version 4.37-01, try completely deleting the C:\Bin folder and using the latest one.
I followed your instructions. The data are updated in the CPD/Map screen, the auto-updater kneepads unfortunately not. Any other steps I have to take besides PRINT in the briefing screen?
-
@linknet It is in process control - it throws Argument error cause in the process control the file is named DataAutoUpdate.exe, but in C:\Bin\ the file is actually called CPDAutoUpdate.exe I had to correct the name in helios process control. Then the process controll was green
-
@maverick007 said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet It is in process control - it throws Argument error cause in the process control the file is named DataAutoUpdate.exe, but in C:\Bin\ the file is actually called CPDAutoUpdate.exe I had to correct the name in helios process control. Then the process controll was green
I have no idea what you are doing, there is no DataAutoUpdate.exe file or any instance of it in any of the 4.37-01 profiles.
-
@linknet The Briefing.txt gets updated correctly. The Pilot Roster etc are not displayed correctly when I press the DED. They show the data of some other TE. Hope this helps in troubleshooting. Auto_Left.png and Auto_Right.png do not get updated.
-
@Bikeman said in Ice’s Falcon BMS Profile Updated for BMS 4.37:
@linknet The Briefing.txt gets updated correctly. The Pilot Roster etc are not displayed correctly when I press the DED. They show the data of some other TE. Hope this helps in troubleshooting. Auto_Left.png and Auto_Right.png do not get updated.
From what I can see you’ve got parts of 4.35-06 hanging around which are now totally incompatible with 4.37-01. Unless you completely reinstall the profile I don’t believe I can help. Delete the Bin Folder and the Profile files completely and start again. I’ve tested 4.37-01 several times from a clean install and it works perfectly.
-
@linknet Wildo. Btw: thank you for the superb things you do with Helios. I couldn’t fly the Falcon without.
-
@linknet No problem, I keep investigating further. I erased BIN und Helios folders and installed new. The control center gives me a binding error when I push the Restore Kneepads and Update Kneepads buttons. As I said, no need for you to spend time, I keep investigating and let you know what I find.
I noticed that the profile is set to BMS 4.36. I changed it to 4.37.