Hi all, I just completed reinstallaion for FSX and all add/ons with Windows 7. This all looks good. Whats happening now is that my rudder and nose steering is all messed up. I'm using a reconditioned Saitek X52 thats been working fine for more than a year, but the problem just started a day or two ago after reinstalling FSX....The calibration of my X52 stick works perfectly fine thru Windows control panel and thru FS. The rudder moves fine in both directions and all other axis is good. Incidentally, the calibration seems to work much better now than before...The PROBLEM is while in FS and regardless of what aircraft I use, the aircraft veers to a hard right turn when taxing or flying. This is not the case when Autopilot is engaged. What's also noticeable is that the rudder is stuck in the right position. When the aircraft is not taxing the wheel is straight but the rudder is to the right. When I start to taxi, the rudder stays to the right but the wheel veers hard to the right ...I tried to calibrate the rudder in FSUIPC (Latest and registered) but FSUIPC could only calibrate and recognize the rudder left position, not the right. This is very difficult as I'm not sure the problem is My Saitek stick or FS itself...I even tried an older version of FSUIPC but still no change. Unfortunately, I have no other games I can test the stick with. If someone has a clue to what the problem could be, your help is greatly appreciated. Thanks

TroyA couple of points:1) Make sure that you have NO duplicate axes assigned in FSX (and/or FSUIPC4) - very important. If you assign an axis, etc in FSX then you should NOT asign the same axis in FSUIPC4)2) In FSX make sure that for ALL axes the sensitivity is full right (100%) and the null zone is full left (0%) Note There are "hidden axes in the dropdown boxes.3) In FSX under settings REALISM start off with all "Flight Model" set full left ie "EASY". You can then change these as you get more experience.4) For Taxiing only delete the rudder axis (I guess you are using the twist grip?) in FSX and assign it to the tiller in FSUIPC and see if you have any issues when taxiing (Note this will disengage above 60KTIAS)RegardsPeterH

TroyA couple of points:1) Make sure that you have NO duplicate axes assigned in FSX (and/or FSUIPC4) - very important. If you assign an axis, etc in FSX then you should NOT asign the same axis in FSUIPC4)2) In FSX make sure that for ALL axes the sensitivity is full right (100%) and the null zone is full left (0%) Note There are "hidden axes in the dropdown boxes.3) In FSX under settings REALISM start off with all "Flight Model" set full left ie "EASY". You can then change these as you get more experience.4) For Taxiing only delete the rudder axis (I guess you are using the twist grip?) in FSX and assign it to the tiller in FSUIPC and see if you have any issues when taxiing (Note this will disengage above 60KTIAS)RegardsPeterH

PeterH, Thanks for your help. I followed your suggestions and here it is:1)no duplicates assigned. In fact i renamed FSX.cfg and had FS rebuild a new one...same issue2)Done...no change3)no change....also this was the case even after installing a fresh copy of FSX and no add/ons...Not even FSUIPC and no configuration and or assignment of Joystick4) Deleted the rudder axis (Z Rotation) but no change; Im am using the twist grip...Twisting to the right is not recognized in FS; The tiller? Would that be the same for Joystick calibration under FSUIPC....If so, no change

PeterH, Thanks for your help. I followed your suggestions and here it is:1)no duplicates assigned. In fact i renamed FSX.cfg and had FS rebuild a new one...same issue2)Done...no change3)no change....also this was the case even after installing a fresh copy of FSX and no add/ons...Not even FSUIPC and no configuration and or assignment of Joystick4) Deleted the rudder axis (Z Rotation) but no change; Im am using the twist grip...Twisting to the right is not recognized in FS; The tiller? Would that be the same for Joystick calibration under FSUIPC....If so, no change

Troyhave you tried the os 7 drivers from Saitek

Troyhave you tried the os 7 drivers from Saitek

This is what I have been using. I checked Saitek's forum for similar issues but none were exactly the same...Others however, were having different issues with the X52 and FSX calibration using Win7. There were some suggestions by the admin to unplug the joystick, delete a specific reg entry and reconnect joystick to rebuild Joystick config...I did this but problem still remains. I'm thinking of getting a cheap joystick for now, hoping this would rid the issue...not sure...

what happens if you unplug joystick and use keyboard as a test.bob

what happens if you unplug joystick and use keyboard as a test.bob

Bob,Works fine this way, which leads me to believe its joystick or drivers. Again the Z rotation axis for the rudder works fine during calibration outside of FS. There is full movement on the slider in both directions. The same if I use the calibration from within FS... This little test tells me the stick is ok...I'm not sure why both FSX and FSUIPC see the same issue.Could it be badly written saitek drivers or is FS struggling to incoporate all the Saitek axis with win 7? What are your thoughts?

Troyhave you checked Fsuipc4.ini file to see if anything untowards in that, not familiar with it myself as I only use FSuipc4 for wheel trim.I think you have to disable the controller in FS if your using FSuipc callibration, but you need to confirm this. you could always try unplugging the key board to see if thats not conflicting with the X52.You could do with trying getting you hands on a different joystick just to test then if the same happens and if its the set up between fsx and FSuipc4I had a bit of a problem in XP when I was running the X52, the function keys would freeze out on the HP keyboard, so I got the old ch flight yoke and pedals out of the loft.off on hols in a few hours hope you can track the problem down. I'll check when I get back to see if you have been successful.Bob

Troyhave you checked Fsuipc4.ini file to see if anything untowards in that, not familiar with it myself as I only use FSuipc4 for wheel trim.I think you have to disable the controller in FS if your using FSuipc callibration, but you need to confirm this. you could always try unplugging the key board to see if thats not conflicting with the X52.You could do with trying getting you hands on a different joystick just to test then if the same happens and if its the set up between fsx and FSuipc4I had a bit of a problem in XP when I was running the X52, the function keys would freeze out on the HP keyboard, so I got the old ch flight yoke and pedals out of the loft.off on hols in a few hours hope you can track the problem down. I'll check when I get back to see if you have been successful.Bob

No luck Bob. I tried most of the above suggestions with the exception of a new joystick. I went to Bestbuy and Walmart today and neither of them have one...Next up, Craigslist. In FSUIPC.INI there was an option to enter Rudder configurations manually. I believe those settings would be (-16380,0,512,16380) for accurate trimming of the rudder. When I went back to FS, the trimming reverted back to (-16380,-512,512,-16380). Notice the two (-) before 16380 and the two 512's. There should be no (-) on the last 16xxx and only one 512.This problem is cramping my style...I can't fly :(

Hi Troy - sorry to hear of the your problem. I've had the X-52 almost from the time it came out I also have a second one I bought on a crazy sales last year at Best Buy.I had the same problem as you stated with my first stick and I had to return it to Saitek for a replacement - sorry to be the bearer of bad news.... Howard

Hi Troy - sorry to hear of the your problem. I've had the X-52 almost from the time it came out I also have a second one I bought on a crazy sales last year at Best Buy.I had the same problem as you stated with my first stick and I had to return it to Saitek for a replacement - sorry to be the bearer of bad news.... Howard

Howard,Thanks for your feedback. I guess now its time to dispose this stick and get something new.Is anyone using Logitech's flight system G940? http://www.logitech.com/index.cfm/gaming/j...55&cl=us,enIf so, how do you like it?

Before you give up I would delete the Saitek drivers and SST software and try it with just the default windows drivers, game controllers applet, and fsuipc. After getting rid of the drivers I would also clear out the registry calibration entries so you start from scratch.scott s..

TroyFYIYou said: When I went back to FS, the trimming reverted back to (-16380,-512,512,-16380). Notice the two (-) before 16380 and the two 512's. There should be no (-) on the last 16xxx and only one 512.No - there should be two 512's or some other value as this is the null zone with both values at a minimum and maximum of 512 your null zone is basically 0. Yes there should be a minus figure the full travel of an axis is from plus 16xxx to minus 16xxx - otherwise you do not have full travel. For example, if you expect the values to be between plus 16xxx and zero then your rudder will only work either left OR right. :( A couple of suggestions:Disable the SST softwareDelete your fsx.cfg file (and the FSUIPC4.ini file)Assign the axes only in FSX with the settings I recommended above - any change?RegardsPeterHPS I use a G940 and again you need to set it up correctly in FSX (and/or Logitech profile software and/or FSUIPC4) for it to work correctly). It is NO better than an X-52 in terms of control of a plane and there are a couple of disadvantages - there is no twist grip on the joystick and the pedals seem to be an integral part of the joystick so just to use them with another joystick or yoke is quite cumbersome to achieve. Its a very good system in terms of build, etc, and it is a force fedback stick which works well with FS Force. (You can't use FSUIPC to set up the joystick if you want to keep the FF function)

Before you give up I would delete the Saitek drivers and SST software and try it with just the default windows drivers, game controllers applet, and fsuipc. After getting rid of the drivers I would also clear out the registry calibration entries so you start from scratch.scott s..

Scott,I did as you suggested...I uninstalled SSt software and drivers and used just windows. I even went as far as using another keyboard and mouse and deleted the fsx.cfg and relaunched FS....Absolutely no change...Aircraft continues to veer hard right when taxing. Rudder on all default aircraft is stuck to the right.Thanks for your help.

TroyFYIYou said: When I went back to FS, the trimming reverted back to (-16380,-512,512,-16380). Notice the two (-) before 16380 and the two 512's. There should be no (-) on the last 16xxx and only one 512.No - there should be two 512's or some other value as this is the null zone with both values at a minimum and maximum of 512 your null zone is basically 0. Yes there should be a minus figure the full travel of an axis is from plus 16xxx to minus 16xxx - otherwise you do not have full travel. For example, if you expect the values to be between plus 16xxx and zero then your rudder will only work either left OR right. :( A couple of suggestions:Disable the SST softwareDelete your fsx.cfg file (and the FSUIPC4.ini file)Assign the axes only in FSX with the settings I recommended above - any change?RegardsPeterHPS I use a G940 and again you need to set it up correctly in FSX (and/or Logitech profile software and/or FSUIPC4) for it to work correctly). It is NO better than an X-52 in terms of control of a plane and there are a couple of disadvantages - there is no twist grip on the joystick and the pedals seem to be an integral part of the joystick so just to use them with another joystick or yoke is quite cumbersome to achieve. Its a very good system in terms of build, etc, and it is a force fedback stick which works well with FS Force. (You can't use FSUIPC to set up the joystick if you want to keep the FF function)

PeterH,I tried all those suggestions...Although I did uninstall the software and drivers for Saitek and used windows default, No luck at all. I think this Stick just about had it.Thanks for our help

TroySorry we couldn't solve this one :( RegardsPeterH