I have a problem with my trusty old Saitek Cyborg Evo. A while ago I wanted to play IL2 Sturmovik again. Installed everything, plugged in my Evo and started. Unfortunately, something was wrong. The nose of my plane was pushed down. Took a look into the settings and yes, in neutral position of the stick the game thought I would push the stick forward. In the game the input for the y-axis was at neutral position when I pulled back the stick about 50%.
I thought the stick was broken, which would be ok, this thing is way over 10 years old. But I took a look into the calibration options of Windows, I use Windows 10. There, everything was ok. Neutral position, everything was working fine. I tried the stick in another game (Kerbal Space Program) and the stick was working fine.
So I thought it must be a problem with the game, translating the input wrong.
Then I stumbled over this tool here (http://www.xedocproject.com/joystickcurves.html) and decided to try it. As far as I could see, it emulates virtual game controllers so you can modify the input translation. Wouldn't work for my problem as I found out, but the interesting thing was, that I had the exact same behavior like in the game. The tool has a windows where you can see how your input translates, and there, in neutral position of the stick, the program also thought that I pushed the stick forward. So I thought, there must be more to it.
I hope you could follow me so far. Here are some screenshots of this tool (Joystick Curves), so you can really see what I mean:
Stick in Neutral Position:
Stick pulled back 100%
Stick pulled back 50%
Stick pushed forward 100%
As you can see, the Y-axis just translates wrong here, and I have the exact same behavior in IL2. All other axis are working fine, everywhere, even in IL2.
Like I've said, in other games the stick is working fine. In Windows calibration options it looks like this:
Stick in Neutral Position:
Stick pulled back 100%
Stick pulled back 50%
Stick pushed forward 100%
So the stick itself seems to work fine and the problem doesn't only exist in this one game. Are there different methods how the input of such a device is translated into the computer? So that Windows calibration and KSP uses method 1 and the other tool and IL2 uses the other method? Is there something like this?
I installed the latest Saitek drivers (at least the version for Windows 8, because there is no dedicated driver for Windows 10). The joystick is connected via USB. Seems to make no difference if I use USB2 or 3, no difference in using the front slots of the case or the build in slots of the motherboard. I have used the stick with this game before, but years ago in another version of the game and on another windows version.
Do you have any idea what could cause the problem and more important: how I can fix it? I really don't want to give up my old stick =)