10th command unusable in comm menu
-
I guess I must have missed something : I can no longer use the 10th command option in the comm menu (like “set bingo” or “kickout”), since hitting [0] does not activate it anymore (on an azerty keyboard, it that may matter), whereas [1] to [9] keys do right what you expect them do to.
Does anyone encounter the same problem, or have any idea where this may come from ?
-
@ewildcat
Just curious… is your “0” correctly recognized in the controls setup in BMS? -
@ewildcat Try using your mouse on the tenth command. If that annoys you, try using a voice program like Voice Attack.
-
@ewildcat if it helps remove doubt – it works ok for me (standard US qwerty keyboard layout)
everything in BMS key files is done by “scan-codes”… you will either have to determine which key on your keybd layout is scan-code 0x0B and use that… or, determine the scan-code of whichever key is to the right of ‘9’ and rebind to use that
table of US standard keyboard scan codes:
https://gist.github.com/arithex/3e953d1eb096afe58ce05ba6846493e4I think many EU countries have this problem, with one or more keys… the “forward-slash” to toggle NWS/MSL-Step is a FAQ
at least it used to be … haven’t heard anyone mention it lately.
-
First : thanks for your time. It’s appreciated.
@Amadeus75 said in 10th command unusable in comm menu:
@ewildcat
Just curious… is your “0” correctly recognized in the controls setup in BMS?Good question. I just checked, and yes it is.
@airtex2019 said in 10th command unusable in comm menu:
@ewildcat if it helps remove doubt – it works ok for me (standard US qwerty keyboard layout)
everything in BMS key files is done by “scan-codes”… you will either have to determine which key on your keybd layout is scan-code 0x0B and use that… or, determine the scan-code of whichever key is to the right of ‘9’ and rebind to use that
0x0B is the [0] key too on an azerty (French) keyboard. Which used to work.
Thanks for confirming it still works for you. At least I know I must go on investigating what may be wrong on my own config then.Probably a silly and tiny config problem, that I may even be ashamed of when I find it out.
-
Are you on windows 10?
You can easily change your keyboard language by hitting the “windows key” + “space”.If you change it to, let’s say, English or US… can you check if the issue still persists?
Another thought… have you tried SHIFT and “0”?
I just learned that on AZERTY keyboards you have to press SHIFT to produce numbers, because the unshifted 1-0 keys are needed for the special characters.