It causes a bunch of weird controller errors, such as when a controller disconnects (or if the deck goes to sleep), it can’t reconnect again.
Just let it use the default version (which I believe should be Proton Hotfix, or whatever Valve decides it should be since BG3 is an AAA headliner, they’ll want this to work)
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…
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.
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.
Changing the controller order with the game running worked for me. It was setting the deck built-in controller as “player 1” by default.
