MSFS 2024 Controls Not Working? Fix Joystick, Throttle, and Button Problems

Microsoft Flight Simulator 2024 has the most flexible controller binding system of any consumer sim ever shipped. It also has the most confusing one. Axes go dead for no obvious reason. Profiles silently swap when you change aircraft. A Sim Update lands and suddenly the throttle is bound to the elevator trim wheel. None of this is your fault - the system is genuinely complex - but most of it is fixable in about ten minutes once you understand how the pieces actually fit together.

This guide walks through why the chaos happens, how to build a clean master profile that survives Sim Updates, how to revive an unresponsive axis, and how to spot the hidden conflicting binding that's stealing your input. It covers the hardware most simmers actually use: Honeycomb Alpha and Bravo, Thrustmaster TCA and Warthog, Logitech X52/X56, and the Xbox controller.

Why do my controls stop working when I switch aircraft?

MSFS 2024 has a three-tier profile system. The official documentation describes three layers of control profiles, and they are layered on top of each other for every device you plug in:

1. General Controls - applied across every aircraft, every situation. UI navigation, camera, sim pause, that kind of thing.
2. Aircraft Type Controls - applied to every aircraft in a category. So one set for airplanes, a different set for helicopters, another for gliders.
3. Specific Aircraft Model Controls - applied only when you load that exact model. The PMDG 737 can have completely different bindings to the default Cessna 172.

When you open Settings → Controls, the bindings you see are the merged result of all three layers for whatever aircraft is currently loaded. Change aircraft and the merge re-runs. This is why your buttons "stop working" after switching planes - they didn't stop working, you're now looking at a different combined profile.

The system also auto-applies a profile when it detects a known device. Microsoft's own FAQ notes that most common controllers get a profile set automatically. Plug in a Honeycomb Bravo and MSFS will pick a default Bravo profile for you without asking. Helpful in theory, infuriating in practice, because that default rarely matches the airliner you actually fly. The PMDG forums carry several user threads on reworking Bravo throttle, reverser and gear assignments for the 737. The fix is not to fight the system. The fix is to take control of which profile each device uses.

How do I set up controller profiles properly?

This is the single most important thing you can do. Do it once, properly, and most of the chaos disappears.

Start from a known-good preset, not from blank. Building from scratch sounds appealing but you will miss something - usually a view button or a parking brake - and have no easy way to know what you missed. Instead, pick the closest matching preset (the named ones from the manufacturer, or the MSFS default for your device) and use that as your foundation.

Duplicate before you edit. Open Settings → Controls, select your device, click the cogwheel next to the profile name, and choose Duplicate. Give the duplicate a clear name, something like Mine - Bravo - Airliner or Mine - X56 - GA. Never edit the default profile directly. Community reports suggest that edits to built-in profiles can revert after an update or aircraft change, so always duplicate first. Editing a duplicate avoids that entire class of bug.

Apply the duplicate to all aircraft. When you duplicate or save a profile, the dialog offers an Apply to all aircraft checkbox (and a Set as default one). Tick it so the sim picks your custom profile automatically next time. Two limits catch people out. First, it only covers the device you have selected, so repeat it for the yoke, the throttle, the pedals and anything else you use. Second, community testing reports that it only propagates within one aircraft class: an airplane profile reaches other airplanes, not helicopters or gliders.

Test it by changing aircraft. Load the Cessna 172, confirm the bindings work. Load the 737, confirm they work. Load a helicopter, confirm whatever helicopter profile you've set up loads cleanly. If everything stays sane across three aircraft switches, your master profile is in good shape.

Why is my throttle or joystick not responding?

The classic MSFS 2024 axis problem: you move the throttle, nothing happens, and the sensitivity preview bar doesn't even twitch. At launch this was a genuine sim bug. The Controls axises are not responding report from November 2024 drew confirmations from Honeycomb, Thrustmaster, Virpil and Logitech owners, and it is now tagged fixed on the live build. The symptom still turns up today, but the cause is usually one of the local issues below.

Work through the fixes in this order - most cases resolve within the first three.

1. Confirm the OS sees the device. Press Windows+R, type joy.cpl, and check that your hardware shows under "Installed game controllers" and that moving it produces motion in the Windows test page. If Windows doesn't see it, MSFS never will.

2. Check the active profile. In Settings → Controls, click each device and confirm the profile name is the one you actually built. Sim Updates and new aircraft loads can quietly swap you onto a different profile. If you're staring at "Default - Honeycomb Bravo" when you expected your custom profile, that alone explains why "nothing works."

3. Zero the dead zones to rule out calibration. Select the device, open Hardware Settings, and pick the axis. Set Dead Zone and Extremity Dead Zone to 0 and leave Neutral (the software centre point) at its default. If the preview bar now moves with the hardware, the axis is fine and your settings were just eating the input.

4. Start a fresh flight. This is the cheapest reset. In the axis bug report above, some users found their controls only responded after backing out and launching a new flight session.

5. Full sim restart with everything plugged in first. Quit MSFS completely. Confirm every controller is plugged in and recognised in Windows. Then launch MSFS. The Controls page only lists devices the sim has recognised, so plugging everything in before launch and waiting a few seconds is the simplest way to rule out a late-detected device.

Never use Clear or Delete as a troubleshooting step on a profile you've spent time on. Both options sit on the same cogwheel menu as Duplicate, and both throw away work you cannot get back from inside the sim. If you absolutely have to start over, export the profile first (covered below) so you can re-import after.

Why did a working button suddenly stop doing anything?

The most frustrating MSFS 2024 binding problem isn't the missing binding, it's the conflicting one. When one button, key or switch is mapped to more than one command, pressing it can do something you did not expect, and the command you wanted can look broken. The sim does flag this, but the indicator is easy to miss.

Look for a small number next to the binding. Microsoft's official Controller Settings FAQ calls these mapping conflicts. If you see a number, click the gear icon on that row, and the screen that follows lists the other commands the same button, key or switch is mapped to. Remove the assignment you do not want.

The FAQ also points to a faster tool: Search by input, next to the search bar at the top of the Controls page. Press it, then press the button or move the axis on your hardware, and the sim lists every function that input is mapped to. If the list is empty, the input is not mapped to anything. If it shows two commands, you have found your conflict.

Run through this check whenever a previously working binding "stops". It's faster than rebuilding the bind.

How do I fix bindings for my specific hardware?

These are the patterns that come up most often per device. Specific button-by-button layouts change with firmware updates and aircraft choice, so treat these as starting points rather than gospel.

Honeycomb Alpha + Bravo. The Alpha's default profile is usually fine for general aviation. The Bravo is the one that catches people out, because its levers can mean throttle, prop, mixture, speedbrake or flaps depending on the aircraft, and no single default suits all of them. Duplicate the default preset, then rebuild the lever assignments for the aircraft you actually fly, using its own documentation to decide which lever drives which engine. The PMDG forums have several user threads on Bravo setup for the 737, covering throttle, reverser, gear lever and speedbrake assignments.

Thrustmaster TCA Airbus / TCA Boeing. The TCA throttles work well when the active profile matches the aircraft family (Airbus throttle on an Airbus, Boeing throttle on a Boeing). The recurring pain point on third-party airliners, particularly PMDG and Fenix, is reverse thrust, which often needs a manual rebind because the detent behaviour differs from the stock Airbus/Boeing. If an axis runs backwards (throttle closes when you push it forward), that's axis inversion: open that axis binding and tick its reverse (invert) axis option.

Thrustmaster Warthog HOTAS. The Warthog's twin throttle is the common headache here: the two levers report as separate axes, and if only one of them is bound you get one engine responding and the other ignored. Bind them yourself. The left throttle reports as the RZ axis and the right throttle as the Z axis, so map RZ to "Throttle 1 Axis" and Z to "Throttle 2 Axis." For four-engine aircraft you'll need to split the levers further or pick a different mapping strategy.

Logitech X52 / X56. Both work cleanly as general-aviation HOTAS once you've duplicated the default preset and renamed it. The most-reported X52/X56 issue is the mode selector dial. If you've programmed multiple modes in Logitech's SST software, the X52's mode dial silently changes which set of button IDs the stick sends to MSFS - which can make bindings appear to vanish when you bump the dial. If buttons suddenly do the wrong thing on an X52, check the mode dial first. Based on community reports, the MFD displays on the X52 Pro do not interact with MSFS 2024 out of the box and need third-party software if you want them showing aircraft data.

Xbox controller. The default Xbox profile maps the left stick to pitch and roll and the right stick to camera, with rudder on the triggers. The "Reactivity" smoothing slider that existed in MSFS 2020 has been removed from MSFS 2024, which the forum thread on the topic confirms, with users still asking for it back in 2026. You now manage twitchiness through Sensitivity and the dead zone settings instead. If your controller feels too twitchy, add a small Dead Zone (a few percent) and curve sensitivity downward on the pitch axis. Sim Update 6 also adjusted the default gamepad presets (landing gear now toggles on release, and propeller pitch is now mapped to RB plus D-pad left/right), so re-check any custom gamepad profile you built from the old default.

A note on hardware: If a controller is genuinely failing (drifting axes that no dead zone cures, dead buttons, worn-out pots) rather than just mis-bound, it may be time to replace it. For airliner flying the usual pairing is the Honeycomb Alpha yoke and Bravo throttle quadrant; Airbus pilots tend to run the Thrustmaster TCA Sidestick and Quadrant. On a tighter budget, the Thrustmaster T16000M FCS uses Hall-effect sensors, which avoid the wear that makes potentiometer sticks drift, the T.Flight HOTAS 4 is the budget HOTAS, and the Logitech Extreme 3D Pro is the classic budget entry point. Add a set of rudder pedals once you want proper yaw control. At the premium end, force-feedback hardware adds real control loading: MOZA's AB6 base with the MHG flightstick (or the AY210 yoke base for airliner flying), paired with the MTQ throttle quadrant with swappable Airbus/Boeing lever modules, and the MRP rudder pedals. If you're choosing your first HOTAS or yoke for airliner flying, our best hardware for airliner flying in MSFS 2024 guide covers which combinations cause the fewest binding headaches out of the box.

Why don't my binding changes take effect immediately?

Microsoft does not document any delay. But community reports keep turning up cases where a change looked right in the menu and only behaved after the flight was relaunched, or after a full sim restart. The launch-era axis bug report above is one example: some users only got working controls back by starting a new flight session.

Two things are worth checking before you assume a delay, because they look identical:

• Did you save to the profile that is actually active? If the save prompt created a new profile, or you edited a different tier (General, Aircraft Type or Specific Aircraft) from the one the loaded aircraft uses, the change is real but not in play.
• Is a newly plugged-in device listed at all? The Controls page only shows devices the sim has recognised.

If both check out and the sim still isn't behaving, back out and start a new flight first. If the change still hasn't taken, restart the sim. Don't waste an hour debugging a binding that was already correct.

How do I back up my controller profiles?

The built-in export is the only backup method you should trust. Community tools exist, but the file storage on MSFS 2024 is complicated by Xbox cloud sync, which makes the raw files awkward to grab manually.

Export through the UI: Settings → Controls → select device → click the cogwheel icon next to the profile name → Export. Microsoft's export and import support article says to save the file outside the simulator's installation directory, so a reinstall cannot remove it. A dedicated MSFS 2024 Profile Backups folder on a separate drive (or in OneDrive/Dropbox) is the right move. Repeat for every profile you've spent time on.

Where the raw files live, if you must know: on Steam installs they're under Steam/userdata/<your-steam-id>/2537590/remote. On Microsoft Store / Xbox app installs they sit inside the WGS (cloud sync) folder under %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\wgs, in a structure that isn't safely editable by hand. A forum moderator on the dedicated backup files thread confirmed bindings load from the cloud and should survive a reinstall. That's true most of the time but, as plenty of users have learned the hard way, "most of the time" is not "always."

To restore: Settings → Controls → select device → cogwheel icon → Import → choose your saved file. Microsoft notes two rules: a profile can only be imported to the same controller it was created for, and it must go back into the same category it came from (a General Controls profile cannot be imported as an airplane profile). Once it's in, apply it to all aircraft again if needed.

To move between PCs: export on the source machine, copy the files across, and import on the destination, onto the same model of controller. That is the supported way to carry a profile between machines, rather than copying raw save files.

Why did a Sim Update reset all my bindings?

Often it didn't. Updates do change the stock defaults (Sim Update 6's release notes list changes to the default gamepad presets and the T.Flight HOTAS 4 and 5 profiles, among others), and the usual symptom after an update is that a device is no longer on the profile you expected. Check that before assuming your work is gone. The recovery flow is short.

1. Don't panic and don't clear anything. Your custom profile may well still be there.

2. Open Settings → Controls, pick your first device. Use the arrows next to the profile name to scroll through every available profile. If your custom one is in there, set it active.

3. Repeat for every device. Yoke, throttle quadrant, rudder pedals, secondary HOTAS, controller - every one.

4. Re-apply your profile to all aircraft if needed. Select your custom profile and use Apply to all aircraft again. Then check by loading the aircraft you fly most and confirming the right profile loaded.

5. If your custom profile is genuinely gone, import from the backup you exported. You did export a backup, right?

6. Check the conflict numbers. If an update changed a default profile you built on, a new default mapping can collide with one of yours. Use Search by input on the high-traffic controls (gear, flaps, parking brake, autopilot disconnect) and look for conflict counts.

The full recovery, including conflict cleanup, takes about fifteen minutes if you have backups. Without backups it can take hours of rebuilding. The first time you finish a master profile, export it. The second time, export it to two places. There is no good reason not to.

What if none of this fixes my controller?

If you've worked through every step above and the sim still ignores a device, the issue is usually one of three things:

• The device firmware or driver is out of date. Most controller makers ship firmware or driver updates through their own software. Check the manufacturer's tool.
• A USB hub is getting in the way. Plug the problem controller directly into the PC, not through a hub, and retest.
• A third-party app is intercepting the inputs. Joystick Gremlin, vJoy, SimConnect bridges and various streaming-deck companions all sit between the hardware and MSFS. Close them and retest.

If the device still does nothing in MSFS but works fine in joy.cpl, search the official forums for your exact device name plus the current sim build number - chances are someone else has hit the same combination this week.

The binding system in MSFS 2024 will get easier to live with as Asobo continues iterating on it, but for now the rule is the same as for any complex sim: own your profiles, back them up, and never trust the defaults.