Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'x-55'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Product Support Forums
    • FSUIPC Support Pete Dowson Modules
    • MyTraffic Support Forum
    • FeelThere Support Forums
    • Flying W Simulation
    • AConstable Traffic Sounds Support Forum
    • Fabio Merlo Products Support Forum
    • Elite-Air Studio Support Forum
    • Nikola Jovanovic Support Forum
    • Intrasystems Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia


There are no results to display.

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 1 result

  1. Hello, I've recently updated my Windows 7 Ultimate installation to Windows 10 Pro (using the upgrade functionality). Since then, I have one major issue with my Saitek X-55 throttle and FSUIPC. The problem is that FSUIPC does not detect axis and button inputs from the throttle unit. This in both FSX and P3D. If I start the sim, open FSUIPC, and go the axis calibration tab, nothing happens when I move one of the axis. Same thing for buttons, on the respective tab. The X-55 stick works fine though, it's just the throttle. Similarly, the throttle works perfectly if I don't use FSUIPC. It's detected in Windows, the calibration tool works, and it also works if I assign axis through FSX or P3D. As I said, the problem only seems to happen with FSUIPC. I've tried: 1) reinstalling latest saitek drivers 2) completely uninstalling the X-55, restarting, then reinstalling, restarting again. 3) deleting the [JoyNames] section of the fsuipc.ini file 3) deleting fsuipc.ini file altogether So far, no luck. One thing I did notice that struck me as weird, (although I'm not sure) is that fsuipc.ini shows 2 entries for the X-55 rhino stick (the unit that works) and only one for the throttle (the one that doesn't). No idea why it shows 2 entries, and if it should or not. (I also tried updating fsuipc to v4.951 after copying the below files. No difference) My usual fsuipc.ini file, containing the options and edits I used successfully before moving to Windows 10: The new autogenerated fsuipc.ini file: and the FSUIPC.log file from the last try: Any feedback would be very welcome. Would very much like to get this working as it should... Thank you very much, Lars
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.