nighteyes

in Eyebrowzing's case and mine, it didnt. The registry values point to the saitek drivers, not the windows drivers. Somehow, this seems to be a different calibration.

So its been a year since anybody saw this. I just thought i'd respond anyway since yesterday a buddy of mine had the same exact problem and i spend the last 18 hours solving it. I finally managed to find the solution: What you need to do: uninstall all saitek related drivers/software including the registry entries. From the windows 7 start menu select 'devices and printers' this will show you a saitek x52pro flight control system. Now this is the were the trick lies. If you call up the properties for this controller while the saitek drivers are installed, you get the same control panel you normally see when you call it from the icon in your taskbar where you launch your profiles. BUT, thats not what you need. You need the windows control panel to show. The saitek panel tells you your axis are working fine, just not in the games. So, with the saitek drivers uninstalled, you should get another control panel made by windows itself. This window will show you the same problem you are having in the game with the axis. Now, this panel also has a calibration tab. So suddenly, even though the x52 pro is auto calibrated, you can suddenly calibrate it yourself!. When you calibrate, you'll probably find that some of the axis dont seem to be working at all! Dont worry, just skip over these axis and finish the calibration procedure. After it has finished, all the axis are magically working again as they should be. Now reinstall the saitek drivers and everything should be working just fine again.