Cockpit controls not working with the mouse in Microsoft Flight Simulator? Fix interaction mode, bindings, focus, power and aircraft-specific faults.
If cockpit controls will not move with the mouse in Microsoft Flight Simulator, release cockpit freelook, restore the Mouse device’s default control profile, and switch the Cockpit Interaction System between Legacy and Lock. Then remove conflicting bindings, confirm the aircraft has power, and test a default aircraft to separate an input fault from an aircraft-specific one.
Fastest cockpit mouse fix checklist
Most widespread mouse-interaction failures come from captured camera input, the wrong interaction mode or a damaged custom profile.
- Release camera control. Let go of the right mouse button and cancel any active freelook toggle. Close open toolbar panels, then click inside the simulator window to restore focus.
- Change the interaction mode. Search the general settings for Cockpit Interaction System or “cockpit interaction”, then change Legacy to Lock or Lock to Legacy. Save the change before testing again.
- Restore the Mouse preset. Open the control settings, select the Mouse device and choose its built-in Default profile. Record any custom assignments first; do not reset the joystick, throttle or controller unnecessarily.
- Check for conflicting inputs. Use the control-options search-by-input function with the left button, right button and wheel. Remove accidental duplicates that assign the same input to camera, menu and cockpit actions.
- Test a powered default aircraft. Load a standard aircraft, switch on its battery and avionics as required, and try an obvious unguarded switch. This removes third-party aircraft logic from the test.
- Disable suspect add-ons. If default aircraft work, temporarily deactivate the affected aircraft and any cockpit, toolbar or interface modifications, then test them individually.
Microsoft Flight Simulator 2024 has a few additional focus and profile failure modes; our MSFS 2024 cockpit-click troubleshooting steps cover those version-specific checks. On Xbox, also follow the Xbox mouse-profile and controller-focus checks, because a controller can retain interface focus while the mouse pointer still moves.
Should I use Legacy or Lock cockpit interaction?
Legacy is generally the more direct choice for a PC mouse, while Lock suits highlight-based selection and mixed controller use. Neither mode is universally better, so use the one that operates your aircraft’s hotspots reliably.
| Mode | How it behaves | Choose it when |
|---|---|---|
| Legacy | Point directly at a hotspot, then click, drag or turn the wheel according to the control. | You use a physical mouse and want conventional desktop-style cockpit interaction. |
| Lock | The control highlights and remains selected while you perform the prompted action. | You use a controller, prefer prominent highlighting or struggle to hold the pointer over small hotspots. |
Interaction tooltips can help while testing because they show whether a control expects a click, wheel movement or drag. Switching tooltips off only hides those instructions; it does not disable the control itself.
Why does a highlighted switch still not move?
A highlight confirms that Microsoft Flight Simulator has found a cockpit hotspot, but the control may require a different action or aircraft state.
- Compound knobs have separate hotspots. The inner knob, outer knob and push function may each occupy a different part of the same control.
- Some switches are guarded. Open the cover before trying to move the switch beneath it.
- Rotary controls may require the wheel or a drag. If the wheel zooms the camera instead, release freelook and recheck the wheel’s camera bindings.
- Aircraft power matters. Avionics keys, electrically actuated controls and displays may do nothing until the correct battery, bus or avionics master is active.
- Not every visible control is modelled. A decorative or
INOPcontrol cannot be fixed through mouse settings.
If a switch moves and immediately returns, look for a spring-loaded real-world function first. Otherwise, disconnect controllers one at a time and disable piloting assistance temporarily; a duplicated hardware assignment or automated system may be continuously commanding the opposite position.
Why do G1000 or FMS knobs fail while other controls work?
Avionics-only failures usually point to electrical power, a missed inner or outer knob hotspot, cursor focus, or duplicated wheel and button bindings rather than a broken mouse.
Confirm the appropriate electrical buses and avionics switches are on, then test the knob’s centre, inner ring, outer ring and push action separately. For deeper diagnosis, use our targeted G1000 and FMS control fixes.
How can I separate a mouse fault from an aircraft fault?
Compare the same simple control in a default aircraft and the affected aircraft under similar powered conditions.
| Symptom | Most likely cause |
|---|---|
| No cockpit controls work in any aircraft, but menus respond | Interaction mode, Mouse profile or cockpit focus |
| Only one aircraft is affected | Aircraft-specific hotspot, state logic or add-on fault |
| Only powered avionics are unresponsive | Battery, avionics master, electrical bus or avionics-specific binding |
| Controls move and then snap back | Spring-loaded function, duplicate hardware input or piloting assistance |
| The pointer disappears and cockpit panning also fails | Camera capture, window focus or mouse-look binding |
If mouse look is broken as well as cockpit interaction, diagnose the camera system first using our mouse-look and cockpit-panning checks. A camera-focus fault can make working cockpit controls appear completely unresponsive.