Pinky Shift (DX Shift) stops all mapped buttons working until game restart
-
I hope someone can help, i’m new to BMS so maybe i missing something obvious.
When i press the joystick button assigned to 'pinky shift (dx shift) it disables ALL my mapped joystick functions (though all axis still work).
The only way to get my buttons back is to restart the game (restarting mission does not work)The joystick is X52 pro and i’m on 4.33u3, please help!
Thanks in advance, koppel
-
Do you have both states mapped in your keyfile?
Below example would be using DX 3 button for it.SimHotasPinkyShift 3 8 -2 0 0x0 0
SimHotasPinkyShift 259 8 -2 0 0x0 0 -
Thanks for responding.
So in my keyfile i have the following entries for SimHotasPinkyShift;
line 1082 2 8 -2 0 0x0 -1
line 1136 62 8 -2 0 0x0 -1
line 1168 258 8 -2 0 0x0 -1what that all actually means i don’t know
-
Thanks for responding.
So in my keyfile i have the following entries for SimHotasPinkyShift;
line 1082 2 8 -2 0 0x0 -1
line 1136 62 8 -2 0 0x0 -1
line 1168 258 8 -2 0 0x0 -1what that all actually means i don’t know
I take it looks like:
SimHotasPinkyShift 2 8 -2 0 0x0 -1
SimHotasPinkyShift 62 8 -2 0 0x0 -1
SimHotasPinkyShift 258 8 -2 0 0x0 -1Think that middle one needs to be deleted, SimHotasPinkyShif 62 8 -2 0 0x0 -1, there should only be 2. The 2 8 and 258 8 entries look good.
I would delete that middle line and retest.Edit:
And to clarify, the SimHotasPinkyShift 2 8 -2 0 0x0 -1 tells BMS that is the pinky shift and while held, it will add 256 to DX button count, the SimHotasPinkyShift 258 8 -2 0 0x0 -1 is the shifted state, 2 +256 - the 258.
Since BMS DX assignments start at 0, you are actually using button 3 on the joystick for the Pinky Switch. -
Well i tried deleting the line SimHotasPinkyShift 62 8 -2 0 0x0 -1 and it didn’t work
Also deleted just SimHotasPinkyShif 2 8 -2 0 0x0 -1 and that didn’t work either.
Is there anything to the fact that my lines end in -1 but the manual examples end in 0 ?
-
-1 and 0 are for the audio sound to play on press, neither 0 or -1 being any sound.
The reason none of your buttons work after pressing SimHotasPinkyShift (SHPS to save on typing) is that all of your DX buttons are being elevated by some quantity and those elevated numbers aren’t bound to the callbacks you are used to. If you want a button to activate the same callback regardless of the shift state, you’ll have to make up additional binds for those callbacks at their elevated numbers. For example if you want button 10 to do SimPickle with and without the SHPS button held then you have to bind both button 10 and button 266 to SimPickle.
But the immediate problem you’re having is that the SHPS callback isn’t being released. So you have SHPS bound to joystick button three (2 being the third number). When you activate SHPS it elevates all joystick buttons by a number including itself which is why you need a second bind so that when you release button two fifty-nine (258) SHPS deactivates. Otherwise it gets stuck.
This is a good time to check that the number it elevates buttons by is 256. That’s the most common and default number but it can by any number so let’s check. In falcon bms.cfg look for all line(s) similar to “set g_nHotasPinkyShiftMagnitude 256”. If it’s a different number our assumption to make the second bind as 258 wrong.
Back to SHPS getting stuck on. That has to be some error with the key file. I would go into the .key file and delete all lines which have the SHPS callback except for the one with the " marks. You need that one. Save the .key file. Run the game and specifically load that key file. Then while in the game bind button three to that command. Save the .key file and close BMS. Open that .key file in Notepad and see that the .key file now has a second generated bind due to your previous action. Take this generated bind and paste a copy on the next empty line. Then edit the “2” for button three to its value 258. Save the .key file again. Run BMS and load that key file. Then try it in instant action that SHPS responds to a release.
If that doesn’t work then something is deeply wrong with your game.
-
Mucho thanks guys, i’ve got it working after deleting all the SHPS lines in the keyfile and manually re-entering them, the problem was the 2nd bind was not 256 steps away from the button bind.