Logitech flight controls not working: how do I fix the yoke, throttle or pedals?
Logitech flight controls not working? Diagnose a yoke, Saitek Pro Flight Quadrant or pedals with USB tests, driver fixes and axis setup.
Logitech flight controls usually stop working because Windows has not detected the USB device, the supplied throttle quadrant is connected incorrectly, the simulator has loaded the wrong controller profile, or an axis is unassigned or duplicated. Test the yoke, throttle and pedals in joy.cpl first, then repair only the layer that fails.
This is a general PC flight-simulator diagnosis for Microsoft Flight Simulator, FSX, Prepar3D, X-Plane and DCS. Older hardware may appear under Saitek, Pro Flight or Logitech G; the different name does not itself indicate a fault.
Our community is international, so we see the same problem described as no los detecta, da tut sich nichts, jak naprawic or sigue igual. These amount to not detected, nothing happens, how to fix it, or still unchanged. The decisive test is whether Windows receives the controller input before the simulator opens.
Why does my Logitech yoke not pop up in Windows?
If the yoke does not appear in the Windows Game Controllers panel, troubleshoot its USB connection, driver or hardware before changing simulator settings.
- Close the simulator. Disconnect the controls and restart the PC. Profiling software and the simulator should remain closed during the first test.
- Check how the quadrant connects. The throttle supplied with many Logitech G/Saitek Pro Flight Yoke Systems uses a round proprietary connector and plugs into the yoke. A standalone Pro Flight Throttle Quadrant has its own USB connection. Do not force the round plug into a computer socket or use an unverified adapter.
- Use a direct USB port. Connect the yoke directly to the PC, preferably to a rear motherboard port on a desktop. Temporarily avoid monitor ports, keyboard ports, extension leads and unpowered hubs.
- Open the controller panel. Press Windows key and R, enter
joy.cpl, and press Enter. Select the Logitech or Saitek device and open its properties. - Test every input. Move the yoke through pitch and roll, operate all quadrant levers, press the buttons, and test rudder and toe-brake travel. A light or display turning on does not prove that the USB data connection is working.
- Add devices one at a time. Start with the yoke, then connect separate pedals or a standalone USB quadrant. If several controls disappear only when used together, suspect the hub, USB power delivery or one faulty device.
If the answer is “no, it does not pop up” in joy.cpl, try another direct port and inspect Device Manager for an unknown or failed USB device. If practical, test the controller on a second PC. Failure on two computers and several ports points towards the cable, connector or controller electronics rather than a simulator profile.
For the packaged unit, follow our detailed wiring and first-time test for the Logitech G yoke system.
Should the Saitek Pro Flight Quadrant appear as a separate device?
A quadrant supplied with the yoke normally reports through the yoke and may not appear as a second controller; a standalone USB quadrant should have its own entry.
- Both yoke and supplied quadrant are dead: troubleshoot the yoke's USB connection first because the quadrant depends on it.
- The yoke works but the supplied quadrant does nothing: disconnect the yoke from USB, inspect and firmly reseat the quadrant's round connector, then reconnect the yoke.
- A standalone USB quadrant is missing: test its own cable and USB port independently of the yoke.
- The levers work but the quadrant buttons do not: check the button assignments in the simulator. Buttons and analogue axes are mapped separately.
Why does Windows detect both controls but nothing happens in the simulator?
If the controls move correctly in joy.cpl, the hardware is working and the fault is usually the active simulator profile, an absent assignment or a duplicate binding.
| Physical control | Correct assignment type | Common wrong assignment |
|---|---|---|
| Yoke left and right | Aileron or roll axis | Aileron-left and aileron-right buttons |
| Yoke forward and back | Elevator or pitch axis | Elevator-up and elevator-down buttons |
| Main throttle | Throttle axis or individual engine throttle | Binding both all-engine and individual-engine axes |
| Propeller and mixture levers | Propeller and mixture axes | Testing them in an aircraft that does not use those controls |
| Pedal movement | Rudder or yaw axis | Rudder-left and rudder-right buttons |
| Toe brakes | Separate left and right brake axes | One combined brake command or unreversed axes |
Assign each physical lever or control to an analogue axis. If the terminology is unfamiliar, our guide to mapping analogue axes and controller buttons explains how to identify an input and remove conflicting assignments.
- Microsoft Flight Simulator 2020 and 2024: select each device separately in Controls, verify which preset or profile is active, and search by moving the physical input. Change the filter if it is hiding unassigned commands. MSFS 2024 users should also check these MSFS 2024 profile and binding fixes.
- FSX and Prepar3D: confirm that controllers are enabled, choose the correct device, and assign controls in the axes section rather than the button section.
- X-Plane: calibrate every detected device and inspect the profile selected for the loaded aircraft. An assignment saved to one aircraft profile may not exist in another.
- DCS: bindings are stored by aircraft and device column. Remove automatic pitch, roll, rudder and throttle assignments from gamepads or other controllers that should not operate them.
A mistake we see constantly is assigning the Logitech yoke correctly while leaving the same axis bound to a gamepad, joystick or second throttle. The two inputs then fight, causing recentering, reduced travel or movement that appears to ignore the yoke.
Why is the yoke, throttle or brake axis reversed or jumping?
Reverse an axis in one place only, and compare its simulator behaviour with the raw movement shown in joy.cpl.
- Throttle moves backwards: enable the simulator's reverse-axis option. Do not also reverse it in Logitech profiling software.
- Brakes remain applied: reverse the left and right toe-brake axes separately. Pedal movement, left brake and right brake are three independent axes.
- Only part of the travel works: restore a simple linear sensitivity curve, recalibrate where the device offers that option, and check for an aircraft-specific throttle calibration.
- The control jitters around the centre: apply a small dead zone. If the Windows indicator also flickers, the likely cause is USB instability or a worn sensor; a large dead zone only masks it.
- The cockpit control moves and returns by itself: remove duplicate bindings and check autopilot, autothrottle, AI assistance and aircraft-specific control logic.
Complex airliners may require throttle detents or lever ranges to be calibrated through their own cockpit tablet or configuration panel. A throttle that works in a default aircraft but not in one add-on is therefore unlikely to have a Windows driver fault.
Do Logitech and Saitek flight controls need drivers?
Many basic yoke, pedal and throttle axes can be recognised as standard Windows game controllers, but model-specific software may be needed for profiles, mode functions or older hardware.
Do not reinstall drivers merely because the simulator has no response when every axis already works in joy.cpl. Reinstall only when the device is absent, appears with an error, repeatedly disconnects, or conflicting Logitech and legacy Saitek packages are installed.
- Disconnect the controller. Close Logitech and Saitek background software.
- Remove conflicting packages. Avoid keeping an old Saitek profiler, disc-era driver and newer Logitech package installed together unless the hardware explicitly requires them. Use our clean removal sequence for mixed Saitek and Logitech drivers when both generations are present.
- Restart Windows. This clears driver components that remain loaded until reboot.
- Install one appropriate package. Use software intended for the exact model and supported Windows edition, connecting the controller at the stage requested by the installer.
- Retest in
joy.cpl. Do this before restoring profiles or opening the simulator.
Controls that vanish after sleep or part-way through a flight often indicate USB power management or an overloaded hub. Test with non-essential USB equipment disconnected. Switch panels, radio panels and instrument panels are a separate class of device and may require simulator-specific plug-ins even when the yoke axes work normally.
What should I do if it still won't work or sigue igual?
The remaining cause can be identified by where the signal stops rather than by repeatedly reinstalling everything.
| Result | Most likely area to repair |
|---|---|
No entry in joy.cpl on two PCs | Cable, connector or controller hardware |
| Works on another PC | Windows USB configuration or driver installation on the first PC |
| All inputs work in Windows but not the simulator | Active profile, assignments or controller enable setting |
| Works in default aircraft only | Aircraft-specific profile, detent calibration or cockpit logic |
| Several devices disconnect together | USB hub, port or power delivery |
| Yoke works but attached quadrant remains dead | Round connector, quadrant cable or quadrant hardware |
Will Logitech PC flight controls work on Xbox or PlayStation?
A USB plug does not make a Logitech or Saitek PC controller compatible with a console; the exact model must be supported by that console and simulator.
Microsoft Flight Simulator 2024 is available on PC, Xbox Series X|S, PlayStation 5 and PS5 Pro, while Microsoft Flight Simulator 2020 remains on PC and Xbox only. Console editions cannot use Windows drivers, joy.cpl or PC profiling software. If the yoke is not listed for the intended console, changing bindings will not make it compatible.