Researching axis and button assignments
-
I am looking for a good post explanation of why bms cant hang on to axis and button assignments for the cougar hotas, and if there is any info on how it chooses the axis names of physical controllers.
If anyone has posts on these topics bookmarked, please share them. Thanks.
-
It should. If the program is having an inability writing to the files to save configuration (program files/program files x86 is often write protected) that could be it. In general the program also writes the names of devices in devicesorting.txt which is how it allocates device #1, #2, #3 etc. If your buttons shift by multiples of 32 strangely then that’s a device order issue. If nothing ever saves ever that’s probably file writing.
-
If you have specific problem scenarios where you think something should be consistent and it’s not, please give us more detail on that. Consider framing as a bug report…because generally the code tries hard to keep axis and button assignments consistent so long as the mapped devices are connected to the system each time it tries to access them. Generally things like names for axes come from Windows – either the driver for the device provides them or the Windows defaults are applied as I recall.
-
As a long time Cougar user I can only say I have never had the issue OP refers to,
-
I will see if i can get some screen shots. Thanks guys, it may take me a few days before i can get back to bms.
-
If you have a problem as a user, I highly recommend chihirobelmo’s Alternative Launcher to make it easy setting up a HOTAS and keeping mappings (just make sure you read about the key text file as it differs from not using AL):
https://www.benchmarksims.org/forum/showthread.php?31774-Falcon-BMS-Alternative-Launcher-(Easy-Setup-Keep-Joystick-Assignments)
