Why is my joystick not working in my flight simulator?

In a general PC flight simulator, a joystick fails because the computer cannot detect it, the simulator has selected an empty controller profile, or the pitch and roll axes are unassigned. Test it outside the simulator first: if the axes move there, fix simulator settings; if they do not, fix USB, power, mode or hardware.

My joystick doesn't work: where is the fault?

The fastest diagnosis is to identify the last place where the joystick produces a response. Do this before reinstalling drivers, deleting profiles or replacing the controller.

How do I make my computer detect the joystick?

The computer must receive stable joystick input before the flight simulator can use it.

1. Close the simulator. Some simulators scan for controllers during startup and do not handle hot-plugging reliably. Connect the joystick before reopening the simulator.
2. Check every connection. Reseat the USB cable, detachable grip, throttle cable and external power lead where fitted. A charge-only USB cable can illuminate the controller without carrying any input data.
3. Bypass hubs and adapters. Connect the joystick directly to a known-working USB port. Temporarily remove extension leads and unpowered hubs, especially if the controller repeatedly disconnects.
4. Select the correct hardware mode. Some controllers have separate PC, console, XInput or DirectInput modes. Set the required mode before connecting the device; changing it later may cause the simulator to treat it as a new controller with an empty profile.
5. Test it outside the simulator. On Windows, press Win+R, enter joy.cpl, select the joystick and open its Properties panel. Move the stick, twist grip and throttle through their full travel, then press each button. Our Windows flight-stick testing procedure explains how to interpret each result.
6. Open the simulator's controls menu. Select the joystick itself rather than the keyboard, mouse or gamepad. Make sure an active profile is loaded.
7. Assign the analogue controls. Bind roll to the aileron axis, pitch to the elevator axis, twist or pedals to the rudder axis, and the throttle lever to a throttle axis. Do not bind stick movement to digital commands such as Aileron Left or Elevator Up.
8. Test without competing devices. Disconnect spare gamepads, throttles and virtual controllers temporarily. A duplicate pitch, roll, yaw or throttle assignment can override or fight the joystick.

The joystick does not show up on the computer

If the controller name does not appear in joy.cpl, changing simulator bindings will not fix it because Windows has not detected the hardware.

• No lights or display: check the power switch, external supply, USB cable and port.
• Lights are on, but no device appears: use a data-capable cable, a direct USB port and the correct PC mode. Lights prove that power is present, not that USB data is working.
• A device appears, but nothing moves: reseat detachable controls and check whether the exact model requires its own driver or configuration software.
• It connects and disconnects repeatedly: suspect a loose cable, damaged socket, inadequate hub power or failing controller before editing simulator profiles.

A generic name such as USB Game Controller still counts as successful detection if its axes and buttons respond. Stable input matters more than the displayed product name.

What if a detachable grip or throttle is not responding?

A detachable module must be fully connected to its base before the computer can read it. Disconnect USB and external power, align the connector correctly, secure its collar or latch, and never force exposed pins.

HOTAS designs differ: some throttles connect through the stick base, while others require their own USB connection. If the base is detected but a connected module produces no input in the operating-system test, investigate that module, its connector and its cable rather than simulator bindings.

Why is the joystick listed but not moving in the simulator?

A listed joystick that works in the operating-system test normally needs an active profile and correctly assigned axes.

Set the simulator's controls filter to show all commands, not only assigned commands. Search for controls labelled Axis, move one physical control at a time and watch the on-screen input indicator. A common mistake we see is binding a stick axis to left and right button commands, which produces full deflection rather than proportional control.

• No indicator movement: confirm that the correct controller and profile are selected.
• Indicator movement but no cockpit movement: remove duplicate assignments and disable autopilot, pause and control-assistance features for the test.
• Movement is reversed: use the simulator's reverse-axis option rather than swapping unrelated commands.
• Movement is partial, delayed or drifting: check calibration, centre position and dead zones. Large dead zones can make a working joystick feel completely unresponsive near the centre.

For a precise mapping workflow, use our guide to assigning analogue joystick axes without duplicate or digital bindings. If the problem is specifically in Microsoft Flight Simulator, our MSFS controller and profile troubleshooting steps cover its device profiles, filters and assignment conflicts.

What if both the joystick and throttle do not work?

If both controls fail together, look for a shared connection, power source, hardware mode or empty simulator profile before assuming that two devices failed at once.

• One combined HOTAS unit: check the base's USB connection, external power and the cable between the stick and throttle.
• Two separate USB devices missing from the computer: bypass their shared hub and test each device alone in a direct USB port.
• Both work in Windows but not in the simulator: check whether controllers are enabled globally, then select and configure each device separately.
• The stick works but the throttle does not: the throttle may have an empty profile, the wrong axis assignment or an aircraft-specific engine binding. Follow our throttle detection and axis checks.

Why has the joystick never worked on this computer or console?

A joystick that has never worked may be incompatible with the platform or simulator, set to the wrong input mode, or waiting for its first control profile to be created.

A USB plug alone does not guarantee console compatibility. The console must support that exact controller, and the simulator must accept it on that platform; a Windows driver cannot add console support. Microsoft Flight Simulator 2024 is available on PC, Xbox Series X and S, PlayStation 5 and PlayStation 5 Pro, but peripheral support differs between platforms. Microsoft Flight Simulator 2020 remains a PC and Xbox release and was never released on PlayStation.

On a computer, confirm that the device produces input in the operating-system test. If it does, create a clean simulator profile containing only pitch, roll, yaw and throttle, then test a default aircraft before restoring other assignments.

Should I uninstall and reinstall the simulator or joystick driver?

Uninstalling and reinstalling should be a targeted last step, not the first fix.

• If the joystick is absent from joy.cpl: reinstalling the whole simulator cannot fix USB detection. Concentrate on the port, cable, power, hardware mode and any driver required by that controller.
• If the joystick works in joy.cpl: the driver and basic hardware path are functioning. Create a clean simulator profile before reinstalling anything.
• If the operating system reports a device or driver error: reinstall the correct driver for the exact controller model, then repeat the external input test.
• If simulator files appear damaged: use the platform's verify or repair function before a complete reinstall.

A full reinstall may restore the same broken bindings from a saved or synchronised profile. Back up custom assignments before deleting them, and remember that changing the USB port or controller mode can create a second device identity with a new blank profile.

What if none of these fixes worked?

If the first fixes did not work, isolate one variable at a time instead of repeating the same installation.

1. Return to the original USB port and mode. Check whether the simulator has selected a different, empty profile.
2. Disconnect every other controller. Close input-remapping or virtual-controller software and test only the joystick.
3. Create a minimal profile. Assign only pitch, roll, yaw and throttle, then use a default aircraft.
4. Test another computer if possible. Use the correct mode, a known data-capable cable and a direct USB port.
5. Judge the result. If the axes work correctly on another computer, the original computer or simulator configuration is at fault. If the device remains absent or unstable on both, hardware failure is likely.

Replacement or repair is justified when the joystick receives no power, disconnects as its cable moves, or fails the operating-system test on more than one computer. If its axes and buttons remain stable outside the simulator, the joystick itself is probably sound; focus on compatibility, profiles, assignments and conflicting inputs.