BMS 4.37 DX button changes
-
Maybe I missed it somewhere but I finally figured out why my key file wasn’t working for all my controllers. It looks like a DX device can now support 128 buttons (unshifted) compared to the old limit of 32. Well this really threw all my buttons assignments off but once I realized what was going on it was easy to solve.
What worked for me was to do the following quick math:
- I have 10 DX devices (Cougar, TM MFDs, 5 Bodnar boards, Redneck ICP, rudder pedals)
- At a minimum then, I needed to reserve 1280 buttons before mapping shifted / pinky button
- Knowing I will want to add some additional devices, I settled on a plan for 16 devices
- This means pinky button should be 16x128 or 2048.
So now any DX button on my first device (Cougar) starts at 1 and could go to 128 (of course the Cougar doesn’t have that many) and starts its shifted buttons at 2049. My second device starts unshifted at 129 and goes to 256 using shifted 2177-2304 and so on.
After making those changes, all my old mappings worked great. Of course I verified all the callbacks were still valid and added in any new callbacks that were desired.
Hope this info helps others.
-
I guess I did miss this!
Looking back at some posts from a few weeks ago, I found this gem that would have saved me all the trouble if I had just known about it:
set g_nButtonsPerDevice 128
set g_nHotasPinkyShiftMagnitude 1280 // room for 10 devices x 128 buttonsIf I had that setting in my user config and set it to 32, then everything would have been fine.
-
Thanks, this helped me track down my issue as well!
While not as many and/or as complex, the buttons were still not mapped correctly after WinMerge-ing my DX keyfile back in (even after enabling the BMS Alt Launcher “setup override”).
It appears that the global “Falcon BMS.cfg” did change the defaults to 128 ButtonsPerDevice, even though the documentation says it will remain at 32 devices for backward compatibility (page 164 of Tech Manual).
I added the following to “Falcon BMS User.cfg” to restore the 4.36 values:
set g_nHotasPinkyShiftMagnitude 256 set g_nButtonsPerDevice 32
-
Alt Launcher, which is now bundled with 4.37 and no longer “Alt”, will set it to 128 always.
This was a pain point in 4.36 as well, for folks with multi-device key files
-
@boomer said in BMS 4.37 DX button changes:
set g_nHotasPinkyShiftMagnitude 256
Just installing 4.37 and wanted to mention that 256 is the default value for 4.37 too
-
@jayb said in BMS 4.37 DX button changes:
@boomer said in BMS 4.37 DX button changes:
set g_nHotasPinkyShiftMagnitude 256
Just installing 4.37 and wanted to mention that 256 is the default value for 4.37 too
Yep. And combine that with the new default of 128 buttons per device and anyone with more than two devices is going to have an issue unless they add the PerDevice override (in 4.36 they didn’t have to do that). Hopefully most will see posts like this one.
-
@boomer
Thanks for this tip! I just finished my first 4.37 test flight, after importing my 4.36 DeviceSorting.txt file and my 4.36 .key files, my axismapping.dat, d3d11.dsp, and Falcon BMS User.cfg from 4.36.I have 4 devices (HOTAS Cougar, 2 x Thrustmaster MFDs {using 4.37’s RTTRemote and my 4.36 RTTRemoteClient.ini file}, and 1 x SimGears ICP) plus a couple others that are not Windows controller devices (1 x smartphone app named “BMSDevicePro” which uses its own mini-server to interface with BMS to extract RWR and Fault/Warning info and 1 x PSM DED+Fuel Flow Indicator which are run via DEDuino on an Arduino Uno board), plus TrackIR and @SemlerPDX 's excellent Profiles for Voice Attack.
Using your tip, I put “set g_nButtonsPerDevice 32” in my Falcon BMS User.cfg file ( @jayb is correct that 4.37 default config is “g_nHotasPinkyShiftMagnitude 256” so no need to put that in Falcon BMS User.cfg). I also set DeviceSorting.txt to “Read Only” attribute.
On a fresh install of Falcon BMS 4.37, I set up my launcher shortcut to point to the original Falcon BMS 4.37 launcher, not Alt Launcher. I have not tried (nor do I want to try) Alt Launcher. During a complete test flight in a F-16 DM-50, all my buttons on all my devices worked properly (even the cursor up left, down right etc.). Upon exiting Falcon BMS 4.37 normally, I checked DeviceSorting.txt and it was unchanged, and still dated from the date of my 4.36 use (11/18/22 is when I last changed it to include the new SimGears ICP).
I use Win10 Home, v22H2, last updated 12/05/22. When I installed BMS 4.37, I di use the Install DirectX option. I do not have VR gear, so that is unchecked in Config.
Hope this helps anyone else who may be having issues with DeviceSorting.txt.
Regards,
Tomcattwo
(VoiceClone)