Saitek X sticks and programmable mice conflict
-
There appears to a a conflict generated between the Madcatz / Saitek HOTAS and R.A.T. mice (programmable), they both use same software to program and the mini mouse on the Saitek X52 Mk1 stick starts the mouse off on its merry way all over the screen.
Quick fix, add a stick profile to change the mini mouse stick from a mouse to the Bands settings, makes it effectively into a four way switch.
I have tried it with a Logitech 7 button programmable mouse as well and had the same issues which are more likely to be in the X-52 driver files than the software.
-
A better fix is changing the mini mouse stick into a pair of DirectX axes. Got a .reg file that does that kicking around somewhere. means you actually get decent resolution on your cursor.
-
Thanks for that Blu3wolf, the problem actually turned out to be a conflict between Teamspeak 3 and Saiteks drivers. The cure to it all was to make TS3 just work via the Keyboard and Mouse. This can be set in the HOTKEY section of the Options in settings for TS3. It gets rid of all Saitek profile conflicts. The idea of yours is the default for the SAITEK HOTAS of whatever flavour if they have the mini mouse toggle on them. Hence why I went to bands to basically make a Cage mover for the minimouse. Band it it splits the scope of the movement into 3 sections, with a fallback into the centre section which ive set to softlock whatevers in the gate or crosshairs at the time, then use another button to upgrade the lock if needed.
Good advice though as not all HOTAS default to X and Y axis on mini mouse.
-
Thanks for that Blu3wolf, the problem actually turned out to be a conflict between Teamspeak 3 and Saiteks drivers. The cure to it all was to make TS3 just work via the Keyboard and Mouse. This can be set in the HOTKEY section of the Options in settings for TS3. It gets rid of all Saitek profile conflicts. The idea of yours is the default for the SAITEK HOTAS of whatever flavour if they have the mini mouse toggle on them. Hence why I went to bands to basically make a Cage mover for the minimouse. Band it it splits the scope of the movement into 3 sections, with a fallback into the centre section which ive set to softlock whatevers in the gate or crosshairs at the time, then use another button to upgrade the lock if needed.
Good advice though as not all HOTAS default to X and Y axis on mini mouse.
Well no, actually, its NOT the default for all Saitek HOTAS, which is the reason I made it in the first place. The X-65F for one and the X52 I have both do not declare their axes to directX by default.
-
Blu3wolf would you be so kind to send me your reg file for my X-65F please ?
Thanks Jamie.
-
No worries Jamie, you can find that file at http://falcon.blu3wolf.com
Right click the link and save the file, then as with all .reg files open it with a text editor to see what it does, as these are entirely capable of messing with your computer. This one doesn’t, but you shouldn’t be in the habit of adding random entries from the net to your registry anyway.
Once you’re satisfied its not intended to screw with your PC, double click the file to add its contents to your registry.
Heads up that its not been tested with Windows 8 and I have no idea if that will make a difference.
End result should be that your X-65F will No LONGER HAVE A TWIST RUDDER, but will gain a pair of new DirectX axes mapped to the ministick on the throttle. Max of 8 axes without messing with extended virtual joysticks, and the X-65F already has 7, so one has to go.
Its possible to change which axis is removed, by editing the file; I chose to get rid of the rudder as I have rudder pedals and twisting a force sensing stick doesn’t work too well.
Let us know if it works for you, or if you have any problems with it!
EDIT: Has now been tested on windows 8, works precisely as before.
-
Blu3wolf I have bookmarked your site I will have a nose later, looks interesting.
Will post back after the weekend when I have had a play with the reg file mode.
Thank you Jamie.
-
Works great Blu3wolf many thanks Jamie.
-
Glad to hear it Jamie!
-
Is there a registry edit for the x52pro mini-stick? And if so does it mess with rudder twist as well?
-
I did have such a file kicking around, but its not on the site… I will have to have a hunt for it and get back to you.
-
Couldnt find the original file, so I sat down and wrote one.
Link is now below the X65F file. This file WILL remove your twist rudder, but it will enumerate your ministick as a pair of directX axes so that you can assign them in game - for example to the radar cursors.
This file is for the regular X52, and will not work with the X52 pro. If you have an X52 pro and want this mod for that joystick, let me know and Ill get some details off of you to set it up.
EDIT: I just realised that you said you had an X52 pro…. shows I should be paying more attention! I just need to know a short registry key to make the file, and it might take a little trial and error to set up as I dont have an X52 pro to test on. The edit is reversible, and it is configurable - you can remove a different axis to the rudder if you need to keep the rudder pedals - however DirectX only likes 8 axes per device and counting the ministick axes, there are 9. X, Y, Throttle, two rotaries, the stick axes (2 of them), the twist rudder and the slider. Gotta lose one to have both cursor axes.
EDIT II: Thanks to TxMtb’s generous help in posting the corrected file for his X52 Pro, you should be able to get up and running!
Ill post a link to the file in a tick.
-
Same link as before, bottom right. Save the link and run it to add a bunch of entries to your registry. Once again, these entries dont mess with your PC but they will remove your twist rudder in exchange for giving you the mouse cursor as directX axes.
-
thanx wolf, i’ll give it a go.