Submitted 4 weeks ago by bjoern_tantau@swg-empire.de to steamdeck@sopuli.xyz
Does anyone else see this? Every time I wake up my Deck to continue playing no gamepad input is accepted by the game only keyboard and mouse.
Might be because I’m not running SteamOS but OpenSUSE and start the game from KDE Plasma. But maybe this is an issue on regular Steam Decks as well I can report.
There’s apparently an issue where this is happening in some games running through proton 10 (or proton experimental because that uses proton 10). Recent steamOS updates apparently helped fix it for people, but that probably hasn’t helped you since you’re not on SteamOS.
I would recommending forcing your steam play to use proton9 or lower until it’s fixed.
That sounds like it may very well be the issue. I think I’m running Proton Hotfix at the moment.
I wish there was a way to see what Valve did to fix a problem with SteamOS. I’m also interested in their solution for low memory slowdowns.
I get the same running rdr2 through steam OS and whenever i wake up from sleep and toggle by bluetooth, the game no longer recognises the controller.
See my edit. It’s a bug in Proton 10. Don’t use Experimental or Hotfix at the moment.
I also run stuff via steamos so I cannot tell much from your setup. However, maybe there is a trick that could potentially work. On the steamos, when you are on to desktopz it is possible to switch between desktop mode and gamepad mode controllers (not sure on exact naming here). You can do this by pressing for a second or two the upper right button from the front (I believe the legend is 3 stripes or similar). On the steamos it changes modes and can help you unblock controls on weird situations.
Maybe this can help?
It helped when I ran a pirated copy through Heroic. I have since bought the game and use Steam Input, so I only get the controls recommended by Steam.
I will try replicating the desktop setup. Maybe switching out of the game and back helps.
I run it on SteamOS, bought via steam. No problem on my side so far.
Flaim@discuss.tchncs.de 4 weeks ago
i noticed this happening too with ffvii rebirth. turned out to be an issue with proton, because the issue disappeared after i switched to the latest proton-GE
bjoern_tantau@swg-empire.de 4 weeks ago
Yes, that was it! It’s a bug in Proton 10.