BMS returning the wrong key bind?
-
Hi guys,
So I have been going through a functions test on buttonology since picking up the game again after a long break and I have come across a serious issue that I cant seem to fix, see details below:-
My X52pro editor reads my stick POV hat (L/R/U/D) as Num7, Num8, Num5 and Num6 respectively (this is correct and as it should be for my set up).
-
BMS settings show those num keys set to DMS L/R/U/D, again, this is correct and as it should be for my set up.
-
When I type those num keys into word (function test) they work as described.
-
When I use my stick POV hat in word (function test) it types those num keys into word, they work as described.
-
[The problem] When I use my stick POV hat OR the num keys directly in the BMS controllers setup page or in the game, these keys do not work. Instead - they show the the button press as SHIFT num pad (7,8,5,6) whether I use the stick POV hat or the keyboard inputs.
This only happens when the stick is set to MODE 1 (I have 3 modes with slightly different set ups). The stick POV hat in question works correctly when in mode 2 (mode 3 has not function set).
I would also add that this set up worked fine before 4.33-1.
CAN SOMEONE PLEASE HELP!!!
-Sharpe
-
-
I guess you didnt bother to try in the game, then?
Its a known bug with the setup page, detailed in the changelog for 4.33, that the num pad keys are incorrectly displayed in the setup page, as having the SHIFT modifier, even though they dont. This is only in the setup page, and the keys will still work correctly in the 3D, even though they appear incorrect in the setup page.
-
Happens in game too (as mentioned in original post). It’s an old profile that has worked before so I was in game when I noticed it was not doing what it should have been.
-Sharpe
-
Stop using software for keypress emulation for any/all HOTAS functions. Use DX instead.
If you need help with DX commands in BMS, hit me up on PM and/or on the wing TS server.
-
Did you set up the bands function? That did the trick for me
-
Did you set up the bands function? That did the trick for me
Should not need bands for POV Hat for DMS Up/Down/Left/Right.
-
true: I was thinking of being able to manipulate the FCR. Guess I read it wrong
-
Did you set up the bands function? That did the trick for me
Hey Buster,
You are not the first person to mention DX only for HOTAS. If i cant find a fix i will have to bite the bullet and move over, but i will cling to the fact that it worked in 4.32 and 4.33 its just gone wrong in 4.33-1 and maybe there is a fix.Thanks for the help so far everyone. To be honest, moving over to DX is a last resort for me (agro of set up, loss of profile, old dog new tricks etc).
However, I am particularly reluctant to change it as the game cant even get it right when I use the direct keyboard press for the desired commands, even when I press num7 etc, it still thinks i am pressing shift-num7. This is the part I find particularly frustrating as it suggests (to me, the technophobe) that there is nothing wrong with the stick or the profile at all, but rather something odd in the BMS code?
-Sharpe
-
Guys,
New update:Numpad keys 0-9 and decimal/delete are returning as being ‘shift’ 1-9 and .
No other keys are showing this issue.
Regards,
-Sharpe
-
As mentioned earlier by someone, this is a known bug and will be fixed in the next update.
Note: It’s only showing a wrong output in the controllers page. In game aka 3d it works flawlessly. -
As mentioned earlier by someone, this is a known bug and will be fixed in the next update.
Note: It’s only showing a wrong output in the controllers page. In game aka 3d it works flawlessly.As I have mentioned this is NOT the case the issue is in game too.
-
I spoke to a friend of mine who is part of the BMS test community. The following was found:
-
Direct X is better, but it’s not the cause/fix for this issue.
-
The fault is in part known and will be fixed.
-
What I found was that the num pad numbers 0 through 9 and decimal/del were all being listed by BMS as having a shift key being pressed when this was not the case. They were the only keys on the keyboard showing this behaviour and it was the same in sim and out of the sim whether I used a direct keyboard press or a mapped keystroke via my x52pro. It was entirely reproduceable as it was a persistent issue.
-
There are two work arounds:
a) Don’t use the numpad 0-9 and decimal keys in your profile (or re map them if your profile already uses them).
b) Map direct X buttons. This will ONLY fix the problem if the keys you want to remap as direct X happen to be the numpad 0-9 and decimal keys, otherwise the problem will continue as it’s the way BMS is reading the keys that is causing the problem.
Hope this helps. Thanks everyone for pitching in to help .
-Sharpe
-
-
Moderator please delete, re posted in error.
-
As I have mentioned this is NOT the case the issue is in game too.
Let me guess, you have edited and saved the key file in the BMS UI.
Of course the shift modifier is saved as well then.Try the default key files: UI -> bug, 3d -> ok
-
“b) Map direct X buttons. This will ONLY fix the problem if the keys you want to remap as direct X happen to be the numpad 0-9 and decimal keys, otherwise the problem will continue as it’s the way BMS is reading the keys that is causing the problem.”
Map keyboard inputs as DX ? (Direct input)
I use the NUMpad for ICP with out any problems, and if memory serves me that is the default.
OK, i see its the setup page that is reporting incorrectly.