A controller works in Windows but not in a Steam game: diagnose it
Test detection, per-game mappings and duplicate input layers before buying another controller or reinstalling drivers.
In brief
Separate a connection problem from a game mapping problem. If Windows cannot see the controller, changing Steam’s button layout will not fix the connection. If Steam sees it but one game does not, start with that title’s controller settings.
Testing one layer at a time gives you a useful failure point instead of a pile of conflicting fixes.
If the device is not detected
Try a different USB port and data cable, keeping only one controller connected. For Bluetooth, compare a wired session before resetting pairing. If neither Windows nor Steam detects the device, use the manufacturer’s support instructions rather than downloading a random driver pack.
If Steam detects it but the game does not
Check whether the game supports a controller and whether it needs input enabled in its own menu. Compare its default Steam Input override with the appropriate enabled or disabled setting. Relaunch after a change. A working result in another game is evidence that the physical connection is probably not the immediate fault.
If one press happens twice
Close third-party remapping software for a clean test and remove duplicate virtual-controller paths. Do not remap every button to hide double input. Once the correct path works, save a per-game layout and reintroduce other tools only if genuinely needed.
Before you act
Some games do not support controllers natively, and advanced features vary by device. A controller being detected does not mean every game understands its inputs.
What to do next
- Use a known data-capable USB cable for the first test and confirm device detection.
- Open Steam Settings → Controller and test the available inputs.
- Close other mapping tools, check the game’s Controller override and retry from Steam.
