X52 Deadzone Problem.

Hi,

I am having a strange problem in game with my X52 Hotas.

The joystick vertical axis is behaving as if it has a large dead zone in the middle of the movement, yet in the configuration software, it reacts without a problem, no deadzone.

Has anyone else come across a problem like this as the other axis works perfectly.

From that, I assume there may be something wrong in the game perhaps?

Thanks,

Martin
 
If I understand you right, I had the reverse problem, where no deadzone seemed to be set, despite configuring it in the driver software. You might try tinkering with the deadzone in the game settings. This worked for me.
 
Hi Jo,

Thanks for the reply!

The sensitivity settings in the game does not appear to move for me for some reason?

I might try the X52 control scheme tomorrow and see if that works better as I am using a custom scheme but why that should only affect one axis is beyond me...

Martin
 
Definitely worth checking them both out and setting one to off. Just to rule out more irritating variables. My 56 throws a wobbly sometimes too, but I've not had the issue you describe.
 
The x52 does not play nice if you have it plugged into anything other than a USB 2.0, might be worth checking that to start with.
You say you have checked the inputs from the HOTAS using the configuration software, i take it that was using joy.cpl.

When i have had issues with my x52, either odd deadzones, or strange axis drift, i have found that unpluging and reconnecting the joystick from the throttle usually solves the problem.
 
Hi,

Thanks for the reply!

I am using the Saitek control software supplied with the X52.

I agree, unplugging then replugging solves the drift problem.

The USB port is USB 2 directly into the pc.

This is a very strange problem that I have not had before so I'll keep looking for a solution.

Martin
 
Hi,

The problem is almost solved, it appears to be a problem with the custom.3.0.binds file!

When I use the Saitek X52 pro binds file the joystick is fine, all I have to do now is to determine what changes are needed in my custom binds file to mirror the vertical axis in the X52 binds file.

Martin
 
Yep i have a x52 pro, had a similar problem, i ended up having to mess with the dead zone outside of ED, under windows game controller. It had a wee bit of a drift in it so i just gave a bit of dead zone for it, and bobs your uncle it worked fine.

The real issue i have is if i take a break form ED for like a month and comback, some of my keybinds just randomly get unbound.
 
That's right, now before I play the game I check the controls haven't been altered.

In this case, it was the pitch axis that was getting unbound for some reason?

Martin
 
I sometimes have an issue with deadzones acting weird. I unplug and plug in again the stick and it straightens out.
If I recall the stick uses hall effect sensors. Can those get dirty?

Drift is what I get sometimes. The unplug/plug fixes that for me.
 
Last edited:
The x52 does not play nice if you have it plugged into anything other than a USB 2.0, might be worth checking that to start with.
You say you have checked the inputs from the HOTAS using the configuration software, i take it that was using joy.cpl.

When i have had issues with my x52, either odd deadzones, or strange axis drift, i have found that unpluging and reconnecting the joystick from the throttle usually solves the problem.
Ah this is true. You need the higher power throughput of the usb 2 plug. Most of my controller weirdnesses went away when I moved it to the blue plugs.
 
Beware that there are two ways of binding some axes. I don't remember whether pitch has these two, but I had the behaviour you describe once with yaw.

I'd bound "yaw left" to left stick twist and "yaw right" to right stick twist. This gave a digital behaviour with a large dead zone.
Instead, the right way is to bind "yaw" to "twist" in just one entry in the Controls menu. This gives proportional control.
 
I build my own controllers so here's a little advice.

The very first thing to do with a controller is calibrate it.. Windows options USB devices. Only then can you start using the other software that comes with the controller if any. In most cases, the controller software can be dumped in the bin. But if memory serves for the saitek controller you have to turn something off for the pinky to work.

In games, there should ways be a deadzone slider where you can tell the software to ignore the first percentage of the stick movement. This 'play' can be form the actual device construction, ie, worn plastic, or a worn/cheap potentiometer. In any case, you are telling the game to only take input as movement once the analog signal reaches a certain value above 0.

TL;DR: calibrate first then mess around in game deadzone sliders.
 
Back
Top Bottom