How do I map and save controller bindings in MSFS 2024?
Open Settings > Controls in Microsoft Flight Simulator 2024, select the joystick or gamepad itself, then duplicate its default preset or create a custom one. Assign commands by scanning each axis or pressing a button, save or apply the preset, and leave it selected for that device. Repeat for every connected controller.
How to map joystick or controller bindings
The safest method is to create an editable preset for each physical device rather than changing several controllers at once.
- Connect the controller before starting the simulator. Confirm that it appears in the Controls screen. On PC, if it is missing or an axis does not respond, first check that Windows detects every joystick axis and button.
- Select the correct device. Open Settings > Controls and choose the named joystick, throttle, pedals or gamepad from the device list. Bindings are stored separately for each device.
- Create a custom preset. Duplicate the default preset if its basic assignments are sensible. Start with a blank custom preset when the device has numerous unwanted automatic mappings. Built-in presets may not be directly editable, and a custom copy also gives you an easy route back to the original.
- Find the required command. Change the filter to the all-controls view if searches return nothing, then search by action name. Select the binding field and use the scanning function, moving one axis or pressing one button without touching anything else.
- Confirm the input. Move an analogue control through most of its travel so MSFS 2024 identifies the correct axis. For a button, press it once. Accept the assignment, then check for a duplicate-input warning.
- Remove unintended conflicts. A warning is harmless when commands operate in different contexts, but two pitch, roll, rudder or throttle assignments can make the aircraft twitch or ignore inputs. Clear the unwanted binding from the other device or preset.
- Save and verify the preset. Use the save or apply command shown by the Controls screen, confirm that your custom preset remains selected, then return to the cockpit and test it. Repeat these steps for the throttle, pedals and any other separate USB device.
On Xbox Series X|S and PlayStation 5, the procedure is similar, but the console must recognise the peripheral itself. A PC-only USB joystick cannot be made console-compatible by assigning it inside the simulator.
Which controls should I bind first?
Map continuous hardware controls to axis commands and reserve directional or incremental commands for buttons. A mistake we see constantly is binding a joystick axis to left/right or up/down button commands, producing abrupt, binary control movement.
| Physical input | Preferred binding | Avoid for analogue hardware |
|---|---|---|
| Stick X-axis | Ailerons Axis | Aileron left/right commands |
| Stick Y-axis | Elevator Axis | Elevator up/down commands |
| Twist grip or pedals | Rudder Axis | Rudder left/right commands |
| Throttle lever | Common throttle axis, or numbered engine axes for separate levers | Increase/decrease throttle commands |
| Analogue toe brakes | Left and right brake axes | Parking brake or full-brake button commands |
After the primary axes, assign elevator trim, brakes, landing gear, flaps, cockpit view controls and autopilot disconnect. Command wording can vary slightly by aircraft and control context. Owners of Airbus-style hardware can use our device-specific Thrustmaster TCA mapping workflow for separate engine axes, detents and duplicate assignments.
Why do saved bindings disappear or change?
Saved bindings usually appear to be missing because MSFS 2024 has loaded a different device preset or control context.
- The default preset is active: reopen Controls and select the custom preset you saved.
- The wrong device is selected: a joystick, throttle and pedal set each has its own bindings and preset selection.
- The aircraft changed: some preset choices or control contexts can differ by aircraft. Check the active aircraft-control preset after loading another aeroplane or helicopter.
- The command is in another context: aircraft, general and camera controls are separated. Make sure the assignment was created in the relevant control set.
- Windows created another device instance: reconnecting through a different USB port or hub can occasionally make hardware appear as a separate device. Select the newly detected entry or return it to its usual port.
- The edit was not applied: reopen the preset immediately after saving and verify that the binding is present before configuring the next device.
If presets have become cluttered or unusable, follow our instructions for clearing and rebuilding MSFS controller profiles rather than deleting individual assignments at random.
How do I fix reversed, drifting or doubled inputs?
Most bad control behaviour comes from axis direction, dead zones or the same flight control being assigned to more than one device.
- Reversed movement: enable the binding's reverse-axis option, then check both ends of the travel. Do not use a negative sensitivity setting merely to reverse an axis.
- Drift near the centre: add only enough dead zone to stop the unwanted movement. Excessive dead zone makes the aircraft feel unresponsive around neutral.
- Jerking or double movement: filter the controls by assigned inputs and remove duplicate pitch, roll, rudder and throttle axes from unused gamepads or throttles.
- An axis moves in Controls but not in the aircraft: confirm that it is mapped to an axis command appropriate to that aircraft. A helicopter collective, for example, is not necessarily controlled by an aeroplane throttle assignment.
- Travel does not reach its limits: check the device outside MSFS first, then adjust sensitivity and extremity settings only after confirming that the hardware reports its full range.