Hardware & Technical Saitek X52 Hotas Problems

[Jetstream]

Hello Everyone,

Just joined this forum and I'm hoping one of you good people can solve my problems. I use my X52 with DCS A10C, I also use the Saitek Rudder Peddles. My problem lies with the axis of the X52; I have calibrated it in Windows and it recognises all the positions. I fire up DCS and one of the missions for the A10C. I have the X52 set up in settings along with the Rudder and then fire up the A10C. I use a runway start, but once I begin the takeoff roll the A/C seems to do its own thing and I need to use a lot of rudder input to keep it on the runway. When I finally get airborne the A/C does its own thing again, rolling from side to side and no way to control it, and ends up crashing. DCS tries to help but they don't know why its happening. I've tried so many things I'm beginning to think the X52 might need to be thrown out. I would appreciate any advice you could send my way. By the way it also happens in P3D.

Thanks,

Alan

 

[duckofdeath]

Is the controller working fine on the x52 control panel? If not, then it's definitely something with it, the drivers or connection.

If it works fine there (the red things moves the same way you're moving it) then it's probably a game setting?
What you're describing almost makes it sound like your control movements are set to add or reduce "turn rate" depending on how much you press each pedal, rather than responding to their current position. Could also be a driver conflict or a lot of other things. Anyhoo, check the control panel first. Also, just in case, make sure both the control panel and the profile editor is installed and updated and that your current profile settings aren't messing anything up.
http://support.logitech.com/en_gb/product/x52-space-flight-simulator-controller/downloads

 

[ziddan]

On my x52pro the ministick mouse is unreliable, sometimes jumping around so ive made a binding for the both whole x/y axis that does nothing through the profiler software and that sorted it.

I also had a problem with my saitek rudder pedals, i was getting bad input from the yaw axis because some internal connections were being stressed by how the cables were routed and the circuit board was mounted, i moved the electronics inside the base and the pedals have been working with the exception of the right pedal sometimes deciding its being pressed a little when its not, thats sorted by temporarily adding deadzone when its acting up.

 

[Jetstream]

The controller works fine in the calibration panel. I've tried game settings but the same thing happens all the time. I have all the latest drivers installed, and even with the Saitek software, or without installed I get the same thing happening. I have even reinstalled Windows 10 thinking that might help, but still the same.

 

[metatheurgist]

I had a bizarre incident with my X52 a few months ago. With the control panel up the stick worked perfectly. With it closed, when I moved the throttle the LEDs would flicker and the stick would randomly reset essentially recalibrating it to the position I was holding it in and throwing out all the inputs.

What fixed it was reinstalling the NVidia drivers with a clean install. Wouldn't have thought that'd be an issue. Dunno if it'll help in your case but it won't hurt to try.

 

[FoxTwo]

Are you running Win10 by any chance? If so, did you just update to the Fall Creator's Update?

The recent Fall Creator's Update (a couple of days ago) resetted quite a number of devices, eg my Logitech gamepad. Had to reinstall a few things to get it all working again. You may have to remove the Saitek software, remove the drivers for the HOTAS, reboot, and redo them again.

 

[duckofdeath]

Just to check, do the rudders work in Elite or do you have the same problem in all games?
Also, like metatheurgist siad, I had a similar issue to that myself a couple years ago. The hotas would only in games if I kept the control panel open. Turned out I had to install the whole software package including the profiler. I guess this is why Logitech has force bundled them in one install as the device doesn't work without it.