Help with Saitek X52 Issue Needed Please!

Hi everyone.
After many years of successful use, something odd happened to my X52 HOTAS yesterday and I need some advice.
At first it appeared the joystick simply stopped working, but it is more involved than that:
- all lights on both throttle and joystick are still on​
- running tests on my computer, all buttons and movements of both throttle and joystick are recognised and within the correct limits on the test page​
- the drivers are updated​
- in the controls section of the game, you can still map every button on both throttle and joystick; you have to use a mouse to enter this section, the joystick buttons normally used do not work​
- changing the cable between throttle and joystick does not fix the issue​
- using a different USB 2.0 port on the computer does not fix the issue​
It is very frustrating, to say the least.
Other information that may be relevant:
- I am running Elite Dangerous Legacy​
- Prior to the issue, I had just remapped my landing thrusters to new keys (up, down, left and right arrows, pg up and pg down)​
- I have not tried uninstalling or reinstalling the game - I do not know if this would wipe out my history or profile, and since I have Elite rank, I cannot risk this happening​
- I have not unscrewed the joystick - the fact that movement is recognised by the computer suggests this is possible not a hardware issue​
Any help or suggestions you could offer would be appreciated; of course, I may have to buy a new HOTAS but would like to be sure that this is not a problem that this would not cure!

Many thanks

Kakapo
 
have you read the lost bind guide stuck at the top of this pc subforum?
welcome to the forums o7
 
Last edited:
If the stick wasn't connected (for whatever reason) when starting the game, this might explain those symptoms. In that case, the game will revert to the basic kb+m setup.
 
have you read the lost bind guide stuck at the top of this pc subforum?
welcome to the forums o7
I have now followed exactly the instructions laid out on the lost bind guide, naming my new binding Kakapo.3.0 and unfortunately the stick still will not work in the game. The HOTAS is always plugged in before starting the game.
However, I did find a message in the bindings folder which may be the cause:
- it is called BindingLoadingErrors​
- it is dated today​
- it says​
"There where errors when loading preset file: Kakapo.3.0.binds
There are multiple entries of binding "MouseGUI" Only the first will be used
There are multiple entries of binding "MouseGUI" Only the first will be used
Missing devices: SaitekX52"

Anyone have any ideas how to fix this?
 
ok somthings not quite right I suggest you backup your current binding folder to some place safe
for now like your desk top
once done delete it from ed
restart the game and a new one will be created see if the x 52 is available in presets or copy an paste a profile to try from here https://edrefcard.info/binds/yovhxm
 
no once you have backed up the folder to your desktop delete it from the game directory
the game should be closed not running
once done and game restarted it will be as if you just installed the game controls wise your progress will not be effected you should then be able to select the x52 fresh from the presets or try one of the many x52 profiles from ed ref card website
 
Last edited:
Missing devices: SaitekX52
That means that, on startup, ED couldn't find your stick (at least at somer point in the past, today). I'd suggest you delete this file (ED will create it anew if necessary) and try to see if it's again created when you start up ED again.
IIRC, the Saiteks also have a reputation for occasionally pulling more power than specified from USB. The ususal recommendation in this case is to run them via a powered USB hub.
 
volts drop across the device will increase with age as contacts get dirty and worn that could cause the stick or throttle to be briefly undetected manifesting in the device being undetected in the binding errors log
which then causes the game to default to keyboard bindings...…….
or worse becomes a corrupt file due to the device being undetected and then overwritten...….
often as mentioned an external powered hub is a quick fix for this on older pc;s where usb milliamp output current may be limited
or a dry soldering joint may have been the cause
how long is a piece of string exactly 🤷‍♂️
still once you have a backed up a renamed file from a working set it should no longer be an issue until the device or pc actually mechanically falls over as any corrupted file can be quickly replaced
the main thing is your back in the game...….
 
Last edited:
Back
Top Bottom