Why is my joystick or throttle not working in FSX?

In FSX and FSX: Steam Edition, a joystick or throttle usually stops working because Windows cannot see the device, controllers are disabled, the analogue axis is assigned incorrectly, or two inputs conflict. Check it in Windows, enable it in FSX, assign the correct axis, remove duplicates, then calibrate it.

Where is the controller signal failing?

Use Windows, FSX's Controls screen and a default aircraft in that order to identify where the input signal stops.

This distinction saves time. Reinstalling FSX cannot fix a device that is absent or motionless in Windows, while repeatedly reinstalling a controller driver will not repair an incorrect FSX axis assignment.

How do I get FSX to recognise my joystick or throttle?

Start with Windows detection, then configure the controller inside FSX while it remains connected to the same USB port.

1. Close FSX and test the device in Windows. Press Win+R, enter joy.cpl and open the controller's Properties window. Move every stick, pedal, lever and rotary axis through its full range. The indicators should respond smoothly rather than sticking, jumping or remaining still.
2. Fix Windows detection first. If the device is absent, reconnect it to a direct USB port and avoid an unpowered hub. Try another direct port and install the appropriate device driver if the hardware requires one. If it remains absent on multiple ports, the cable or controller itself may be faulty.
3. Connect it before starting FSX. FSX does not always handle controllers connected after the simulator has launched. Keep established devices in the same USB ports where practical because Windows may present them to FSX as new devices after a port or driver change.
4. Enable controller input. From the opening screen, open Settings and then Controls. During a flight, use Options, Settings and Controls. Confirm that Enable Controller(s) is selected.
5. Select the physical device. On the Control Axes tab, choose the joystick, throttle quadrant or pedals from the Controller Type list. FSX stores assignments separately for each device, so editing the joystick will not change the quadrant's bindings.
6. Assign each analogue axis. Use Ailerons axis, Elevator axis, Rudder axis and Throttle axis as appropriate. Move only the intended control when FSX asks for an input.
7. Check the direction. Select Reverse only if that particular axis operates backwards. A throttle that gives idle when pushed forwards often needs reversing; that does not mean the stick or pedals should also be reversed.

A mistake we see constantly is assigning a lever to Throttle increase or Throttle decrease. Those are button-style commands. A physical lever needs the continuous Throttle axis assignment. Our complete FSX joystick connection and assignment procedure covers the baseline setup in more detail.

For a multi-engine quadrant, use the general Throttle axis when one lever should operate all engines. Use numbered throttle axes only when separate physical levers are intended to control individual engines.

Why does the keyboard throttle work but the hardware does not?

If the keyboard changes power in a default aircraft but the physical throttle does not, the engine can accept standard FSX commands and the fault is in controller detection, assignment or calibration.

Load an engine-running default Cessna 172 and test F1 for idle, F2 to reduce power, F3 to increase it and F4 for full power. If these work, return to Control Axes and inspect the hardware binding. If they do not, check whether the keyboard commands were changed and confirm that the engine is running; our guide to viewing and restoring FSX keyboard assignments explains where those commands are stored.

How do I remove duplicate axis assignments?

Inspect every entry in the Controller Type list and leave each flight-control axis assigned through only one device or control system.

• Remove an automatically assigned throttle axis from a joystick slider when a separate throttle quadrant should control power.
• Check gamepads, pedals and unused controllers for unwanted aileron, elevator, rudder, brake or throttle assignments.
• Disconnect unused controllers temporarily. If the problem stops, reconnect them one at a time and clear the duplicate binding.
• Watch for physical and virtual copies of the same controller created by remapping software or a controller layer. Map one copy, not both.
• If FSUIPC handles an axis, delete the matching assignment from FSX. If FSX handles it, do not assign the same axis again through FSUIPC.

Duplicate inputs cause characteristic symptoms: the cockpit lever jumps back, one device overrides another, the aircraft pulls to one side, or an axis responds intermittently. For an FSUIPC-controlled setup, use our FSUIPC axis-assignment and endpoint calibration instructions rather than mixing two independent calibration systems.

How should I calibrate an FSX joystick or throttle?

Calibrate in Windows first, then adjust FSX sensitivity and null zones only after Windows detects the complete physical range.

1. Open the Windows controller properties. Run joy.cpl, select the device and use its calibration option if one is provided. Some controllers perform calibration through their own driver or internally instead.
2. Centre self-centring axes. Leave the stick and rudder centred when calibration begins, then move every requested axis through its full travel.
3. Start with high sensitivity. For a normal linear flight-control axis, set FSX sensitivity at or near maximum. A low sensitivity setting can prevent the cockpit control from reaching its full range.
4. Use the smallest useful null zone. Add only enough null zone to stop unwanted movement around the centre. Throttle levers generally need little or none because they do not have a spring-centred position.
5. Verify both endpoints in the cockpit. Check that the yoke, pedals and throttle reach their expected limits. Reverse an axis if its direction is wrong; do not attempt to fix a reversed axis with sensitivity or null-zone settings.

Calibration cannot create a missing assignment. A perfectly calibrated throttle will still do nothing until it is bound to Throttle axis.

Why does FSX see the throttle but the aircraft not respond?

If the cockpit lever moves when the hardware moves, FSX is receiving the axis and the remaining fault is usually the aircraft state, autothrottle or aircraft-specific control logic.

The default Cessna 172 is a useful control test because it has no autothrottle. Start it in a ready-to-fly state, move the physical throttle and watch the cockpit lever. If it works there, stop changing FSX's global assignments and investigate the affected add-on aircraft instead.

FSX-SE still isn't showing the controller — what next?

If FSX: Steam Edition, often shortened to FSX-SE or FSXSE, still is not showing a device that works in joy.cpl, look for a changed device identity, virtual controller conflict or damaged FSX controls profile.

Simmers describe this same broad problem in different ways: “it still isn't showing up”, Italian non va meaning “it doesn't work”, or Finnish ei näy meaning “it isn't visible”. The useful diagnostic distinction is whether the device is absent from the list or appears there but produces no axis movement.

1. Restart with only essential controls connected. Close FSX-SE, disconnect gamepads and unused controllers, connect the joystick or throttle directly, then launch the simulator again.
2. Check for virtual controllers. Temporarily disable unnecessary remapping layers and control utilities. If both physical and virtual versions appear, assign the version that actually shows movement and clear the other.
3. Match utility permissions. If TrackIR, camera software or a controller utility also stops communicating with FSX, ensure the applications are not running at incompatible permission levels. Hotkey clashes and virtual-device conflicts can affect both systems; see our checks for combined TrackIR and joystick failures.
4. Reset the controls profile only as a last resort. Close FSX and back up %APPDATA%\Microsoft\FSX\Controls\Standard.xml. A Steam Edition profile, particularly beside a boxed installation, may instead be under an FSX-SE folder. Rename the active Standard.xml, restart FSX and test the fresh defaults. This removes customised keyboard and controller bindings, which is why the backup matters.

Why do my FSX bindings keep disappearing?

Bindings usually disappear because Windows has given the controller a different identity, the USB connection is dropping, or FSX cannot retain its controls profile.

• Connect each device before starting FSX and keep it in the same USB port.
• If it vanishes from both FSX and joy.cpl during a flight, investigate USB power management, the cable and the device rather than the FSX assignment.
• If assignments disappear only after restarting FSX, confirm that its controls profile exists and that the Windows user account can write to the profile folder.
• If FSX repeatedly creates defaults, restore the backed-up profile only after resolving the USB identity or file-access problem; otherwise the fault will return.

If there is still nothing in joy.cpl after trying multiple direct USB ports, the problem lies outside FSX. If Windows shows clean movement and a fresh FSX profile works with a default aircraft, reconnect add-ons and control utilities one at a time until the conflicting component becomes clear.