Fix Steam not recognising a controller or DualSense PS5 pad by checking Windows, USB, Bluetooth, Steam Input and each game's override.
For Steam on a Windows PC, a controller usually goes unrecognised because Windows cannot see it, the USB cable supplies power but not data, Bluetooth pairing has failed, Steam Input is disabled, or another input tool has claimed the device. Check Windows first, then Steam's controller test, then the game's per-title setting.
This is a general Steam controller issue rather than a fault tied to one simulator. The key is to identify where detection stops: Windows, Steam or the game itself.
Does Windows detect the controller?
Steam cannot detect a controller that is missing or unresponsive at Windows level.
- Open the Windows controller test. Press
Win + R, enterjoy.cpland press Enter. Select the controller, open its properties and check whether buttons and sticks respond. - Test a different USB data cable. A PS5 DualSense can illuminate and charge through a power-only cable while sending no controller data. Connect it directly to another PC port rather than through a hub.
- Pair Bluetooth again. Remove the old controller entry from Windows Bluetooth settings. On a DualSense, hold the Create and PS buttons until the light flashes, then use Windows Bluetooth device discovery and select
Wireless Controller. - Disconnect competing devices. Temporarily unplug other gamepads, wheels, throttles and virtual controllers. This makes it clear which device Windows and Steam are testing.
If the controller does not appear in joy.cpl, changing Steam Input will not help. Concentrate on the cable, USB port, Bluetooth pairing, battery, Windows device recognition or the controller itself.
How do I make Steam recognise the controller?
If Windows detects the controller but Steam does not, restart Steam with a clean input path and check its Controller settings.
- Close the game completely. Many older simulators scan for controllers only during startup.
- Exit Steam rather than closing its window. Use Steam's Exit command, reconnect the controller and reopen Steam.
- Open Steam Settings and select Controller. The connected pad should appear there as an Xbox, PlayStation, Nintendo or generic controller. Open Steam's device-input test and confirm that buttons and axes respond.
- Enable the appropriate Steam Input support. For a DualSense or DualShock, enable PlayStation controller support if the game needs Steam Input. Steam has changed the exact labels over time, but the relevant options remain on the Controller page.
- Stop other controller-mapping software. A mapper may hide the physical DualSense and expose a virtual Xbox controller instead. Use one translation layer, not a third-party virtual pad and Steam Input together.
- Update and restart Steam. If detection failed immediately after joining a Steam client beta, return to the stable client and test again before changing game profiles.
A DualSense listed as Wireless Controller in Windows but as a PlayStation controller in Steam is normal. If it works over USB but disappears over Bluetooth, the problem is the wireless pairing or Windows Bluetooth path rather than Steam Input.
What Steam Input setting should I use for each game?
Use Steam Input when a game lacks native support for your controller; disable it when the game handles that controller properly by itself.
| Situation | Per-game setting | Expected result |
|---|---|---|
| You are unsure or the controller previously worked | Use default settings | Steam applies its global controller policy |
| The game lacks PlayStation or generic-controller support | Enable Steam Input | Steam commonly presents the pad through an Xbox-style input layer |
| The game has native DualSense support | Disable Steam Input first | The game receives the physical controller directly |
| Inputs are doubled or buttons activate twice | Use only one input layer | Disable either Steam Input or the separate virtual-controller tool |
Change this under the game's Steam Library properties on the Controller page, then restart the game. Xbox button prompts while using a PS5 controller usually mean Steam Input is translating it into the widely supported XInput format; they do not mean Steam has detected the wrong hardware.
Native DualSense features such as specialised haptics or adaptive triggers depend on the individual game. Where supported, they may require Steam Input to be disabled and the controller connected by USB.
Why does Steam see the controller but the game does not?
If Steam's input test responds, controller detection is fixed; the remaining fault is the game's launch method, controller profile or input system.
- Connect the controller before starting the game, particularly with older flight and train simulators.
- Launch the game from the Steam Library so its per-game Steam Input configuration is applied.
- Check that the game has controllers enabled and that the correct device or control profile is selected.
- Disconnect unused controllers if the game always assigns the first detected device as controller one.
- Avoid running the game as administrator while Steam runs normally, because the privilege mismatch can prevent input translation. Run both at the same privilege level.
Microsoft Flight Simulator adds its own control profiles and binding filters after Steam detects the pad. Our MSFS controller profile and duplicate-input setup covers that second layer without repeating the Steam checks.
Train Simulator Classic also has game-specific limitations, especially with PlayStation and generic pads; use these Train Simulator Classic Steam Input checks once the controller responds in Steam. For an Xbox pad that passes Steam's test but fails in a flight simulator, follow our PC flight-simulator Xbox controller troubleshooting.
The stopping point identifies the fault: no response in joy.cpl means Windows or hardware; response in Windows but not Steam means a Steam or virtual-controller conflict; response in Steam but not the game means a per-game profile, launch or compatibility problem.