Fix an Xbox controller not working in a PC flight simulator by checking Windows detection, USB or Bluetooth, profiles, bindings and conflicts.
An Xbox controller that is not working in a PC flight simulator usually has one of four faults: Windows cannot see it, the sim loaded the wrong control profile, essential axes are unbound, or another input layer is intercepting it. Test it in Windows first, then rebuild its simulator bindings.
What should I check first?
Confirm that the controller works at Windows level before changing simulator settings or reinstalling anything.
- Connect it before opening the simulator. For a wired connection, use a known data-capable USB cable plugged directly into the PC rather than a hub. A charge-only cable can power the controller without carrying input data. For wireless use, re-pair Bluetooth or Xbox Wireless and check the batteries.
- Test the controller in Windows. Press Windows key and R, enter
joy.cpl, select the controller and open its properties. Move both sticks and press every button and trigger. Our Windows detection and calibration checks for PC flight controls cover this stage in more detail. - Remove competing devices temporarily. Disconnect spare gamepads, yokes, joysticks and virtual controllers. This prevents the simulator from selecting the wrong device or receiving two commands for the same axis.
- Restart after connecting. Some simulators do not handle controllers connected after launch reliably. Close the simulator completely, reconnect the controller and reopen it.
- Select or create a controller profile. Open the simulator's control settings, select the Xbox controller itself and load its default preset if one exists. If the existing profile is empty or corrupted, create a clean one.
- Test with a default aircraft. A stock light aircraft removes add-on-specific control logic from the diagnosis. Check pitch, roll, rudder and throttle before adding custom bindings.
| Symptom | Likely cause | Best next step |
|---|---|---|
Controller absent from joy.cpl | Cable, USB, pairing, battery or Windows problem | Try another data cable or direct USB port, then re-pair wireless |
| Works in Windows but not the simulator | Wrong profile, disabled controllers or input wrapper conflict | Select the device in the sim and check its active profile |
| Buttons work but sticks do not | Axes are unassigned or bound as buttons | Assign the dedicated pitch, roll and rudder axis commands |
| Aircraft jerks or ignores inputs | Duplicate bindings or excessive stick drift | Clear competing axes and adjust dead zones |
| Controller disconnects during flight | Weak batteries, cable fault, wireless interference or USB power saving | Test wired through a direct motherboard USB port |
Why does Windows detect the controller but the simulator does not?
If joy.cpl shows correct movement, the hardware and basic Windows input path are working; the fault is inside the simulator or an intermediate input layer.
- Microsoft Flight Simulator 2020 and 2024: select the controller tile rather than the keyboard or mouse, check the active preset and remove duplicate axis assignments. For MSFS-specific profile and detection faults, follow our controller troubleshooting sequence for Microsoft Flight Simulator.
- X-Plane: run the simulator's controller calibration and assign each recognised axis. If the device is missing or calibration will not complete, use these X-Plane detection, calibration and binding checks.
- FSX and Prepar3D: make sure controllers are enabled, then inspect the axis assignments for every attached device. Older profiles often retain duplicate pitch, roll or throttle bindings after hardware changes.
A mistake we see constantly is searching the control list with a restrictive filter enabled. Switch the filter to show all available commands, not just commands already assigned to the selected controller.
Why do the buttons work but the sticks or triggers do not?
Menu buttons and flight-control axes use separate bindings, so navigating the menus does not prove that pitch, roll or rudder has been configured.
Bind the left stick's horizontal movement to the aileron or roll axis and its vertical movement to the elevator or pitch axis. Use an axis command rather than separate left, right, up or down button commands. Reverse the axis only if the on-screen control moves opposite to the stick.
Triggers are a special case. Depending on the simulator and input layer, they may appear as separate controls or opposite ends of one combined axis. They work well for rudder only when the sim recognises both directions correctly. An Xbox controller also lacks a physical throttle lever that stays in position, so incremental throttle buttons are often more predictable than a spring-centred stick or trigger.
If an aircraft moves without input, clear pitch, roll, rudder and throttle assignments from every unused controller. Add a small simulator dead zone for minor stick drift; a large dead zone that is needed to stop constant movement usually points to worn hardware.
Should I use Steam Input or Windows calibration?
Use only one controller translation layer, and treat calibration as a diagnostic step rather than the first fix.
Most Xbox-compatible controllers use XInput. A modern simulator with native Xbox controller support usually works best without an extra remapper. If Steam Input or another controller utility creates a virtual device, the simulator may see both the physical and virtual controllers, producing duplicate commands or no response from the profile you edited.
If applicable, disable Steam Input for the simulator and test its native support first. An older simulator that cannot interpret the controller properly may benefit from translation, but bind only the resulting virtual device and remove assignments from the original one.
Windows calibration will not repair worn stick sensors. Use joy.cpl to confirm whether each axis reaches its full range and returns near the centre, then make sensitivity and dead-zone adjustments inside the simulator. Update the controller firmware through the Xbox Accessories application where supported, but avoid unofficial driver packages.
When is the Xbox controller itself faulty?
The controller is probably faulty if it fails in joy.cpl with multiple data cables or USB ports, repeatedly disconnects on both wired and wireless connections, or shows severe drift outside the simulator.
Small centre movement can usually be managed with a dead zone. Missing buttons, an axis stuck at one extreme or repeated connection loss after changing the cable and batteries indicates a hardware problem; reinstalling the flight simulator will not correct it.