[SOLVED] v4.36 - can't detect keys > 32
-
check BMS manual as you need to activate the 128 support via a parameter set…
-
@MaxWaldorf Thank you! I will look tomorrow
-
Read the manual (Tech Manual section 10 page 10-164 from memory). it says to change the default to 128 using
" a new config option, g_nButtonsPerDevice, which defaults to 32 for backwards compatibility reasons, but users can now set this to a larger value if they want to support more buttons per device".
But: “The config line is not present in the default file”.
I’ve not edited a config file before (and makes me a little nervous). Do I simply insert that line with “=128” at the end? Or is there a simple guide to how to safely edit the config file? -
@viffviff99 you can add the line with any text editor, like notepad, I’d suggest you add it in the x:Falcon BMS 4.36\User\Config\Falcon BMS User.cfg file.
-
@viffviff99 said in v4.36 - can't detect any key above 32:
Read the manual (Tech Manual section 10 page 10-164 from memory). it says to change the default to 128 using
" a new config option, g_nButtonsPerDevice, which defaults to 32 for backwards compatibility reasons, but users can now set this to a larger value if they want to support more buttons per device".
But: “The config line is not present in the default file”.
I’ve not edited a config file before (and makes me a little nervous). Do I simply insert that line with “=128” at the end? Or is there a simple guide to how to safely edit the config file?My knowledge of .config etc is zero, but following the directions in the user manual to add to the user config I’ve been able to implement a heap of stuff, including the 128 option. It’s testament to the guys writing the manuals, especially if I can make it work!
-
@Badger Many thanks for the advice, that’s very useful. Will give it a go.
SOLVED: Use syntax: “set g_nButtonsPerDevice 128” - works a treat!
Boy there is a lot to learn… Probably about as much to learn as the real thing!
-
@viffviff99 I’m new at this and have a Orion with the F16 handle. So I just add that line to “C:\Falcon BMS 4.36\User\Config\Falcon BMS User.cfg”? Right now it looks like this:
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
// User can place here his or her specific configurations lines that will superseed the main ones located in the Falcon BMS.cfg file //
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////set g_nButtonsPerDevice 128
-
@Kumquat yep … if you have more than 2 devices with buttons, be aware you may also need to raise your pinky-shift offset (the default shift-range is 256).
set g_nButtonsPerDevice 128 set g_nHotasPinkyShiftMagnitude 1280 // room for 10 devices
BUT changing that will hork existing key file layouts … eg. all the stock key files are coded with shift-range starting at 256. so you’ll have to update the shifted-button assignments manually, or with Alt Launcher
-
@airtex2019 Ahh ok! Well right now I only have the throttle and a VKB stick. But plan on getting the Cougar MFDs and a Simgears ICP. So should I go ahead and make it 1280 now?
Interestingly, after I edited my “falcon BMS user.cfg” file, I opened the main “falcon bms.cfg” and noticed that this line was already in there:
set g_nButtonsPerDevice 128 // SETUP OVERRIDE
So I guess I didn’t have to add it after all?
-
@Kumquat it is true the latest Alt Launcher sets it to 128 now … I think you’re seeing the result of that
I don’t know, if Alt Launcher has any special ability to track which button-assignments map to which device, and adjust accordingly (incl. pinky-shift magnitude) if/when you plug in new devices.