Steam Deck

17142 readers

491 users here now

A place to discuss and support all things Steam Deck.

Replacement for r/steamdeck_linux.

As Lemmy doesn't have flairs yet, you can use these prefixes to indicate what type of post you have made, eg:
[Flair] My post title

The following is a list of suggested flairs:
[Discussion] - General discussion.
[Help] - A request for help or support.
[News] - News about the deck.
[PSA] - Sharing important information.
[Game] - News / info about a game on the deck.
[Update] - An update to a previous post.
[Meta] - Discussion about this community.

Some more Steam Deck specific flairs:
[Boot Screen] - Custom boot screens/videos.
[Selling] - If you are selling your deck.

These are not enforced, but they are encouraged.

Rules:

Follow the rules of Sopuli
Posts must be related to the Steam Deck in an obvious way.
No piracy, there are other communities for that.
Discussion of emulators are allowed, but no discussion on how to illegally acquire ROMs.
This is a place of civil discussion, no trolling.
Have fun.

Link to our Matrix Space

founded 3 years ago

MODERATORS

[email protected]

[Solved] Gamepad input gone in Clair Obscur: Expedition 33 after standby (swg-empire.de)

submitted 4 days ago* (last edited 4 days ago) by [email protected] to c/[email protected]

9 comments fedilink hide all child comments

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.

Edit: It's a bug in Proton 10. Thanks guys!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 4 days ago (1 children)

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.

[–] [email protected] 2 points 4 days ago

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.