Hardware & Technical Saitek X52

Cmdr Scorpion

Cmdr Scorpion
I have a Saitek X52 and the pinky trigger has stopped working.
When I go into the USB Game Controlers the no 6 button is working but when I go into the options or game it isn't.

I have tried using it in other settings but for some reason or other it wont register.
Any ideas or suggestions.
 

Asp Explorer

Asp Explorer
Clear any profile you have set in the control panel, make sure it's not set to launch automatically, and the MFD should say Mode 1 No Profile, and everything should work.

If you do want to use profiles - you'll have to completely unbind the pinky.
 

Deleted member 110222

D
Asp Explorer said:
Clear any profile you have set in the control panel, make sure it's not set to launch automatically, and the MFD should say Mode 1 No Profile, and everything should work.

If you do want to use profiles - you'll have to completely unbind the pinky.
Click to expand...

I have the same problem as OP. I'll try this tomorrow.
 

Frameshift_is_Magic

F

Cmdr Scorpion

Cmdr Scorpion
A big thanks to all that answered.
Believe it or not I had a link in my favourites, it is to a post by Cmdr Calaban it is picture heavy but easy to follow all he did was get rid of all but one column in the big spreadsheet and unprogram what you want to work.
I would post a link but don't know how to, sorry.
 
Last edited:

babelfisch

babelfisch
My pinky trigger only works when I run the software simultaneously. I have also something that seems to be polling issues. Reinstalled the drivers ten times but I have given up, I think I am just going to buy a better HOTAS.
 

DaveB

DaveB
Asp Explorer said:
Clear any profile you have set in the control panel, make sure it's not set to launch automatically, and the MFD should say Mode 1 No Profile, and everything should work.

If you do want to use profiles - you'll have to completely unbind the pinky.
Click to expand...

"No profile" is misleading. There is a built-in default profile that has the pinky switch configured as a shift key and the mouse nub, its button and the scroll wheel configured to produce mouse events. It's the same state you see in the profiling software when you create a new profile. To make the pinky a "raw" button you HAVE to use the profiling software to delete pinky-switch shift states and free it up as a programmable button.
 

DaveB

DaveB
babelfisch said:
My pinky trigger only works when I run the software simultaneously. I have also something that seems to be polling issues. Reinstalled the drivers ten times but I have given up, I think I am just going to buy a better HOTAS.
Click to expand...

When you have the control panel open, it forces the driver to pass through all button events, even if the profile loaded on the stick (including the misnamed "no profile" built-in one) wouldn't normally generate them. Yes, it works but it's the "wrong" way to do it. Create a "raw buttons" profile with only the basic 3 modes as shift states and everything else unprogrammed. You can then make it the default profile loaded to the stick on startup.

The kludge of keeping the control panel open comes from the misinformation that "you don't need the profiling software" - sure you can do without it and even use the OS's built in drivers rather than the sticks own, but being stuck with the sticks built-in profile cripples way too much of its capability for that to ever be anything but a sub-optimal state.
 

babelfisch

babelfisch
DaveB said:
When you have the control panel open, it forces the driver to pass through all button events, even if the profile loaded on the stick (including the misnamed "no profile" built-in one) wouldn't normally generate them. Yes, it works but it's the "wrong" way to do it. Create a "raw buttons" profile with only the basic 3 modes as shift states and everything else unprogrammed. You can then make it the default profile loaded to the stick on startup.

The kludge of keeping the control panel open comes from the misinformation that "you don't need the profiling software" - sure you can do without it and even use the OS's built in drivers rather than the sticks own, but being stuck with the sticks built-in profile cripples way too much of its capability for that to ever be anything but a sub-optimal state.
Click to expand...

Thanks, but I already tried that. It worked under 8.1 but since I switched to 10 it just doesn't work anymore. I am going to try it again and report back, but what you described was the first thing I tried IIRC.
 

DaveB

DaveB
babelfisch said:
Thanks, but I already tried that. It worked under 8.1 but since I switched to 10 it just doesn't work anymore. I am going to try it again and report back, but what you described was the first thing I tried IIRC.
Click to expand...

I've got it working on win10. I've still got all the downloads of the software versions that work for me so if you continue to have issues drop me a PM and I'll throw them up on dropbox for you and help out any way I can.

ETA: One issue on win10 is that the stick doesn't play nice with win10 power management. If your machine "sleeps" or goes into low power mode while the stick is connected, restoration of the stick state on resume is severely unreliable, since the stick doesn't reinit cleanly. Replugging the stick or going into the control panel and making inconsequential changes like LED/MFD brightness mostly fixes it but you will still need to reapply any profile - even if the MFD and the tray icon for the profiler both show a profile applied - they are fibbing to ya.
 
Last edited:

BDelacroix

BDelacroix
Be sure you have the x52 flight control system switched on. Mine will be a dumb stick with just a few buttons if I forget to do this. Hat won't work, etc. I have an elite profile for it.
 

FluorescentBlack

FluorescentBlack
So I sometimes have weird issues with my 13 year old X-52 pro, the teamspeak clutch button issue is always a fun one.

Here's what I do and it works every time for me. Lets say we are tabbed out of the game. If open you close the profiler and control panel. Then replug the stick. Open the saitek software control panel ( not nessecarily profiler) and leave it open in the background. Problem solved.

Edit: I read back through thread and it seems the same or simmilar fix was suggested and works.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom