Why is my joystick or throttle not working in FSX?
In FSX and FSX: Steam Edition, a joystick or throttle usually fails because Windows cannot see it, controllers are disabled, the wrong axis is assigned, or two devices conflict. Test it in Windows, enable controllers in FSX, bind analogue inputs under Control Axes, remove duplicate assignments, then calibrate the device.
How do I get FSX to recognise my controller?
Start with Windows detection and work towards FSX; reinstalling the simulator cannot fix a controller that Windows itself cannot see.
- Test the controller in Windows. Close FSX, press
Win+R, enterjoy.cpland open the controller's Properties window. Every stick, pedal and throttle axis should move smoothly through its full range. - Reconnect it before starting FSX. Use a direct USB port where possible, reconnect the device to the same port and then launch FSX. Older controllers and unpowered hubs can be unreliable, and FSX does not always handle hot-plugging cleanly.
- Enable controllers in FSX. From the opening screen, use Settings and then Controls. During a flight, the same panel is available through Options, Settings and Controls. Make sure Enable Controller(s) is selected.
- Select the correct device. Open the Control Axes tab and choose the joystick, throttle quadrant or pedals from the Controller Type list. Assignments are stored separately for each listed controller.
- Bind the analogue axes. Typical assignments are Ailerons axis, Elevator axis, Rudder axis and Throttle axis. Move the intended control when creating each assignment.
- Check the direction. If a throttle produces idle when pushed forwards, select Reverse for that axis. Do not reverse every axis merely because one control is backwards.
An analogue throttle must be assigned to Throttle axis, not the keyboard-style Throttle increase and Throttle decrease commands. For a multi-engine quadrant, use the numbered throttle axes only when each physical lever is intended to control a separate engine.
If the controller also fails in joy.cpl on more than one direct USB port, investigate its cable, driver or hardware rather than reinstalling FSX. Our FSX joystick setup and replacement checks cover what to assess before buying another device.
Why does keyboard throttle work but the hardware does not?
If the keyboard changes engine power but the physical throttle does not, the aircraft can accept standard FSX throttle commands and the fault is in the controller assignment or detection.
In a default aircraft, test F1 for idle, F3 for increasing power and F4 for full power. Our full FSX keyboard command reference provides the remaining control commands for comparison.
How do I remove duplicate axis assignments?
Inspect every device in the Controller Type list and delete any unwanted copies of the same axis.
- If a separate throttle quadrant is installed, remove any automatic throttle assignment from the joystick slider.
- Check gamepads, pedals and unused controllers for accidental aileron, elevator, rudder or throttle assignments.
- If a third-party control utility handles an axis, clear that axis inside FSX so the two systems do not compete.
- In FSX: Steam Edition, a remapping layer may expose both a physical and virtual controller. Map only the device whose inputs you intend to use.
Duplicate assignments are a common reason for a lever that jumps back, responds only intermittently or appears to ignore movement from the preferred controller.
How should I calibrate an FSX joystick or throttle?
Calibrate the device in Windows first, then adjust FSX sensitivity only after the full physical range is being detected.
- Centre self-centring controls. Leave the stick and rudder centred before beginning calibration.
- Move every axis fully. Sweep the stick, rudder, throttle and any rotary controls through their complete travel when requested.
- Set an initial FSX response. For a normal linear axis, start with Sensitivity at or near maximum and a small Null Zone. Increase the null zone only enough to stop unwanted movement around the centre or idle position.
- Confirm the endpoints. Make sure the cockpit control reaches both limits. A large null zone or incomplete Windows calibration can hide part of the available travel.
Calibration does not create an FSX assignment. A perfectly calibrated throttle will still do nothing until Throttle axis is bound to it.
Why does FSX see the throttle but the aircraft not respond?
If the cockpit lever moves, FSX is receiving the axis and the remaining problem is normally the aircraft state, autothrottle or aircraft-specific control logic.
| Symptom | Likely cause | What to check |
|---|---|---|
| No cockpit control movement | Missing, disabled or incorrect axis assignment | Test a default aircraft and recheck Control Axes |
| Throttle lever moves but power does not change | Engine stopped, mixture at cut-off or custom add-on logic | Load an engine-running default aircraft |
| Throttle moves back by itself | Autothrottle or a duplicate assignment | Disconnect autothrottle and inspect every controller |
| Only one engine responds | A numbered engine axis was assigned | Use the general Throttle axis or map every engine separately |
| Default aircraft works but an add-on does not | Aircraft-specific input system | Use that aircraft's own control configuration and avoid duplicate mappings |
The default Cessna 172 is a useful test aircraft because it has no autothrottle. Start with the engine running, move the physical throttle and watch its cockpit lever. If that works normally, repeatedly changing FSX's global assignments is unlikely to fix a problem confined to one add-on aircraft.
What if FSX bindings keep disappearing?
Bindings often disappear because the controller's Windows identity changed, its USB connection dropped or the FSX controls file became damaged.
- Connect controllers before launching FSX and keep them in the same USB ports.
- If a device stops responding during a flight and also vanishes from
joy.cpl, check the USB connection and Windows power-management settings. - For persistent configuration faults, close FSX and back up
%APPDATA%\Microsoft\FSX\Controls\Standard.xml. A side-by-side boxed and Steam installation may use an FSX-SE profile folder instead. - Rename
Standard.xmland restart FSX to generate fresh default assignments. This resets customised keyboard and controller mappings, so use it only after recording or backing up the existing setup.