Newbie MAY have something to contribute.

[Lowboy]

I *MAY* have something that could help someone else like it helped me....I didn't notice this info anywhere else but I am just learning the sim and my way around this forum after lurking here for several weeks......

 

Among the many, many, many problems I have had in learning this sim has been the poor and/or over responsiveness of my X52. Trim just seemed to make it crash faster and it was not predictable how far the stick needed pushed one time to trim it as opposed to the next to get the same result.

 

...something wrong.....

 

....axis tune showed cyclic y off center and very jittery.....cyclic axis x centered but "slewed" at an angle instead of a straight line when pushed (if that makes any sense). Basically, i think my calibration was off and I couldn't find any way to fix it besides deadzones, saturation, positive s-curves, etc etc.....i even tried the DX Tweak and a logitech calibration tool found on this forum deep down there somewhere.....this is a NEW X52....shouldn't be this way, i thought. I haven't had to *calibrate* a joystick since windows 95 and the FIRST Jane's Apache sim.....

 

anyways.....

 

a google search determines this post on "Flyaway" forum at

 

http://flyawaysimulation.com/postlite25404-.html

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Your problem is your registry.

 

I had this problem and it took some time to figure it wasn't anything I could have fixed easily. The following is an excerpt from a Saitek email.

 

In some cases, the calibration for the controller may be off. This may be an issue with a corrupted initial calibration of the controller. The following instructions involve changes to the Windows Registry. The registry is a very sensitive part of Windows and removing or editing the wrong value can cause a multitude of problems. See about making a backup of the registry before proceeding. In case you screw up! Do the following at your own risk! But this worked for me and within ten minutes my x52 was working.

 

click Start, and Run. Type in "regedit".

 

- click on the plus sign next to " HKEY_LOCAL_machine"

- click on the plus sign next to "System"

- click on the plus sign next to "Current ControlSet"

- click on the plus sign next to "Control"

- click on the plus sign next to "MediaProperties"

- click on the plus sign next to "Privateproperties"

- click on the plus sign next to "DirectInput"

- Look for keys starting with VID_06A3 and delete them.

- Close the registry editor by clicking on Registry at the top then click exit.

- Reboot your machine.

-Recalibrate the controller by twisting the joystick, then rotate it around several times.

~~~~~~~~~~~~~~~~~~~~~~~~~~

 

It worked for ME!! All my deadzones are centered, no jittery axis anywhere, completely centered and normally responsive and trim is a WONDERFUL THING now....no wonder everyone here is so happy........it was like trying to fly the helicopter drunk, i think....now i can finally get down to learning stuff.

[26-J39]

Thanks for the info :thumbup:

[Feuerfalke]

Interesting. This can definitely be helpful for a lot of people - thanks for sharing.

[Shaman]

Good! though I don't use Saitek system, this could be moved to problems and bugs and named properly. So it is easier to find.

[Kirai]

Thanks for sharing! :)

 

I have been playing with my x52 for a long time now and when I read about your problems I think I have the same problems and I didn't start to notice until a couple of days ago when I started to play FSX again. Every plane I try to take off with drag to the left on the runway and to calibrate didn't help at all. When I think of black shark I know my heli also drag to the left on start but I thought this was my fault with bad trimming so I have got used to it by pushing slightly to the right and trim.

 

I will try this out but I will change my system anyways hopefully this week to the logitech G940.

 

Thanks again :)

[-Painter-]

Thanks for sharing!

 

I have something to add:

Before editing the registry, try to reconnect the cables between stick and throttle!

A few days ago I experienced the same problems as described in the first posting. My problem was that the cable-plug was a little loose. Reconnected and everything was fine again.

[RealDCSpilot]

as far as i know, this is also the workaround to get FFB working on the saitek cyborg evo force running under vista. it stops other ffb-devices or older installations from interfering.