cachiozza Posted March 25, 2016 Report Posted March 25, 2016 When I assign a saitek throttle quadrant lever to throttle 1 and go back to the sim, it immediately puts the spoiler out and reverses the thrust on 1. I can assign it to "throttle" and it works fine. I have deleted all axis in P3D. Any ideas?
wkrp2005 Posted March 25, 2016 Report Posted March 25, 2016 See my thread a few days back: http://forum.simflight.com/topic/81161-saitek-throttle-issues-again/ First off, remove any Saitek drivers. Then, Try this recalibration fix To recalibrate, first unplug the quadrant. Go to start/run and type regedit. The registry editor will have a list of folders on the left hand side. Go down into the following folders in order. HKEY_LOCAL_MACHINE (CURRENT_USER if on VISTA) System CurrentControlSet Control Media Properties Private Properties Direct Input Inside the Direct Input folder, delete any folder that begins VID_06A3. Once done, close the editor. Plug the quadrnat back in and move all the axes through their full range of movement 4 times. Now go to control panel/game controllers/properties to see if everything is ok on the test screen. Finally, what fixed mine was to do what I did in the last post of my initial thread. It has to do both with the Saitek registry and also the dead zones. Good luck
kifp Posted March 26, 2016 Report Posted March 26, 2016 I have the same problem with CH controllers. Not only the throttles going to reverse thrusters, but can't get the rudder working. I thought the P3D v3 problem was resolved. Also I removed FSUICP because of this problem. Today I thought I'd give it another shot, but now the registration won't take my key. I guess I removed too much of FSUIPC. Found a file in the trash (the key), restored it, then my key worked. I still need help with the original problem however.
cachiozza Posted March 28, 2016 Author Report Posted March 28, 2016 How do I remove the saitek drivers?
cachiozza Posted March 28, 2016 Author Report Posted March 28, 2016 I removed the reg entries but still same.
wkrp2005 Posted March 31, 2016 Report Posted March 31, 2016 Did you tweak your dead zones in Windows calibration? I think that's what did it for me. Otherwise, I'm out of ideas.. Sorry.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now