How do I set up a joystick in MSFS 2020?

Plug the joystick into Windows before launching Microsoft Flight Simulator 2020, verify that its axes respond, then open Options > Controls Options. Select the joystick, duplicate or create a control profile, bind the analogue flight-control axes, remove duplicate assignments, adjust dead zones only where needed, and finish with Apply & Save.

Microsoft Flight Simulator 2020 joystick setup steps

1. Connect and test the joystick in Windows. Press Windows key + R, run joy.cpl, select the controller and open Properties. Check that every axis moves smoothly, centres correctly and reaches both ends. If it does not, use our detailed procedure for checking every joystick axis and button in Windows before changing anything in the simulator.
2. Open the controller settings. Start MSFS 2020 and go to Options > Controls Options. Select the joystick from the devices shown across the top; make sure you have not accidentally selected the keyboard, mouse or another controller.
3. Create a custom preset. Open Preset Manager and duplicate the device's default preset, or create a new preset if it has no useful default. Give it a recognisable name so that you do not overwrite a working layout while experimenting.
4. Show every available command. Change the control filter from Assigned to All. Search for each required command, select its binding box, use Search by Input or move the relevant control, then validate the assignment.
5. Check sensitivity and direction. Open the Sensitivity panel and move each axis through its full range. Correct reversed axes and add only enough dead zone to stop unwanted movement around the centre.
6. Save and test. Select Apply & Save, load a simple aircraft such as the Cessna 152 and test roll, pitch, yaw and throttle. Use an external view to confirm that the control surfaces move in the expected direction.

Which joystick axes should I assign in MSFS 2020?

A joystick should use the commands containing Axis; the similarly named left, right, up and down commands are intended for buttons or keys.

The plain Throttle Axis command can be appropriate for hardware with a below-idle or reverse region. For an ordinary joystick lever running from idle at one end to full power at the other, the 0-to-100% command is usually easier to configure.

After the main axes work, assign only the buttons you need regularly: elevator trim, wheel brakes, flaps, landing gear, cockpit view reset and the parking brake. Adding dozens of commands at once makes conflicts much harder to diagnose.

How should joystick sensitivity and dead zones be set?

Start with the default response and tune only the behaviour you can actually see or feel; there is no universal best sensitivity setting for every joystick.

• Dead zone: Increase it slightly if the aircraft rolls, pitches or yaws while the joystick is physically centred. A large dead zone makes fine corrections difficult.
• Sensitivity: A gentler response around the centre can help a short-throw joystick, particularly during landing. Keep enough authority to reach full control deflection.
• Reverse Axis: Use this when a control moves in the opposite direction. Pulling back should command nose-up elevator, and advancing the throttle should increase power.
• Reactivity: Leave it at its default unless you deliberately want to smooth abrupt input. Reducing it can also make controls feel delayed.
• Extremity and neutral adjustments: Use these only to correct a demonstrated range or centre problem. They are not substitutes for proper hardware calibration.

Control profiles for different aircraft

One general preset is enough for most single-engine aircraft, but separate profiles help when switching to multi-engine throttles, helicopters or aircraft with reverse-thrust detents. MSFS stores a preset for each listed device, so a separate stick, throttle and pedal set each needs its own assignments.

Advanced HOTAS equipment may appear as several devices and can therefore create duplicate axes. Owners of that hardware can use our hardware-specific WinWing mapping steps for the same profile-by-profile approach.

Why does MSFS 2020 detect the joystick but ignore it?

A detected joystick usually fails because the wrong preset is active, an axis has been bound to a button command, the changes were not saved, or another device is sending a conflicting input.

• Confirm that the joystick is selected and that its intended custom preset is active.
• Set the filter to All; the Assigned filter hides commands that have not yet been mapped.
• Use Search by Input and move the problem axis. Remove every unrelated command returned for that input.
• Check the keyboard, gamepad, throttle and pedals for a second aileron, elevator, rudder or throttle assignment.
• If the control jumps straight to full deflection, replace directional button bindings with the corresponding Axis command.
• If the simulator appears to fight your input, disable AI piloting and any take-off or landing assistance that is controlling the aircraft.
• If movement also disappears in joy.cpl, reconnect the device directly rather than through an unreliable hub and resolve the Windows or hardware problem first.

When a preset has accumulated too many unknown assignments, starting clean is faster than chasing them individually. Our guide to clearing duplicate or unwanted MSFS controller bindings explains how to rebuild the profile without disturbing other devices.

Can I use the same joystick setup on Xbox?

Only Xbox-compatible flight controls are recognised by the console version of Microsoft Flight Simulator; an ordinary PC USB joystick will not work merely because it has a USB connector. Supported hardware is configured through Controls Options using the same axis principles, but console device support and button availability differ. Our Xbox installation and control checklist covers the console-specific setup.