How do I fix an Xbox controller not working in a PC flight sim?

To fix an Xbox controller in a PC flight sim, first confirm that it responds in Windows with joy.cpl. If it does, rebuild its simulator profile, bind true axes, remove duplicate devices and disable conflicting input layers. If it does not, troubleshoot the cable, USB port, pairing, batteries or controller itself.

This advice covers a general PC flight simulator rather than one specific title. Menu names differ between Microsoft Flight Simulator, FSX, Prepar3D and X-Plane, but the fault-isolation order is the same: Windows connection first, simulator profile second, individual bindings last.

What should I check first on the PC?

Establish whether the fault is in Windows or the simulator before changing profiles, drivers or calibration.

1. Close the simulator. Some sims do not recognise a controller connected after launch, while older titles may fail to recover after it disconnects. Connect it first and then reopen the sim.
2. Test the physical connection. Use a known data-capable USB cable and a port directly on the PC, not a hub. For wireless use, replace or recharge the batteries and pair the controller again.
3. Open the Windows controller test. Press Windows key and R, enter joy.cpl, select the controller and open its properties. Move both sticks, squeeze the triggers and press every button. Our USB, Bluetooth and Xbox Wireless connection checks explain this stage in more detail.
4. Disconnect competing controls. Temporarily unplug spare gamepads, yokes, pedals, throttles and joysticks. Close remapping software that creates virtual controllers.
5. Select the correct in-sim device. Open the controls menu, choose the Xbox controller rather than the keyboard or mouse, and load its default preset if one is available.
6. Test a clean configuration. Use a default aircraft and a new controller profile. Check pitch and roll before adding camera, trim, throttle or add-on-specific commands.

“It’s wired” — why is the controller still not detected?

A lit controller is not proof of a working data connection because some USB cables supply power but do not carry controller input.

Try another cable known to transfer data, then test a different USB port directly on the computer. Avoid an unpowered hub while diagnosing the problem. If Windows repeatedly plays the USB disconnect sound or the controller vanishes when the cable moves, the cable or socket is the likely fault.

What is different about an Xbox 360 controller?

A wireless Xbox 360 controller cannot use Bluetooth and does not become a wired gamepad when connected with a Play & Charge cable.

• Wired Xbox 360 controller: connect its USB cable directly and check for it in joy.cpl.
• Wireless Xbox 360 controller: use a compatible Xbox 360 wireless receiver for PC. The charging cable supplies power but does not carry gameplay input.
• Later Xbox controllers: use USB, Xbox Wireless or Bluetooth only where that controller model supports it.

This Xbox 360 receiver distinction is a common reason a controller has power yet Windows reports no gamepad at all.

Why does Windows detect the controller but the simulator does nothing?

If every control responds in joy.cpl, the controller and basic Windows input path are working; the remaining fault is the simulator configuration or an intermediate input layer.

• Microsoft Flight Simulator 2020 and 2024: select the controller tile, inspect the active preset and change the command filter so it shows all commands rather than assigned commands only. Remove duplicate axes from other devices. Follow our MSFS-specific checks for empty profiles, Steam Input and duplicate controls if the device still produces no response.
• FSX and Prepar3D: make sure controller input is enabled and inspect assignments on every connected device. Old configuration files often retain axes belonging to hardware that is no longer used. FSX users can follow our Xbox controller mapping and null-zone procedure for FSX.
• X-Plane: select the controller, run the simulator's joystick calibration and assign each recognised axis. Windows calibration alone does not create X-Plane bindings.

Another mistake we see constantly is editing the keyboard profile while looking for controller commands. Confirm the selected device name before changing anything.

Does the same fix apply to Gunsmith Simulator?

The Windows connection test applies to Gunsmith Simulator and other non-flight PC sims, but in-game controller support depends on the title and installed build.

If the controller works in joy.cpl, inspect the game's controls menu for a gamepad device, preset or assignable controller commands. If it exposes only keyboard and mouse controls, a blank controller page does not prove the Xbox hardware is faulty; it can mean that the game has no native profile for it. Do not repeatedly reinstall the controller driver to solve an unsupported in-game control scheme.

“Everything is blank” — how do I restore the controller profile?

A blank assignment list usually means the wrong device or filter is selected, or the active profile contains no bindings.

1. Select the Xbox controller itself. Do not edit the keyboard, mouse or a disconnected controller with a similar name.
2. Clear the search box. Switch from an assigned-only filter to the option that displays every available command.
3. Load the default preset. If the sim supplies an Xbox preset, duplicate or save it under a new name before customising it.
4. Create a clean profile if necessary. Bind one axis at a time and test after each assignment. A damaged or empty profile is easier to replace than repair command by command.
5. Distinguish an empty profile from a blank interface. If the entire controls page is missing device tiles, labels and buttons, restart the simulator and temporarily remove controller utilities or add-ons that load with it. Do not delete cloud-synchronised profiles as the first response.

Why do the buttons work but the sticks and triggers do not?

Menu buttons and analogue flight axes use separate assignments, so button response does not prove that the flight controls are configured.

Bind the left stick horizontally to the aileron or roll axis and vertically to the elevator or pitch axis. Choose axis commands, not separate left, right, up and down button commands. Reverse an axis only when the on-screen control moves opposite to the stick.

Triggers may appear as separate inputs or as opposite ends of a combined axis, depending on the simulator and input layer. They can operate rudder only if both directions are recognised correctly. Because an Xbox controller has no throttle lever that stays in position, increase/decrease throttle buttons are often more predictable than assigning throttle to a spring-centred control.

Clear pitch, roll, rudder and throttle from unused devices if the aircraft moves by itself. Use a small dead zone for minor stick drift; needing a very large dead zone usually indicates worn hardware.

“My controller died” during the sim — what failed?

A controller that stops mid-session usually lost power or connection rather than losing its control profile.

• Wireless: replace or recharge the batteries, reduce distance and re-pair if the connection does not return. A controller can also power down after a period without physical input.
• USB: test another data cable and direct port. Movement at the plug causing repeated disconnects points to a damaged cable or socket.
• After reconnection: check whether the simulator still shows the same device and profile. Some older sims require a complete restart before they accept input again.
• Repeated failures: test wired to remove batteries and wireless interference from the diagnosis. If several USB devices disconnect together, investigate the PC's USB power management rather than the controller profile.

Should I use Steam Input or Windows calibration?

Use one controller translation layer, and treat calibration as a diagnostic tool rather than the first repair.

Most Xbox-compatible controllers use XInput, which modern simulators can usually read directly. If Steam Input or another remapper creates a virtual gamepad, the simulator may see both physical and virtual devices. That can cause duplicate movement or leave you editing a profile for the wrong device.

Where the simulator has native Xbox support, test with Steam Input and other remappers disabled. An older title may need translation, but in that case bind only the virtual device and clear assignments from the physical one.

Use joy.cpl to see whether the sticks return near centre and reach their expected range. Make dead-zone and sensitivity changes inside the simulator. Calibration cannot repair a worn sensor, and unofficial driver packages are not a substitute for a failing cable or controller.

Still not working — dalej nie działa, sigue sin hacer nada, or yok?

These phrases describe the same practical result: the controller still does nothing, or no device appears. Stop changing several settings at once and run a final isolation test.

1. Build the simplest connection. Use one controller, a direct USB data cable and no hubs, remappers or other flight controls. A wireless Xbox 360 controller must instead use its PC receiver.
2. Test outside the simulator. If it fails in joy.cpl, the simulator is not the cause.
3. Test a fresh in-sim profile. Assign only pitch and roll, then use a default aircraft or vehicle.
4. Cross-test the hardware. Try the controller on another PC, or try a known-working controller on this PC. Failure on two computers points to the controller, cable or receiver; failure in only one simulator points to that title's profile or input support.

Başka bir şey yok mu — is there anything else to try?

If you searched for baska bisey yokmu, one useful test remains: watch the controller continuously in joy.cpl while moving the cable and operating every axis. Missing buttons, an axis stuck at one extreme, severe drift or repeated disconnection across multiple ports confirms a hardware-side fault. Reinstalling the flight simulator will not repair it.