X52 DirectX Pinky Shift not working
-
I am trying to program my X-52 (non pro) using Kolbe’s keystrokes file and the BMS-DX-Generator 1_6.xls spreadsheet. I have the Stick pinky button programmed with the dx command SimHotasPinkyShift but it is not working in the game. Any ideas what I could be doing wrong?
-
Check the Saitek SST software and see if the key you’re using for the pinky button is marked ‘latched’. If it is, unlatch it.
-
I bet it’s a wrong assignment of the Pinky Shift on the shifted layer.
You have to set the callback SimHotasPinkyShift in both (!) layers.So one in unshifted layer (e.g. btn. # 3) and in the shifted layer (3 plus shifting magnitude, default is 256 -> so btn. # 259)
If this doesn’t work you can post your key file here and I’ll have a look.
In this case please drop me a pm as I am not checking this forum on a daily basis but get a mail when pm’ed…
-
Are you testing in flight or in the UI? Shifted commands are not displayed in the UI. I’ve lost some time to this in the past.
-
The button in the SST software is Unlatched. I have set the pinky shift in both layers and it is not working in the game.
-
The DX part of your key file is ok as far as PinkyShift is concerned.
Have you checked if the button itself is working correctly?
What about the other functions? Are they working as expected?As already mentioned above, just test in 3d. UI does not display shifted commands.
-
Yes other functions work ok. I know the pinky button works ok checked in SST software and it worked before with other profiles in BMS. Only problem seems to be shifted functions aren’t working. Also how do I map the mini stick to the TDC cursor? SST? Can it be done in DX or in game?
-
Found this in another post…
There are two kinds of shift available for X-52: using SST software with up to 6 modes based on mode1-2-3 and shift layer or using SimHotasPinkyShift which changes all input DX numbers by 256.
Because your shift is getting stuck I assume you are using SimHotasPinkyShift. In your *.key file you must have SimHotasPinkyShift three times. Yes three times. The three lines are:
1. Keyboard line that has text label in quotes
2. Joystick line that is activated by joystick button ID
3. Joystick line that is activate by joystick button ID+256Here is an example:
SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 1 “Pinky Shift +256”
SimHotasPinkyShift 2 -1 -2 0 0x0 0
SimHotasPinkyShift 258 -1 -2 0 0x0 0You press button 3 (remember button 1 is 0, button 2 is 1, etc.) and you get SimHotasPinkyShift command. But how do you release it? Once you press the button it raises the DX id number for all buttons. You cannot release button 3 because you no longer have button 3! What used to be button 3 is now button 259. So you also bind the callback to DX ID 258 so when you release the shift button it is releasing button 259 and the SimHotasPinkyShift command can be stopped.
Could this have something to do with my problem?
-
@16th:
Found this in another post…
There are two kinds of shift available for X-52: using SST software with up to 6 modes based on mode1-2-3 and shift layer or using SimHotasPinkyShift which changes all input DX numbers by 256.
Because your shift is getting stuck I assume you are using SimHotasPinkyShift. In your *.key file you must have SimHotasPinkyShift three times. Yes three times. The three lines are:
1. Keyboard line that has text label in quotes
2. Joystick line that is activated by joystick button ID
3. Joystick line that is activate by joystick button ID+256Here is an example:
SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 1 “Pinky Shift +256”
SimHotasPinkyShift 2 -1 -2 0 0x0 0
SimHotasPinkyShift 258 -1 -2 0 0x0 0You press button 3 (remember button 1 is 0, button 2 is 1, etc.) and you get SimHotasPinkyShift command. But how do you release it? Once you press the button it raises the DX id number for all buttons. You cannot release button 3 because you no longer have button 3! What used to be button 3 is now button 259. So you also bind the callback to DX ID 258 so when you release the shift button it is releasing button 259 and the SimHotasPinkyShift command can be stopped.
Could this have something to do with my problem?
Possibly. You should already have the last two lines …. I think you indicated you did in a post above.
@16th:
…. I have set the pinky shift in both layers and it is not working in the game.
Unless, there is some problem with the DX button number assignments (2 & 258 above …. yours may be different. In my keyfile, they are 5 & 261).
Adding the first line is basically adding the shift key command with no key assigned (0XFFFFFFFF), so there is absolutely no reason not to add it and try it.
Edit:
In my keyfile, I do have the keyboard command also … “SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 1 “HOTAS-Pinky Switch””. Basically the same as what you quote. Keyboard command with no key assigned.
-
Yes mine are also 5 and 261 I will try adding the line to my keyfile. Is there anywhere in particular I should place the line?
-
No, it really doesn’t matter where it is in the keyfile as long as it’s in the keyboard command area (top 2/3rds of the keyfile; DX keys are the lower 1/3rd …. give or take).
-
Still not working
-
Are you testing in flight or in the UI? Shifted commands are not displayed in the UI. I’ve lost some time to this in the past.
Hahahahaaaaaaaaaaaaaaaa (expires). I was up till 5am last night trying to sort this one out; checking and rechecking etc. Was about to scrap my keyfile and start again until I read this and immediately went in game to try the shift button. Result: everything works perfectly :facepalm:
Still, it wasn’t all wasted. I had a very good read of kolbe’s .pdf and this forum post and finished off a nice bottle of port
-
I’m wondering if there’s been a resolution for the OP…I’ve got the same issue [emoji848]
I’ve only mapped a couple functions in the SST, got the radar cursor functional as well as speed brakes mapped to the slider. The only issue is I am only able to use the unshifted commands. This is like the last conundrum to solve before I can actually fly the sim seriously [emoji30]
Any help would be appreciated…y’all have already gotten me farther down this rabbit hole than I anticipated it would require…but hey it’s worth it right?..right…?
-
Also in your falcon bms.cfg file, there needs to be “set g_nHotasPinkyShiftMagnitude 256”. This Enables DirectX Shifting and specify button offset.
-
Also in your falcon bms.cfg file, there needs to be “set g_nHotasPinkyShiftMagnitude 256”. This Enables DirectX Shifting and specify button offset.
This is already in the config file under “Misc Settings”. Does it need to be in any other place?
-
This is already in the config file under “Misc Settings”. Does it need to be in any other place?
No. Anywhere in the config file is fine.
-
Well, evidently it’s not fine ha
Not sure where else to go with this. Thanks for the replies
-
Well, evidently it’s not fine ha
Not sure where else to go with this. Thanks for the replies
You saw it, Lord, dear: https://www.benchmarksims.org/forum/showthread.php?26713-BlackHawk-s-Saitek-X52-Keyfile-DX-Profile-for-BMS-4-33/page2
-
Yeah that post is familiar. It helped me setup/edit my key file.
But again, no shifting as of yet…I guess it’s back to DCS for a while lol