Use a PS5 DualSense with MSFS 2020 or 2024 on PC. Compare USB, Bluetooth and Steam Input, map flight controls, and fix common faults.
A PS5 DualSense works with Microsoft Flight Simulator 2020 and 2024 on Windows. Connect it by data-capable USB-C cable or Bluetooth, verify it in Windows, then create a custom MSFS profile. If native detection fails, use Steam Input or one XInput translation layer, avoiding simultaneous physical and virtual bindings.
Should I connect the DualSense by USB or Bluetooth?
USB is the best choice for initial setup because it removes pairing, battery and wireless-interference problems. Use a data-capable cable: a charge-only cable can light the controller without making it available to Windows.
- Connect by USB: plug the DualSense into the PC before starting Microsoft Flight Simulator.
- Or pair by Bluetooth: hold the Create and PS buttons until the light bar flashes, then add it through Windows Bluetooth settings. It normally appears as
Wireless Controller. - Test it in Windows: press
Windows+R, enterjoy.cpl, open the controller’s properties and check its sticks, triggers and buttons.
If it fails in joy.cpl, do not start changing MSFS assignments. Try another USB data cable, USB port or Bluetooth adapter, or charge and pair the controller again.
How do I set up the PS5 controller in Microsoft Flight Simulator?
Once Windows detects the controller, create a dedicated preset in MSFS rather than relying on an incomplete or empty automatic profile.
- Open the controls screen: start MSFS and open Controls or Controls Options, depending on the simulator version.
- Select the detected device: look for DualSense, Wireless Controller, Gamepad or an emulated Xbox controller.
- Show all commands: change the filter from assigned controls to all available controls if the command list appears empty.
- Create a custom preset: duplicate an editable preset or create a new one instead of trying to alter a protected default.
- Scan each input: use the input-search function, move one stick or press one button, and confirm that only the intended input responds.
- Assign the essential controls: map the flight axes, rudder, trim, brakes, throttle, views, flaps and landing gear before adding less-used cockpit functions.
- Apply and test: confirm that the new preset remains selected, then test it on the ground and in a simple aircraft.
If Windows sees the controller but MSFS does not, our Windows gamepad setup walkthrough covers detection, profiles and conflicting input layers in more depth.
Should I enable Steam Input for DualSense?
Use native controller input when it works; Steam Input or another XInput method is a fallback for missing devices, broken axes or unusable mappings.
| Input method | Choose it when | Main limitation |
|---|---|---|
| Native Windows input | MSFS lists the DualSense and responds when you scan its controls | Buttons may use numbers or generic labels, and the default profile may be incomplete |
| Steam Input | You have the Steam edition and native detection is missing or unreliable | MSFS usually sees an Xbox-style controller and displays Xbox button prompts |
| One XInput translation layer | The Microsoft Store or Xbox app edition cannot use native input properly | It can hide PlayStation-specific features and create duplicate devices if another layer is active |
For the Steam edition, enable Steam Input in the game’s per-title controller settings only if direct detection is unsuitable. It presents the DualSense as a virtual Xbox-compatible pad, which MSFS generally handles predictably.
Do not run Steam Input alongside another XInput translator. Also remove MSFS assignments from any unwanted physical controller entry if the virtual Xbox device is in use. Otherwise one stick movement can command both devices, producing doubled rudder, brakes, camera movement or controls that snap back.
Which DualSense controls should I map?
Map analogue flight axes first, followed by trim, rudder, throttle and brakes; camera and cockpit shortcuts come afterwards.
- Left stick: aileron and elevator axes. Use the full-axis commands rather than separate left, right, up or down commands.
- Triggers: left and right rudder when exposed as separate analogue inputs, or the combined rudder axis if the chosen input method provides one. Do not assign one trigger alone to a full-range combined axis.
- Right stick: cockpit and external camera movement.
- Shoulder buttons: throttle decrease and increase.
- D-pad: elevator trim, with spare directions available for flaps or view controls.
- Face buttons: wheel brakes, parking brake, landing gear and a frequently used camera or interaction command.
When Steam Input presents the DualSense as an Xbox pad, an Xbox-style gamepad layout provides a sensible starting point. If you put throttle on the right stick for finer control, you will need the mouse or another device for cockpit viewing.
Push the left stick forward and verify that the elevator commands nose-down; invert only an axis that moves in the wrong direction. Add just enough dead zone to stop neutral drift, then soften the response around the centre if the aircraft feels twitchy. Large dead zones make small corrections and trimming harder. Our controller sensitivity and dead-zone guidance explains how to tune the response without masking useful stick travel.
Why is my DualSense not working properly in MSFS?
Most DualSense faults come from Windows detection, competing input layers, digital commands assigned instead of axes, or a custom preset that was not applied.
| Symptom | Likely cause and fix |
|---|---|
| Controller is absent from Windows and MSFS | Use a known data-capable cable, another USB port or a different Bluetooth adapter. Confirm operation in joy.cpl first. |
| Controller works in Windows but is absent from MSFS | Connect it before launching the simulator and restart MSFS. Try native input first, then Steam Input or one XInput layer if required. |
| Every input happens twice or controls snap back | The physical DualSense and virtual Xbox controller both have active assignments. Keep one input route and clear bindings from the unwanted device. |
| A stick gives immediate full deflection | It is assigned to digital direction commands. Clear them and bind the corresponding full analogue axis. |
| The aircraft yaws or brakes by itself | Inspect trigger calibration and overlapping rudder or brake assignments. Native and XInput modes can expose the two triggers differently. |
| The camera drifts | Remove duplicate camera bindings and disable unwanted gyro, touchpad-to-mouse or desktop mappings. Add a small right-stick dead zone only if the stick does not centre cleanly. |
| Bindings disappear after leaving Controls | Edit a custom preset, apply the changes and make sure that preset is selected for the active controller. |
| Sound changes after connecting by USB | Windows may select the controller’s audio device. Restore the intended speakers or headset as the output device. |
| Bluetooth disconnects | Charge the DualSense, remove and pair it again, or switch to USB to rule out interference. |
If an old profile contains many duplicate or unexplained assignments, rebuilding one clean custom preset is usually quicker than correcting each conflict individually.
Does DualSense work with both MSFS 2020 and MSFS 2024?
Both PC versions accept DualSense input, although device names, control-screen layouts, default profiles and available assignments can differ. Microsoft Flight Simulator 2020 was never released on PlayStation; its DualSense support comes from using the controller with the Windows version.
Microsoft Flight Simulator 2024 also has a native PS5 and PS5 Pro edition, but its PlayStation controller integration does not make the PC edition behave identically. Our platform-specific MSFS 2024 controller notes explain the distinction between PC, Xbox and PlayStation support.
Do adaptive triggers, haptics and the touchpad work on PC?
The sticks, triggers and ordinary buttons are the dependable PC controls. Adaptive triggers, advanced haptics, gyro input, the speaker, PlayStation button symbols and touchpad behaviour depend on the simulator build, connection and input method.
Steam Input and other XInput translation methods make the DualSense look like an Xbox controller, so PlayStation-specific functions should not be expected through that route. The touchpad may become a single button or mouse input, while the PS button may open a launcher overlay; disable those mappings if they interfere with cockpit control.
Do I still need a joystick?
No. A DualSense is sufficient for casual flying, camera work and aircraft with forgiving handling. Its short stick travel makes precise trimming and small control corrections harder than with a flight stick or yoke, while rudder pedals provide better independent yaw and braking control. A mouse remains useful for cockpit switches even when every primary flight command is on the gamepad.