Why won't my flight simulator recognise my joystick?

In a general PC flight simulator, a joystick usually is not recognised because the operating system cannot see it, the simulator has opened an empty controller profile, or its analogue axes are not assigned. Test the device outside the simulator first; that single check tells you whether to fix USB hardware or simulator settings.

My controller isn’t working: find the failed layer

The quickest diagnosis is to check whether the joystick produces input before the simulator opens. Statements such as “my controller isnt working”, “it's not workin” or “не роботает” describe several different faults; the result of this one test identifies the correct branch.

If the answer to “Do the axes move outside the simulator?” is no — even if all you can say is “nein” — stay with the USB, driver and hardware branch. Our fault-isolation checklist for joystick, USB and simulator problems expands that diagnosis without assuming the joystick itself is broken.

How do I make my flight simulator detect the joystick?

Make the operating system see stable axis movement before changing simulator settings.

1. Close the simulator completely. Some simulators enumerate controllers only during startup. Connect the joystick before reopening the software rather than relying on hot-plug detection.
2. Check every physical connection. Seat the USB cable, detachable grip, throttle connection and external power lead where fitted. A detachable USB cable must carry data; a charge-only cable can provide lights without allowing the computer to detect the controller.
3. Use a direct USB port. Temporarily remove unpowered hubs, extension leads and adapters. Try another known-working port, preferably with other high-power USB devices disconnected for the test.
4. Select the correct hardware mode. Some controllers have PC, console, XInput or DirectInput settings. Choose the appropriate mode before connecting the device and opening the simulator; changing mode can make it appear as a different controller with a new empty profile.
5. Test it in the operating system. On Windows, press Win+R, enter joy.cpl, select the controller and open its Properties panel. Move the stick, twist grip and throttle through their full travel, then press each button. On another desktop operating system, use its controller or input-device panel for the same test.
6. Select the device inside the simulator. Open the controls or input menu and choose the joystick itself, not the keyboard, mouse or gamepad. Activate an existing profile or create a test profile. A device name can appear while its selected profile contains no assignments.
7. Bind the analogue axes. Assign left/right movement to the aileron or roll axis, forward/back movement to the elevator or pitch axis, twist or pedals to the rudder or yaw axis, and the lever to the throttle axis. Do not use digital commands such as Aileron Left or Elevator Up for stick movement. Our axis-mapping instructions explain how to select and bind the correct controls.
8. Remove competing inputs. Inspect connected gamepads, throttles, pedals and virtual controllers for duplicate pitch, roll, yaw or throttle bindings. Test a simple default aircraft with autopilot, active pause and control-assistance features off.

“It’s not detecting it” and the device name does not appear

If the controller name is missing from joy.cpl, the simulator cannot repair the problem because Windows has not detected the hardware. The symptom “名前が出ない” means that the name does not appear, while “нет не видит” means that it still is not seen; both point to this USB or operating-system branch.

If by “gada apa apa” you mean that nothing appears or happens, look first for a power light and then for an operating-system entry. The result narrows the cause:

• No light or display: check the power switch, external supply, detachable cable and USB port.
• Lights are on but no device is listed: try a data-capable cable, another direct port and the correct PC or console mode.
• A device is listed but no axes move: reseat modular controls, confirm the mode switch and check whether the exact model requires its own driver.
• It repeatedly connects and disconnects: suspect a loose cable, insufficient hub power or a damaged connector before editing profiles.

A generic name such as a USB game controller still counts as detection if its axes and buttons respond. The displayed product name matters less than stable input.

What if a detachable joystick lever, grip or throttle is not responding?

A detachable joystick lever or grip must be fully seated in its base before the operating system can read its axes and buttons. Disconnect power and USB first, align the connector correctly, secure its collar or latch, and never force exposed pins.

HOTAS throttles vary: some connect through the stick base, while others need their own USB connection. If the base appears in the operating-system test but the detachable section produces no input there, the interconnecting cable, connector or module is the likely fault — not the simulator binding.

Can any USB joystick work on a console flight simulator?

No. A console must support the controller, and the simulator must accept it on that platform; having a USB plug or working on a PC is not enough. PC drivers cannot add console compatibility.

Microsoft Flight Simulator 2024 is available on PC, Xbox Series X|S, PS5 and PS5 Pro, but peripheral support differs between those platforms. Microsoft Flight Simulator 2020 remains a PC and Xbox release and was never released on PlayStation. Do not assume that a joystick recognised by one console will work on another.

Why is the joystick listed but it’s not moving?

A listed joystick has passed basic detection, so the remaining fault is normally its profile, assignments, calibration or an input conflict. Buttons working does not prove that the pitch and roll axes have been assigned.

Set the controls-menu filter to show all available commands rather than only assigned ones, then bind commands labelled Axis. Move one control at a time and watch the simulator’s input indicator. If an indicator moves in the settings screen, the simulator is receiving that input.

• The indicator does not move: select the correct device and profile, then retest it in the operating system.
• The indicator moves but the virtual controls do not: remove duplicate axes and disable the autopilot or assistance features for the test.
• The virtual controls move but the aircraft does not: the joystick is recognised. Check pause state, parking brake, engine condition, wheel chocks where modelled and aircraft-specific systems.
• The axis moves only partly, drifts or starts late: calibrate its range, centre and dead zone. Use our PC joystick calibration and profile checks rather than compensating with an extreme dead zone.

For Microsoft Flight Simulator, follow our MSFS-specific device, profile and binding troubleshooting if Windows detects the controller but the simulator does not respond.

I did that, but it’s still not working

After the standard checks, one controlled isolation test is more useful than repeatedly reinstalling drivers. If your position is “did that” or “continua a non andare” — it still does not work — change one variable at a time:

1. Return to the original USB port and mode. A simulator may treat another port or input mode as a new device and select a blank profile.
2. Disconnect other controllers temporarily. Remove gamepads, spare throttles and pedals, and close software that creates a virtual controller or translates joystick input.
3. Create a clean test profile. Keep the old custom profile rather than deleting it. Assign only pitch, roll, yaw and throttle, then test a default aircraft.
4. Check what changed. A controller that worked before may have stopped after a profile reset, USB-port change, driver change or activation of an input-remapping layer.
5. Test another computer where possible. Use the correct hardware mode and a known data-capable cable. This separates a computer configuration problem from a failing controller.

The joystick itself is probably faulty if it receives no power, disconnects when its cable is moved, or remains absent from the operating system on more than one computer. If its axes work correctly outside the simulator, replacing it is unlikely to help; concentrate on simulator support, profiles, assignments and input conflicts.