December 22, 200916 yr I am using a Saitek X-52 Pro joystick with Pro pedals. Recently a maid thought it would be easier to dust my desk if she unplugged my USB cables. Needless to say, they have been re-arranged. What is the remedy?My callibration seems normal on the test page, but in FSX my throttle never gets lower than 1% and never higher than 98%.Donald Traill
December 23, 200916 yr I am using a Saitek X-52 Pro joystick with Pro pedals. Recently a maid thought it would be easier to dust my desk if she unplugged my USB cables. Needless to say, they have been re-arranged. What is the remedy?My callibration seems normal on the test page, but in FSX my throttle never gets lower than 1% and never higher than 98%.Donald TraillDonaldIn the Sim under Settings\Controls check that your sensitivities are full right (100) for all axes and null zone is full left (0) for all axes and that you have no duplicate assignments. I use FSUIPC4 to assign and calibrate my X-52 and it is so easy and "more accurate" than FSX. I don't use the SST software. PS I always mark my USB ports and match them to the same controller - saves hours. BTW the Butler did it! :( regardsPeterH
December 23, 200916 yr Are you using the Saitek drivers? If so you might check the Saitek support forum, I think they have a procedure which involves unplugging, removing the calibration entry in the registry, reconnecting and moving each axis through complete range, and the driver is supposed to "auto-calibrate".scott s..
December 24, 200916 yr Thank you for the replies. All null zones were zero and sensitivities maxed before I posted... shoulda said. I have checked for duplicate entries and deleted them... and deleted them... and deleted them. They keep re-appearing.I will check out the Saitek forums.Donald
December 24, 200916 yr Oh, I had this problem too (except that it was me who plugged the devices into whichever USB ports, not the maid ). I found that reinstalling the driver (over the top of the previous installation) with the device plugged into the 'new' port rectified the problem, and didn't stop the 'previous' USB port from working either. So in the end, I just reinstalled the driver with each component plugged into each USB port (including different ports on a hub), so that now any port works fine.
Create an account or sign in to comment