Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Help with nose wheel and rudder steering

Featured Replies

Troy.Push the 5 on the number pad after disabling joystick and then resave the flight. Then enable the joystick again. It's happened to me before. CH yoke user here.

Gary, CIMEL, retired FAA Controller & all around good guy!
Faa.gif

Same thing is now happening with me.I just installed a windows update when FS was closed, restarted it, and it was all screwed up.Interesting time frame... could be a Windows Update screwing with Saitek drivers possibly?

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.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
Uninstall the Saitek software and only use their drivers.Than in Fsx Control Assignements delete the keyboard and joystick assignements for Rudder Jaw Left and Rudder Jaw Right.It took me several days a while back to solve this same problem.

5950x3d 5.4-5.7 GHz - Asus ROG 870 Crosshair Apex - GSkill Neo 2x 24 Gb 6000 mhz / cas 26 -  MSI RTX 5090 Gaming Trio OC - 1x SSD M2 6000 2TB - 1x SSD M2 2800/1800 1Tb -  Corsair 5400  case - Corsair 360 liquid cooling set  - 3x 75’ TCL tv.

13600  6 cores @ 5.1 GHz / 8 cores @ 4.0 GHz (hypterthreading on) - Asus ROG Strix Gaming D - GSkill Trident 4x Gb 3200 MHz cas 15 - Asus TUF RTX 4080 16 Gb  - 1x SSD M2 2800/1800 2TB - 2x  Sata 600 SSD 500 Mb - Corsair D4000 Airflow case - NXT Krajen Z63 AIO liquide cooling - 

FOV : 200 degrees

My flightsim vids :  https://www.youtube.com/user/fswidesim/videos?shelf_id=0&sort=dd&view=0

 

Uninstall the Saitek software and only use their drivers.Than in Fsx Control Assignements delete the keyboard and joystick assignements for Rudder Jaw Left and Rudder Jaw Right.It took me several days a while back to solve this same problem.
Gerard,This suggestion almost sounded to good to be true, but hen it failed. Bummer! Thanks for your input though.I've opened a thread at Saitek and directed this link to them. Hopefully they have something to add. Thanks again all...Still not giving up
  • 2 weeks later...
Gerard,This suggestion almost sounded to good to be true, but hen it failed. Bummer! Thanks for your input though.I've opened a thread at Saitek and directed this link to them. Hopefully they have something to add. Thanks again all...Still not giving up
Sorry guys I forgot to tell you the problem was resolved by saitek support. Here is what they suggested:"Unplug the controller, click Start>Run, type regedit and click OK. In the Registry Editor browse to the following folders in order:HKEY_LOCAL_MACHINE (HKEY_CURRENT_USER if using Vista)SYSTEMCurrentControlSetControlMediaPropertiesPrivatePropertiesDirectInputAnd delete any folder starting with VID_06A3. Plug the controller back in, move it fully a couple of times and see if that has fixed it."ALSO"The only other thing I can get you to try then is to do that regedit trick again (remembering that the stick must be unplugged first), but this time also look under the HKEY_USERS key and look for the same folder structure under each of the S-1-x-x keys that are in there and delete the VID_06A3 keys.__________________"However, it was not until I went into HKEY_CURRENT_USER and removed the suggested registry entry did it work. The key path in Win 7 is located in 'HKEY_CURRENT_USER/system/CurrentControlsetcontrol/Medi Prop/Privatepro/Directinput'Thanks again for all your help and hope this results can resolve issues others may have with Saitex X52 and Win 7

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.