Are all of these key binds hard coded
-
Or is there a way to change some of them?
Thanks.
-
@rcdem
the ones that say “Hardcoded (not changeable)” are hard-coded and not changeable.the others are just intended as “placeholders” to prevent accidentally mapping a key that is commonly used with 3rd party software…
eg. if you don’t use Teamspeak then it should be possible to assign the [NumpadStar] key for use within BMS.
Not sure if the New Launcher allows that in the UI … or if you’d have to hand-edit a key file, to achieve that.
-
@rcdem I’m not sure on the “Hard coded” ones but yes there is a way to make others in green editable. I had the same problem when trying to assign buttons to the QWERTY keys for radio commands.
It’s important to understand that the BMS - Auto keyfile is generated from the BMS - Full keyfile. (The BMS - Full file could be the standard one with 4.37 or one which you may have used from previous versions - note you would have to add the new callbacks from 4.37 to your old file to be up to date).
Make a backup of the relevant keyfiles first.
Then, import the BMS - Full keyfile into the Excel keyfile editor. Then for each one you want to make editable, change the “UI Visibility” from locked or hidden to Visible.
Save the Excel file and export the keyfile and place it in your config file.
Delete the BMS - Auto keyfile (this is important) and it will be regenerated when you restart the Launcher.
Your DX assignments will be added to the new BMS - Auto file as they are stored in the XML files. (You may have to restart the launcher again to see the DX assignments in the BMS - Auto file though.)
You should now be able to change the key assignments or assign buttons to those commands.
-
Great. Thanks for the help guys.