UnsupportedShow Details
Unknown
Subpar performance and bad M&K controls. Playable, but should not run this bad for what the game looks like.
I bound "execute" and "pocketables" to side mouse buttons and both occasionally needed rebinding on game restart.
A lot of areas chug for some reason, falling into the 40's with 100% GPU utilisation. The only setting which had a meaningful difference was shadow quality. On low, I could get a somewhat stable 60, which is a bit of a joke given the game isn't exactly a showstopper. Doesn't seem to be Linux-specific going by Steam discussions.
A few crashes.
Stuck at loading screen with infinite loader? Needs to login to Epic Store to confirm linked account.
Proton Experimental made tremendous leaps recently, so the game can run at a solid 30 at it's highest benchmark. I recommend TAA, high settings, medium shadows and SSAO. Though I warn you that the game will eat up your battery, even on OLED.
降低瓦數以及鎖40fps
圖型最高只能調中
fps不穩 例如有瀑布或海水的場景會掉fps，掉到20多fps
以遊戲內最低效能執行，只能穩定30fps 建議下載安裝cryoutilities設定後「是否造成機體異常自行負責」 一樣最低效能但fps能夠達到51-54fps 之後鎖40fps,剩下微調圖形或降瓦數,以達到理想的續航時間 有做以上設定應該可以有比較舒適的遊玩體驗
gamemoderun %command%
allways around 20 to 25 FPS
works out of the Box with proton. No problem. no tinkering needed. But still Gamemode is allways a good idea.
Cap the framerate to 40 FPS and lower all the setting to LOW/MEDIUM (shadows on LOW make the game look really bad, but if you want all the performance - it's the main culprit).
Additionally I've set the GPU clock to 1500/1600 MHz (mostly to stabilize the frametimes).
For the most part (ie. while exploring the map) the game sustains stable framrate, but if you trigger a horde or get into a fight with a couple of zombies, the game will chug rather significantly (doesn't dip below 30 FPS, but the hitching is noticeable).
Additionally, TLS:A is the first game to trigger the "Steam Deck is overheating" prompt. Quite concerning given the graphical fidelity isn't really AAA-level.
Framerate's stable at 30 with medium settings, but anything above is difficult to achieve.
The game does not pause automatically when "losing focus", and occasionally refuses any input (except for menus) after returning from the Deck's menu.
I'm not sure why Valve gave this an "unsupported" rating. It works fine, once you get past the weirdly long loading screen.
The performance is a little disappointing. I wasn't able to get to a stable 60 fps even with lowest settings and less-than-native resolution. If you're fine with 30 fps, it runs very stable even on "Medium" + SMAA + SSAO (volumetric lighting disabled), but anything above that turns into a mess quickly. I couldn't even get 45 fps to work reliably on low settings. I also noticed the Deck's own framerate limiter causing a lot of juddering as opposed to the built-in one. YMMV.
Controls on the Deck are fine out of the box, as it's controller-optimized on PC as well.
In general, I think it's a pretty good fit for the Deck, with smaller levels that you can get through in 5-10 minutes (probably longer in later levels), and if you can live with 30 fps (and about two and a quarter hours of battery life at that framerate), I recommend you give it a try.
Seems to work fine, unsure why Valve flagged it as unsupported. It's actually quite fun on the Deck.
Medium settings including SSAO + SMAA Low run pretty steady at 30 fps, 60 is unstable even at lowest settings and resolution.
Black screen after the intro
The game is impossible to play, since right after the intro, when it loads the game, it turns both my monitors black, forcing me to restart.
Once you get your controller figured out, works great!
I'm on steam beta, which recently broke controller support through steaminput, but on most other games, disabling this restores the functionality. Tried lots of stuff to get the controller working in this game, but it finally took switching from GE's 6.21 to no forced compatability before it would accept controller input. I have no idea why this is, and might just be something in my setup that's weird, but there it is.
First boot up takes a very long time. Confusingly so.
Unknown(an hour with Proton)Tested with the current Demo-version. Maybe this changes in the future.
Unknown(an hour with Proton)
