Assign one throttle axis to all engines in FSX, remove conflicting per-engine bindings, and fix reversed, partial or jumping throttle response.
In FSX and FSX: Steam Edition, assign the lever to the global Throttle axis command, not Throttle 1 axis or another numbered engine command. Open Settings, choose Controls, select the correct controller under Control Axes, assign Throttle axis, then remove any duplicate or per-engine throttle bindings.
Assign the all-engine throttle axis in FSX
Assigning the unnumbered Throttle axis makes one physical lever operate every engine on single-engine, twin-engine and four-engine aircraft.
- Connect the controller before starting FSX. From the opening screen, go to Settings and then Controls. During a flight, the equivalent route is through the Options and Settings menus.
- Open Control Axes. Use the controller drop-down list to select the yoke, joystick or throttle quadrant containing the lever. FSX stores axis assignments separately for each device.
- Find Throttle axis. Select the unnumbered command, choose Change Assignment, move the required lever through part of its travel and accept the detected axis.
- Remove numbered throttle assignments. Delete Throttle 1 axis, Throttle 2 axis and any other numbered throttle mappings unless you deliberately want separate engine levers.
- Check every connected controller. A joystick slider, gamepad or second quadrant may have received an automatic throttle assignment. The global throttle axis should normally exist on only one device.
- Test with a default multi-engine aircraft. Move the physical lever and confirm that every virtual throttle lever travels together from idle to full power.
Owners of Logitech or Saitek hardware can also use our quadrant assignment and calibration walkthrough for device-specific setup details.
Why does only one engine respond?
A numbered assignment such as Throttle 1 axis controls only that engine, so replace it with the unnumbered Throttle axis command.
Check the assignments for every controller in the drop-down list. FSX often creates automatic mappings when new hardware is detected, and an overlooked engine-specific assignment can override or interfere with the global one. If you later decide that each engine needs its own lever, use the separate-engine FSUIPC configuration rather than combining global and numbered axes.
Why does the FSX throttle jump, fight or move by itself?
Conflicting axis assignments are the usual cause of a throttle that jumps, flickers or returns to another position.
| Symptom | Likely cause and fix |
|---|---|
| Throttle jumps between two positions | Two devices are assigned to Throttle axis. Remove the unwanted assignment from the joystick, gamepad or second controller. |
| One engine moves differently | A numbered throttle axis remains assigned. Delete all per-engine mappings when using one lever for every engine. |
| Throttle moves backwards | Enable or disable Reverse for that axis in Control Axes. |
| Lever does not reach idle or full power | Recalibrate the controller in Windows, then use high sensitivity and a low null zone in FSX. |
| Nothing responds | Confirm controllers are enabled and that the correct device was selected before assigning the axis. |
With a yoke and separate throttle unit, our conflicting Logitech control assignment checks cover the same failure mode in more detail.
What sensitivity and null-zone settings should I use?
For most throttle quadrants, start with high or full sensitivity and the null zone at or near minimum.
A throttle needs its complete travel more than it needs a softened response around the centre. If the lever cannot command both idle and full power after calibration, check the physical controller calibration before compensating with a large FSX null zone.
Does the global throttle axis work with add-on aircraft and FSUIPC?
Default FSX aircraft normally recognise the global Throttle axis directly, while some complex add-on aircraft or FSUIPC configurations may process throttle input separately.
Test the assignment in a default aircraft first. If it works there but not in the add-on, inspect that aircraft's control configuration. When FSUIPC is handling the lever, avoid assigning the same axis in both FSUIPC and FSX, because two active input paths can produce erratic movement.