Jump to content
The simFlight Network Forums

Search the Community

Showing results for tags 'aileron spike'.

More search options

  • 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
    • FS Commander Support Forum
    • 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
    • FScene Support Forum
    • Taburet & DanVFR Support Forum
    • Environ Scenery
  • simFlight DE
  • simRussia
  • FSUIPC Client DLL for .NET


  • Community Calendar


There are no results to display.

Found 1 result

  1. Pete, I would like to say 'thank you' for developing FSUIPC. I know you've worked hard on it and have used it since your first release. I was hesitant submitting to this forum, but I am now at a loss. About 3 weeks ago in P3D v4, I noticed randomly, sometimes continuously for short spurts, my ailerons were spiking to the left. It did not matter the aircraft type nor condition. I turned on FSUIPC (version 5.122) logging and found this: 1488735 *** AXIS: Cntrl= 65695 (0x0001009f), Param= 16383 (0x00003fff) AILERON_SET A normal aileron axis movement with my Saitek Pro Yoke shows this: 1487907 *** AXIS: Cntrl= 65765 (0x000100e5), Param= 16383 (0xffffce91) AXIS_THROTTLE_SET I ran many tests and cannot figure out what is sending this to the sim: Disconnected ALL USB ports, including mouse/keyboard. Deleted the FSUIPC INI file AND the P3D CFG file. Selected 'aileron' in 'Control Spike Elimination' in FSUIPC but spikes still occur. Allowed FSUIPC to handle all axes (reverted back since this did nothing) Checked all axes for assignments other than joystick It happens at random times, without even touching the computer and will sometimes happen back to back (see log file attached). When at cruise it still happens but luckily the autopilot does not disconnect, though the aircraft almost rolls over. I cannot hand fly anymore worried about this spike. Anyone have any ideas where I can find the culprit? It seems like the 0x0001009f from the FSUIPC log file is the identifier, but I cannot figure out what that is. Or, perhaps there is a way to edit the FSUIPC file to ignore that axis? Thanks in advance for your assistance. fsuipc5.log