Fix Logitech yoke buttons not working in MSFS 2024 by choosing the right profile, removing conflicts, testing inputs and saving clean bindings.
Logitech yoke button assignments usually fail in Microsoft Flight Simulator 2024 because the wrong device or control profile is being edited, the button has a conflicting binding, or MSFS has not detected the input. Select the yoke, use Search by Input, remove duplicates, bind the command, then save and activate that profile.
How do I fix Logitech yoke button assignments?
- Select the Logitech yoke itself. Open the MSFS 2024 control settings and choose the Logitech or Saitek yoke from the connected-device list. Do not edit the keyboard, mouse, Xbox controller or a separately connected throttle quadrant by mistake.
- Check the active control profile. Confirm that the yoke profile shown as active is the one you intend to change. If the default preset is protected or confusing, duplicate it and give the new profile a recognisable name.
- Find the button through Search by Input. Activate Search by Input, then press and release the physical button once. MSFS should reveal every command already attached to that input. Change the control filter if necessary so unassigned and conflicting commands are not hidden.
- Remove unwanted assignments. Clear commands that should not run from that button, particularly camera, menu and cockpit-interaction bindings. Also inspect other connected controllers for controls that continually send an opposing input.
- Bind the correct command type. A momentary push-button normally needs a toggle or single-action command. A maintained two-position switch is better matched to separate on/off or set commands when those are available. Binding a momentary button to only the on half of a command can make it appear ineffective or leave the function stuck.
- Save and apply the profile. Do this before leaving the control screen, then verify that the same profile remains active. A mistake we see constantly is editing one preset and returning to the cockpit with another preset selected.
- Test in a default aircraft. If the button works there but not in a particular add-on aircraft, the yoke and profile are functioning. That aircraft may use a custom system rather than the standard simulator command.
If the axes and basic buttons have never been configured, our MSFS 2024 yoke setup sequence covers the initial device profile, axis selection and duplicate-binding checks.
Why does the assignment appear but do nothing?
An assignment shown in the controls screen can still fail if it belongs to the wrong profile, uses the wrong command variant or is overridden by another input. Use the symptom to narrow down the cause:
| Symptom | Likely cause | What to do |
|---|---|---|
| Search by Input shows nothing | USB or device-detection problem | Test the button in Windows and reconnect the yoke before starting MSFS. |
| The button performs the wrong action | Duplicate or inherited assignment | Search by Input and remove every unrelated command attached to that button. |
| The control moves only while held | Momentary button bound to a hold or set command | Use the corresponding toggle command, if appropriate. |
| It works in one aircraft only | Aircraft-specific command handling or profile selection | Compare the active profile and test the standard simulator command in a default aircraft. |
| The binding disappears after leaving settings | Wrong preset edited or profile not saved | Create a fresh custom yoke profile, apply it and confirm that it remains selected. |
If a button opens an external view, changes the camera or triggers another unexpected function, follow our method for tracing an incorrect yoke button action. It explains how to expose assignments that are easy to miss when the controls list is filtered.
How can I tell whether the yoke or MSFS profile is faulty?
Windows input testing separates a hardware problem from an MSFS binding problem. On PC, press Windows+R, enter joy.cpl, select the yoke, open its properties and press each suspect button.
- No response in Windows: connect the yoke directly to another USB port, bypass an unpowered hub and reconnect it before launching MSFS. If it remains absent, the issue is outside the simulator.
- Windows responds but Search by Input does not: restart MSFS with the yoke already connected, confirm that the correct device tile is selected and check for controller utilities remapping the button to a keyboard command.
- Both Windows and MSFS detect it: the fault is almost certainly the selected command, an assignment conflict, the active profile or the aircraft being tested.
The bundled Logitech throttle quadrant connects through the yoke and can therefore report its switches under the yoke device. A standalone USB quadrant appears separately. For USB, driver and device-detection faults affecting more than one control, use our hardware checks for Logitech flight controls.
The standard PC Logitech G/Saitek Flight Yoke is not made compatible with Xbox Series X|S or PlayStation 5 merely by creating an MSFS binding. Console users need flight-control hardware explicitly supported by their console platform.
Why do Logitech yoke bindings keep resetting?
Bindings usually seem to reset because MSFS has switched profiles, the changes were made under another device, or the custom preset has become unreliable. Create a new yoke-only profile, bind one test button, save it, restart the simulator and confirm that the test survives before rebuilding the rest.
Do not erase every controller at once; that makes it harder to identify the original fault. If a clean profile also refuses to retain assignments, use the controlled steps for clearing or restoring MSFS controller bindings, then rebuild only the yoke commands you actually use.