Deletion of Joystick button 4.33 U1
-
OK not sure if this is the correct forum or not (if not an admin can move it).
I’ve had this issue for some time with previous versions but I haven’t reached out for a solution as of yet.
Currently running 4.33 U1 and fly with a Saitek X45 using the madcatz software for programming of my HOTAS.
I use my pinky switch as a shift state and in the game the pinky of my joystick is defined as “Button 44” that controls the OSB 12 on the LMFD.
If I use my CMS buttons (Shift-POV 1) I also am hitting OSB 12.
How can I set the pinky switch as “do nothing” in game? The madcatz software will override and do what I want without interference the (hopefully).
I’ve gone into game files to search for a line of code to delete to do what I’m looking for but don’t know what line to augment.
Any help is appreciated.
Best,
-Climber
-
I think if I can remember correctly it would be something like
SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 -0
or something like that
-
I’m not sure if it’s still publicly available to download but I use Keyfile Editor Alpha to make all of my keyfile changes.
-
I was just look looking at this and then I read this post
link to download keyfile editor
-
So I’ve deleted the OSB 12 file and when in the in game configuration screen when I push the pinky switch it only shows button 44. I figured this would be “success”, right?
Even after saving my new file, loading, and applying the changes when in game the same OSB 12 button happens when I press the pinky switch. Frustrating to say the least.
What am I missing. I really don’t want to go with a third party configurator because I use the madcatz stuff and know it well. I just want the pinky to not be enabled in BMS…
Oh, and many thanks to the folks whom have already posted. I appreciate the help.
-Climber
-
Open your key file in an editor and delete the DX-code lines at the end of the file.
They look way different to normal keyboard code lines. You will get which I mean as you see them.
By doing this all DX commands are gone and you just have inputs from your SST programming.