X52 stick input scaling incorrect

[Vyper]

Win7 32b

X52 joystick

On first time game spawn in, spawning any AC, the slightest movement (say 5-10% of full stick movement in Y for example) will cause full scale elevator movement. Moving the stick more than 10% will cause such violent ups and downs as to cause instant loss of control.

You can watch, looking back at tail, the slightest stick input causes elevators to move full scale. The game ACTs like it is input x10, with no set limit.

IF the stick is moved while the plane is still in the hangar to full limits, the game then re-scales stick movement correctly.

Please fix. Thanks.

[lutorm]

This has nothing to do with the game, it's the X52 auto calibration. When you turn it on, it doesn't know what full scale deflection is, so it will assume that the largest you've moved the stick must be full scale.

Solution: always deflect all axes fully before starting. Think of it as your preflight check...

[Vyper]

This has nothing to do with the game, it's the X52 auto calibration. When you turn it on, it doesn't know what full scale deflection is, so it will assume that the largest you've moved the stick must be full scale.

Solution: always deflect all axes fully before starting. Think of it as your preflight check...

Yes....you MUST be correct. Except it has nothing to do with ANY other game I play, the saitek control panel where I can watch my inputs in real time, or BGE pre 1.31.... 1.30 to 1.17

So, leave your guessing out of my thread.

[lutorm]

Yes....you MUST be correct. Except it has nothing to do with ANY other game I play, the saitek control panel where I can watch my inputs in real time, or BGE pre 1.31.... 1.30 to 1.17

So, leave your guessing out of my thread.

What makes you think I'm guessing? You must have another x52 than I do because my x52 has done that in every version since I got it...

[Vyper]

What makes you think I'm guessing? You must have another x52 than I do because my x52 has done that in every version since I got it...

You work for saitek?

You work for CRS?

No. You don't.

You are guessing because

A), you are not a software engineer.

You are not even good at troubleshooting issues.

It's NOT a saitek issue. If it was, it would be windows dependent, not BGE dependent. I.E., it issue would show itself on a windows reboot ONLY if it was a saitek cal issue as you stated. It does not, it shows itself on BGE restarts, and only since 1.31.

You wanna keep posting in this thread, post some links to support your babble, or stfu.

[lutorm]

You wanna keep posting in this thread' date=' post some links to support your babble, or stfu.[/quote']

Just some friendly advice: lay off the attitude if you want people to help you.

I don't remember telling you what my profession is... but whatever, enjoy your problem.

[fujimo]

This has acutally been happening to me for as long as I have had an X52.

[Vyper]

Just some friendly advice: lay off the attitude if you want people to help you.

I don't remember telling you what my profession is... but whatever, enjoy your problem.

sweety stfu.

[Vyper]

This has acutally been happening to me for as long as I have had an X52.

This has only been an issue for me since 1.31. I've been using the X52/X52 pro for over 5 years.

No reply yet I take it?

[beazil]

Never had the forethought to look for this before- hence my bouncy nose thread in the hanger as I use an X52 pro as well. Not a solution to your problem Vyper, but a Ty for letting me know to watch for the problem.

[ghostrider]

so once you go through full range of motion it recalibrates correctly?

I have a x52 and havent noticed this before..I'll check next time i log in. I can't really see this being much of a problem except for take off.

[Tigger6]

I have had the same problem occasionally on takeoff (normal pull back on the stick will affect the airplane as if I yanked it back) and it's good to know that I'm not insane.

[Solono]

I had a similar issue, but with my aileron control, here is how I solved it:

While spawned in, unplug the X52 then plug it back in. Scaling was fixed.