Learn FSUIPC joystick and throttle calibration: assign axes, set endpoints and centre zones, stop duplicate inputs, and fix reversed or jittery controls.
To calibrate a joystick or throttle with FSUIPC, remove duplicate simulator bindings, assign each physical axis in FSUIPC, send it to FSUIPC Calibration, then record its minimum, centre or idle, and maximum positions on the Joystick Calibration page. Finish by checking direction, dead zones and full travel in the aircraft.
For general PC flight simulation, this procedure applies to supported FSUIPC releases for Microsoft Flight Simulator, FSX and Prepar3D. FSUIPC is not available on consoles, and its user axis-assignment and calibration facilities require a registered licence. Install the correct release using our FSUIPC download and simulator compatibility information.
What should I do before FSUIPC calibration?
Start with a stable Windows input and only one assignment path for each axis.
- Connect the controller before starting the simulator and FSUIPC.
- Run
joy.cplin Windows and confirm that every axis moves smoothly through its full range. Our Windows controller testing and axis setup procedure covers raw-input faults in more detail. - Delete or disable the corresponding simulator axis assignments. An axis must not be controlled by both FSUIPC and the simulator's native controller profile.
- Decide whether the assignment should be global or aircraft-profile-specific. Profiles are preferable when different aircraft need different throttle, reverse or sensitivity settings.
Windows calibration fixes the device's raw input range; FSUIPC calibration maps that input to simulator commands. FSUIPC cannot repair a worn potentiometer, intermittent USB connection or axis that never reaches its endpoint in Windows.
How to calibrate axes in FSUIPC
The reliable sequence is assignment first, calibration second and aircraft testing last.
- Open FSUIPC's options window. Older FSUIPC modules are normally opened from the simulator's add-on menu, while FSUIPC7 runs as an external Windows application.
- Open Axis Assignment. Move only the joystick, rudder or throttle axis you want to configure. FSUIPC should display the detected joystick and axis identifiers; centre other controls if their electrical noise keeps stealing detection.
- Assign the simulator control. For conventional aileron, elevator, rudder and throttle axes, select
Send direct to FSUIPC Calibrationand choose the matching control. Do not send the same physical lever as both a combined throttle and an individual engine throttle. - Open Joystick Calibration. Find the page containing that control. If its calibration row is inactive, use its initial
Setcontrol. TheResetbutton removes calibration; it does not perform an automatic calibration. - Record the operating range. Set the minimum, centre or idle region, and maximum using the corresponding controls. At each physical endpoint, ease the control back a fraction before recording it. This lets the commanded output reach full travel despite small variations at the hardware stop.
- Check the direction. Select
Revonly when the FSUIPC output moves opposite to the physical control. Do not reverse the same axis again in the simulator or aircraft configuration. - Save and test. Close the options with
OK, load an aircraft and watch the cockpit control or external control surface. Confirm neutral position, both endpoints and smooth movement before adding filters or response slopes.
Which positions should each control use?
Centred controls need a neutral band, while an ordinary throttle usually needs only idle and maximum.
| Control | Positions to record | Main caution |
|---|---|---|
| Aileron or elevator | Full negative, both edges of a narrow centre band, full positive | Release the stick or yoke naturally before setting the centre region. |
| Rudder | Full left, centre band, full right | Do not use a large centre dead zone to hide faulty pedals. |
| Throttle without analogue reverse | Idle and full forward thrust | Use No reverse zone where that option is provided. |
| Throttle with analogue reverse | Full reverse, an idle band, full forward thrust | The aircraft must support reverse thrust through the assigned axis. |
| Toe brakes | Released and fully pressed | Pedal electronics often report these axes backwards, so verify Rev. |
How should throttle reverse and detents be configured?
Throttle calibration depends on whether reverse thrust is part of the analogue axis, a separate lever or a button command.
For an ordinary idle-to-full lever, select the no-reverse-zone option where available and treat idle as the minimum. If the hardware sends analogue reverse below an idle detent, calibrate full reverse, create a small idle band and then record full forward thrust. Reverse levers that operate as buttons should be assigned as buttons rather than included in the analogue range.
Calibrate twin or four-engine levers separately if independent engine control is required. Avoid assigning a combined throttle at the same time as Throttle 1, Throttle 2 and other individual engine axes, because the commands will compete.
Complex Airbus and other add-on aircraft may use their own EFB, MCDU or cockpit calibration utility for IDLE, CL, FLX/MCT and TOGA detents. FSUIPC can supply a clean axis range, but it cannot define aircraft-specific detent logic when the aircraft bypasses standard simulator controls.
Should I disable the simulator's controller assignments?
Disable every native simulator axis binding that FSUIPC is replacing, but unrelated buttons and view controls can remain assigned in the simulator.
The mistake we see most often is leaving an automatically created aileron, elevator or throttle binding active. That produces doubled movement, twitching, controls that return towards centre, or one command apparently overriding another. Check every active controller profile, including profiles created for an Xbox controller or another device that is still connected.
Why is FSUIPC calibration not working?
Most failures come from duplicate assignments, an incorrect reverse-zone choice or an aircraft that expects custom control events.
- FSUIPC detects the axis, but the aircraft does not move: confirm that the axis was sent to the correct simulator control. If only one complex add-on fails, use that aircraft's own input configuration.
- The control moves twice or fights itself: remove the duplicate native simulator assignment. For FSX-specific detection and conflict checks, follow our FSX joystick and throttle troubleshooting steps.
- Full travel is never reached: recalibrate each endpoint slightly inside the physical stop. Check Windows first if FSUIPC's input value itself never reaches a stable extreme.
- The throttle enters reverse at idle: enable the no-reverse-zone setting or recalibrate the idle band, depending on how the hardware generates reverse thrust.
- The centre jitters: create a small centre band. Apply FSUIPC filtering only after checking the USB connection and raw Windows input, because filtering can mask failing hardware and add sluggishness.
- Calibration works in only one aircraft: check whether a profile-specific assignment is active. Different aircraft profiles can contain different axis routes and calibration values.
- Assignments change after reconnecting hardware: keep controllers on consistent USB ports or use FSUIPC's joystick-letter facility where supported, which is less vulnerable to changing Windows joystick numbers.