Fix a joystick or throttle not working in X-Plane: check detection, assignments, calibration, profiles, PS5 controllers and the T.16000M.
If a joystick or throttle is not working in X-Plane, first verify that the operating system and X-Plane both detect it. Then remove duplicate bindings, assign the correct axes, calibrate their full travel and confirm the active aircraft profile. If a default aircraft works, the fault is aircraft-specific, not the controller connection.
Fix an X-Plane joystick or throttle in the right order
The quickest diagnosis is to separate hardware detection from X-Plane configuration and aircraft-specific behaviour. These checks apply to X-Plane 11 and X-Plane 12, although labels and screen layouts can differ slightly.
- Test detection outside X-Plane. Connect the controller, then check whether the operating system can see its axes and buttons. On Windows, press
Windows + R, runjoy.cpland open the device’s properties. If nothing responds there, changing X-Plane settings will not help. - Use a direct USB connection. Temporarily bypass unpowered hubs, extension leads and front-panel ports. Try another port and, where the cable is detachable, a known data-capable cable. A cable can supply power while its data connection fails.
- Open X-Plane’s controller screen. Go to
Settings > Joystick, select each connected device and move every stick, pedal and lever. The corresponding on-screen bars should move smoothly through most or all of their range. - Assign the correct functions. Use pitch and roll for the stick or yoke, yaw for pedals or a twist grip, and throttle for the power lever. Set unwanted axes to
None; automatic assignments are useful starting points, not proof that every control is mapped correctly. - Remove duplicate axes. Inspect every joystick, throttle, pedal set and gamepad. Two devices assigned to pitch, roll, yaw or the same throttle can fight each other, make a control snap back or leave it apparently frozen.
- Calibrate the complete travel. Move each axis firmly from one stop to the other and let self-centring controls return to neutral. If calibration will not complete, the centre is offset or the direction is wrong, use our detailed X-Plane calibration and reversed-axis checks.
- Check the active aircraft profile. X-Plane can load different assignments for different aeroplanes. Confirm that the intended profile is associated with the aircraft; our complete input-device and profile setup sequence covers joysticks, yokes, throttles and pedals together.
- Load a supplied aircraft. Test a simple default general-aviation aircraft with a basic profile. If it works, do not reinstall X-Plane or replace the controller: investigate the original aircraft’s profile, custom commands, detent calibration or plug-in.
What does each joystick or throttle symptom mean?
Where the input stops responding usually identifies which part of the chain has failed.
| Symptom | Likely cause | Next check |
|---|---|---|
| Absent from the operating-system test | USB connection, cable, power, hardware mode or device fault | Use another direct port or data cable and test without a hub |
| Visible to the operating system but absent from X-Plane | X-Plane was started before detection, or a controller utility is hiding the physical device | Restart X-Plane and test without virtual-controller software |
| Listed in X-Plane, but no axis bars move | Wrong hardware mode, virtual mapping or device fault | Test the raw axes outside X-Plane |
| Axis bars move, but nothing moves in the cockpit | Wrong assignment, profile or aircraft-specific control system | Assign a standard axis and load a default aircraft |
| Control moves backwards | That axis is reversed | Change Reverse Axis for that axis only |
| Control jumps, returns or fights the pilot | Duplicate assignment or electrical noise | Clear duplicates, recalibrate and inspect the untouched input bar |
It still isn’t showing up: “no aparece” or “gene yok”
If the controller is still absent, stop changing bindings because X-Plane has no input device to configure. The same diagnosis applies when “no se mueve nada” means that nothing moves in either the operating-system test or X-Plane’s axis display; the fault is before the aircraft profile.
- Connect the device before launching X-Plane, wait for the operating system to recognise it, then restart the simulator.
- Disconnect other controllers temporarily. Add them back one at a time so a generically named device can be identified.
- Remember that a HOTAS package may appear as separate stick and throttle devices. Select and configure each entry.
- If controller-mapping software creates a virtual device, choose one input path: either configure the physical devices directly or use the virtual combined device. Do not bind both.
- If the device has a console, PC or compatibility mode, select the computer-compatible mode before reconnecting it.
If the operating system detects every axis correctly but X-Plane never lists the device, the connection itself is probably sound. Test with mapping utilities and plug-ins disabled before resetting preferences.
Can I use a PS5 controller with X-Plane?
A PS5 DualSense controller can control desktop X-Plane when the computer exposes it as a game controller, but X-Plane itself does not run on a PlayStation 5 console. A USB data cable is the best first test because it removes Bluetooth pairing and battery state from the diagnosis.
Do not expect a ready-made flight-control layout. Assign the sticks and buttons manually in Settings > Joystick. A practical arrangement is one stick for pitch and roll, the other for view movement or throttle, and buttons or triggers for brakes, trim and other commands.
The two triggers may appear as separate one-way axes rather than one combined rudder or throttle axis. If X-Plane cannot use them as the control you want, assign a stick axis to that continuous function and use the triggers as brakes or buttons instead. Apply only a small centre dead zone to short-travel sticks; a large one makes fine control harder.
If USB works but Bluetooth does not, the joystick assignment is not the problem. Remove and pair the controller again at operating-system level, then restart X-Plane. If the DualSense appears twice or inputs fight, disable one virtual or remapping layer.
What if I use a Thrustmaster T.16000M?
A Thrustmaster T.16000M setup should be configured one detected USB device at a time. In a HOTAS package, the T.16000M stick and TWCS throttle commonly appear as separate entries, so selecting the stick does not display the throttle’s axes.
A mistake we see constantly is assigning both the stick twist and the throttle’s paddle control to yaw. Keep the one you prefer and set the other to None. Assign the main throttle lever to throttle, move it through its full travel during calibration and reverse only that axis if idle and maximum power are swapped.
If Thrustmaster or other mapping software combines the hardware into a virtual controller, the original entries may disappear or coexist with the virtual device. Either bind the raw T.16000M and throttle directly in X-Plane or use the virtual controller, not both. Unwanted mini-stick and rotary axes should also be set to None so they cannot acquire accidental assignments.
Why does the axis move in settings but not in the aircraft?
If the axis bar moves in X-Plane, the USB connection and basic hardware detection are working. The remaining fault is usually an incorrect function, the wrong aircraft profile, a duplicate binding or an aircraft system overriding the physical control.
Load a default aircraft first. If that responds, return to the problem aircraft and check its own electronic flight bag, settings panel or calibration page for throttle detents, reversers, tiller steering or custom control commands. Complete the standard X-Plane assignment before applying aircraft-specific calibration.
Autothrottle can command a different thrust setting from the physical lever. Disengage it using the aircraft’s normal procedure, match the hardware position to the cockpit lever and test again. Autopilot, control locks and simulated hydraulic, electrical or engine failures can create similar symptoms.
Watch the virtual control closely. If the cockpit yoke or throttle follows the hardware but the aeroplane does not react, X-Plane is receiving the input; investigate the aircraft’s systems, engine state or failures rather than recalibrating the joystick repeatedly.
How should multi-engine throttles be assigned?
Use the general throttle axis when one physical lever should move every engine, and use the corresponding per-engine axes when each engine has its own lever. Do not assign both the general throttle and an individual engine throttle to the same lever; our generic-versus-per-engine throttle setup explains how to choose and test each arrangement.
How do I fix reversed, jittering or spiking controls?
A backwards control needs its individual Reverse Axis setting changed, while jitter and spikes require calibration and hardware testing. Reversing unrelated axes or adding a large dead zone only hides the real problem.
After recalibrating, leave the controller untouched and watch its input bar. Small movement around the centre of a self-centring stick can be managed with a modest dead zone. Large jumps, movement across the whole range or the same noise in the operating-system test point to the cable, USB connection or the controller’s sensor.
Throttle levers need useful travel near idle and maximum power, so avoid a broad dead zone at either end. If an aircraft cannot reach idle, reverse or full thrust despite a stable input, check its detent calibration before assuming the physical throttle is defective.
Should I delete X-Plane’s preferences?
Reset X-Plane preferences only after checking detection, duplicate assignments, calibration, profiles and a default aircraft. A reset cannot repair a controller that is missing from the operating system.
Close X-Plane and make a backup of the Output/preferences folder inside the installation. Rename the original folder, start X-Plane so clean preferences are created, then configure one controller and test one default aircraft. If the fault remains, restore the backup; if it disappears, rebuild the control assignments rather than copying the suspect configuration back.
Disable third-party control utilities and aircraft plug-ins before performing a full reset. Reinstalling X-Plane is rarely justified when the simulator already detects the device and its axis bars move.