protonscr

DualShock 4 doesn't work in-game

steamclosed
ValveSoftware/steam-for-linux#12338 · opened 2025-09-21 by jmendes418 · updated 2025-09-21 · 1 comments · github
Jjmendes418 2025-09-21 github

Your system information

  • Steam client version (build number or date): 1757650573
  • Distribution (e.g. Ubuntu): Arch Linux
  • Opted into Steam client beta?: No
  • Have you checked for system updates?: Yes
  • Steam Logs:

steam-logs.tar.gz

  • GPU: Nvidia GeForce RTX 4060 Mobile

Please describe your issue in as much detail as possible:

I’m having issues with my PS4 controller (DualShock 4) when playing games on Steam. The controller is detected normally by Steam and works fine in Big Picture mode as well as in the controller test/configuration settings. Steam Input recognizes all button presses correctly, and compatibility with PlayStation controllers is enabled in the settings.

However, the controller stops working only inside the games. Even though some games specifically state they are compatible with the DualShock 4, no input is recognized once the game launches.

I have already tried the following:

  • Tested with two different DualShock 4 controllers (one brand new), same issue.
  • Tried both wired (USB) and Bluetooth connections.
  • Verified Steam Input settings.
  • Reinstalled Arch Linux with a clean setup, issue persists.
  • Confirmed the controllers are properly detected by the system and by Steam.

This issue only started happening recently, right after updating my Arch Linux packages. Before that, everything was working normally.

I would expect the controller to work inside games just as it does in Big Picture mode and in the controller test. Instead, games completely ignore the input.


Steps for reproducing this issue:

  1. Connect a DualShock 4 controller (USB or Bluetooth).
  2. Launch Steam and verify the controller works in Big Picture mode and controller test.
  3. Launch any game → controller no longer works inside the game.
Kkisak-valve maintainer 2025-09-21 github

Hello @jmendes418, this issue is already being tracked at #12310. Closing as a duplicate.

Nothing extracted yet.