If you're having issues take a look at DeviceSorting.txt
-
Setting my TM Warthog controls up has been such a big hurdle preventing me from getting back into BMS that I figured I’d post the solution to an issue I was having here, hoping it can maybe help someone else having a similar issue.
I started off with a fresh 4.33 U2 install and grabbed Morphine’s profile from here. I went through all the steps but many of the key assignments didn’t show up correctly on the BMS controls page, like my DMS was bound to OSB keys. I randomly came across Agave_Blue’s post here about changing the order of controllers in BMS\User\Config and that did the trick. I previously had “Thrustmaster Virtual Game Controller (root)” listed below “Joystick - HOTAS Warthog” and “Throttle - HOTAS Warthog” but moving it to the top of the file did the trick and now all the commands work as intended.
-
So i’m about 2 hours into unboxing this thing. I’m able to get everything working until I plug the Thurstmaster rudder pedals in and then I see the same behavior you’re describing. Does this address this issue?
EDIT
YESSSSSSS success!
-
Have a read of the Installation and Configuration chapters of the BMS-Manual (in your \Falcon BMS 4.33 U1\Docs\Falcon BMS Manuals folder) before you go any further. It will answer a lot of questions you will have.
Pages 49-50 address this specific configuration issue.
-
This post is deleted! -
Theres actually two BMS device files:
- DEVICESORTING: reflects the devices as Windows assigns them to GUIDs and can be checked in then Windows controller panel. This is also what shows up in the BMS Controls device pulldown menu.
- DEVICEDEFAULTS: defines the flight axes for each controller as selected in the BMS Controls assignment pages, and maps the device name back to the Windows IDs.
The point of these files was to maintain the axes assignments within the BMS Controls pages even if the Usb ordering changes as devices are unplugged or moved to different ports. Sometimes it still gets out of sync and you either make the fixes manually in the files if you understand them, replace them from a backup, or delete them and they will be regenerated. In which case you have to reassign the axes again within BMS.