Why is my joystick or throttle not working in X-Plane?
If a throttle or joystick is not working in X-Plane, first confirm that the operating system and X-Plane both detect it, then remove duplicate axis assignments, recalibrate every axis, and load the correct aircraft profile. Test a default aircraft: if that works, the fault is an aircraft-specific profile, plug-in or control mode.
Fix an X-Plane joystick or throttle in the right order
The fastest fix is to separate hardware detection from X-Plane configuration, then from aircraft-specific behaviour. The same basic process applies to X-Plane 11 and X-Plane 12, although some labels and screen layouts differ.
- Confirm operating-system detection. Connect the controller directly to the computer rather than through an unpowered USB hub. On Windows, run
joy.cpland check whether its axes and buttons respond; our Windows joystick detection checks cover the USB and hardware side in detail. If the operating system cannot see the controller, X-Plane cannot configure it. - Open X-Plane’s Joystick settings. Go to
Settings > Joystick, select each connected controller and move every stick, pedal and lever. The on-screen axis bars should follow the physical controls smoothly. - Assign the correct axes. Set the stick or yoke to pitch and roll, pedals or twist grip to yaw, and the power lever to throttle. Set unused axes to
None; an automatically selected but incorrect function can make a working lever appear useless. - Remove duplicate assignments. Check every connected controller, including gamepads, rudder pedals and spare quadrants. Only one physical axis should control pitch, roll, yaw or a given throttle unless the duplication is deliberate. Conflicting inputs often cause controls to snap back, move only partly or ignore one device.
- Calibrate the full travel. Follow X-Plane’s calibration prompts, moving each axis from stop to stop and releasing self-centring controls at the centre. If calibration will not complete or the centre remains offset, use our complete X-Plane joystick calibration procedure.
- Check the active aircraft profile. X-Plane can store different assignments for different aircraft. Make sure the intended profile is selected and associated with the aircraft; see how to create and switch aircraft-specific control profiles without overwriting a working setup.
- Test a supplied aircraft. Load a simple default general-aviation aircraft with a default control profile. If the controller works there, the USB connection and basic X-Plane configuration are sound; investigate the original aircraft’s custom commands, throttle calibration or plug-in instead.
What does each joystick or throttle symptom mean?
The point at which the input stops responding usually identifies the fault.
| Symptom | Likely cause | What to do |
|---|---|---|
| Controller is absent from Joystick settings | USB, power, cable or operating-system detection | Try a direct USB port, reconnect the device and test it outside X-Plane |
| Device is listed, but its axis bars do not move | Hardware mode, driver, cable or controller fault | Check any mode switch and confirm axis movement in the operating system |
| Axis bars move, but the cockpit control does not | Wrong assignment, profile or aircraft-specific input system | Assign the standard axis and test a default aircraft |
| Control moves backwards | Axis direction is reversed | Toggle Reverse Axis for that axis only |
| Control jumps, fights another input or returns | Duplicate binding or electrical noise | Clear duplicates, recalibrate and test the raw input outside X-Plane |
| Controller works in default aircraft only | Add-on profile, custom command, detent setup or plug-in | Configure the aircraft-specific controls rather than reinstalling X-Plane |
Why does X-Plane not detect my joystick or throttle?
If a controller is absent from X-Plane’s Joystick screen, solve detection before changing any axis assignments. Reconnect it directly, try another USB port and restart X-Plane after the operating system has recognised the device.
A detachable cable can carry power while failing to carry data, and an overloaded hub may disconnect a throttle quadrant when other devices draw power. A split HOTAS can also appear as two separate controllers, so configure both the stick and throttle entries rather than expecting one combined device.
If buttons work but axes do not, check for a hardware mode switch and watch the raw axis display in the operating system. An axis that fails or spikes there has a hardware, cable or driver problem; response curves inside X-Plane will not repair it.
Why does the axis move in settings but not in the aircraft?
When X-Plane’s input bar responds but the aeroplane does not, the hardware connection is working. The remaining causes are usually an incorrect function, the wrong profile or an aircraft that handles controls through its own systems.
Many complex add-on aircraft provide separate calibration for throttle detents, reversers or tiller steering. Assign the normal X-Plane axis first, then complete any calibration offered inside that aircraft. Do not assign buttons to imitate a continuous axis unless the aircraft specifically requires it.
Autothrottle can also override or temporarily disregard a physical throttle, particularly when the hardware position does not match the commanded thrust setting. Disengage the automatic thrust system using the aircraft’s normal procedure, match the lever position and test again.
Watch the virtual control in the cockpit. If the yoke or throttle lever follows your hardware, X-Plane is receiving the input; a lack of aircraft response then points to a control lock, hydraulic or electrical state, engine condition, simulated failure or aircraft-specific system rather than the joystick.
How should multi-engine throttles be assigned?
A single physical power lever should normally use the general throttle axis, while separate levers should use the corresponding per-engine throttle axes. Avoid assigning both the general throttle and an individual engine throttle to the same lever; our guide to generic and per-engine throttle assignments explains the correct choices and testing sequence.
How do I fix reversed, jittering or spiking controls?
A reversed control needs its individual Reverse Axis option changed; jittering or spikes require calibration and hardware checks. Do not reverse every axis because one lever moves in the wrong direction.
Recalibrate first, then observe the input bar without touching the controller. If it flickers, try a direct USB connection, another port and a different detachable cable where applicable. Persistent movement in both X-Plane and the operating-system test indicates sensor or electrical noise.
A small centre dead zone can suppress minor noise on a self-centring stick or pedals, but it should not conceal large spikes. Throttle axes normally need usable movement across their full range, so a large dead zone can prevent idle or maximum thrust from being reached.
Should I delete X-Plane’s preferences?
Reset preferences only after hardware detection, assignments, calibration and profiles have been checked. Starting with this step erases useful settings without fixing a disconnected or faulty controller.
Exit X-Plane and back up the Output/preferences folder inside the X-Plane installation. Rename that folder, launch X-Plane so it creates fresh preferences, and configure one controller with a default aircraft. If the fault remains, restore the backup; if it disappears, rebuild the control settings rather than restoring the suspect configuration.
If the problem began after installing a third-party control utility or plug-in, disable that component temporarily before resetting everything. Reinstalling X-Plane is rarely necessary when the device is detected and the fault is confined to bindings, profiles or preferences.