How is the game on steamdeck otherwise? I'm debating if I should do what I never ever do and buy a game at full price...
this post was submitted on 09 Aug 2023
39 points (100.0% liked)
Steam Deck
591 readers
8 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.
founded 3 years ago
MODERATORS
I'm playing it on Steam Deck right now and though I'm still only a few hours in, I've only had some very minor issues. The game plays fine!
Issue 1: The graphics settings don't seem be persisted. I have to manually activate anti-aliasing every time, or deal with jaggies.
Issue 2: On Proton Experimental, my controller didn't work at the start. I was able to fix it by launching the on-screen KB (Steam button+X), hitting "Enter", and then switching back to controller mode. Sounds like it's time to switch to Proton Hotfix.
Otherwise, it's been great! I left the graphics settings (other than AA) at their defaults and I've seen no noticeable lag or stuttering during play.
I've been getting 25fps not having touched the settings. Anything I can do to improve that? I'm running SteamOS beta branch and have not adjusted the VRAM levels
I fiddled with it a fair bit, and ultimately decided to just stick with the "Medium" default. With that, it's pretty stable, with a few dips, but given the turn-based combat etc, it doesn't really bother me.
(But that said, I'm an old-school PC gamer. I played DooM on an 8 MHz 386 at sub-10 FPS. I had to "lead" my shots to play. So my personal standards for game performance may be a little low.)
That's normal, I have been using fsr from steam deck's menu and got it running at 30 fps for the most part, it can still go below 30 but it is very playable.
It work well but i stopped because the UI is small.
I played the EA on steam deck, and it was awesome. However, i'm waiting for improvement on the UI side so i can fully enjoy the game.
As for mapping control, i use the DOS2 and i tweaked it to suit my taste.
Tangentially related: I've had this exact problem with quite a few games. Most recently, Subnautica: Below Zero. I often pause a game, go take care of a chore or something, then come back to having no controller input. Only recourse seems to be to exit the game and start it back up again. Using an 8bitdo Ultimate (non bluetooth) controller at the moment, Steam Deck connected to the official dock.
Anyone else have this issue? Any remedies you're aware of?
Maybe try turning steam input on or off? That's the first toggle I'd reach for with controller issues (like when Elden Ring came out).
I'll keep that in mind, thanks.
I have this problem with Skyrim and Fallout 4 if I use an external controller (either USB or Bluetooth) when docked. If the controller gets disconnected or I touch any of the Deck's own controls when playing, the game will just completely stop listening to the external controller and will only work if I use the Deck's controls. Restarting the game does fix it but it's pretty annoying, and eg. toggling steam input off and on doesn't do anything and the controller order is correct.
Changing the controller order with the game running worked for me. It was setting the deck built-in controller as "player 1" by default.