UnsupportedShow Details
Unknown
This configuration works flawlessly so far. The gamescope options aren't entirely necessary.
game-performance gamescope -W 3840 -H 2160 -r 165 -F fsr --adaptive-sync --hdr-enabled -f --force-grab-cursor --mangoapp -- %command%
My previous report using vanilla Arch was a good experience until I encountered certain sections of the game where frametime spikes became unbearable. At some points, the game would become unplayable. I tried various kernels including zen, bazzite, and cachyos. I tried various configurations including and excluding gamescope, gamemode, VRR, FSR, HDR, but nothing seemed to work. I tried to replicate this in Arch with this guide: https://wiki.cachyos.org/configuration/gaming/ but it just became a Frankenstein distribution which I didn't feel was sustainable and it didn't help the stuttering. Something about the CachyOS distro taken in whole turned out to be the secret sauce to a better experience.
PROTON_ENABLE_WAYLAND=1 PROTON_ENABLE_HDR=1 %command%
Steam Input is not compatible with Wine Wayland.
The game ocassionally hangs indefinitely, some of those lead to a crash. There seems to be no discernible trigger.
The new native Wayland + HDR mode of Wine 10 is the only option that currently works for me for HDR. However, that does mean that Steam Input, the overlay and other functions relying on that (e.g. screenshots) don't work.
If HDR is not needed/wanted, regular Proton versions and XWayland work, and don't have those incompatibilities.
Aside from the occasional frametime spike (usually during dialog), game runs better than on Windows.
gamemoderun gamescope -W 3840 -H 2160 -r 165 --hdr-enabled --adaptive-sync -f --force-grab-cursor --mangoapp -- %command%
During dialog after frametime spikes. Resolved when next character begins speaking.
Camera rotation would stop. Fixed with --force-grab-cursor
Occasional frametime spikes that freeze the game for a fraction of a second.
Only issue is the occasional frametime spike. Have not tried different kernels but I imagine they wouldn't make a difference.
When running with gamescope without the --force-grab-cursor flag, the cursor seemed to be running into the side of the monitor in the background, as I couldn't spin my view around 360 degrees without hitting a cursor wall.
Running with HDR on Nvidia works for a couple minutes but then crashes. No issues thus far on AMD.
Limit FPS to 30 via Steam Deck’s “…” button menu.
On the OLED Deck’s integrated screen, the default “Very Low” quality setting combined with manually enabled XeSS from Forbidden West’s Display Settings and Steam’s 30 FPS override looks pretty solid at mostly stable 30 FPS. I did not experience any audio crackling or crashes other reports mention (I had a few crashes on my Windows PC, so such problems may be game bugs and not SteamOS/Proton).
I kept frame generation off and kept the XeSS quality setting at its default. In my short tests FSR resulted in worse performance than XeSS, roughly by 10%.
In docked operation with a bigger screen, the flaws of the very low quality preset are very apparent but in handheld play these are negigible.
gamemoderun mangohud %command%
- Sometimes ambient music just cut out, while other sounds continued
- Sometimes Alloy became mute
- Audio cuts out in some cutscenes
- Flickering lighting in tavern of Chainscrape
- Black lines on water while swimming
- In some cutscenes, some textures loaded only in a tiny resolution
- After completing story mission in Heaven's Rest , all palm trees had rainbow colored squares on their surface. Restarting the game fixed it.
- Tabbing out froze the game. Somehow it got fixed while i was playing.
- Walking: Traversal stutter into the 40ms (25FPS) range. Especially on high settings, the spikes were extremely noticeable.
- Standing: Sawtooth-Microstuttering (7ms->11ms->7ms) depending on location. Especially in cutscenes. Sometimes over minutes.
- Map loads sometimes for >10 seconds. In rare cases it never loads.
- Game stutters when M.2 SSD slightly loaded (<20MB/s)
- Tabbing out froze the game. Somehow it got fixed while i was playing.
- All NPCs frozen (some in T-pose) in Fleet's End
I payed the game with a ulimit of 1024. Only after i came here, i saw that i should have increased that to get a better experience.
Systemd-users, set DefaultLimitNOFILE=49152:524288 in /etc/systemd/system.conf
If you have played a few games on Linux (and you have already played Zero Dawn), i can recommend this game, but a newcomer would probably blame Linux for the technical issues.
In the desert region, the sound is completely broken. (sometimes)
Rarely crashed.
Steam OS 3.7.1 Fixes most crashing problems as far as I can tell. Audio almost immediately had problems either cutting out, crackling, or just cutting dialogue.
Sometime the map fails to load and you have to restart the game to get it back
getting anywhere from 15-40 fps depending on the area
ulimit -n 1048576; %command%
Without the launch command the game occasionally hangs or voices disappears
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening men
FSR, Lowered Settings, Set the GPU to 1600
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening menus.
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening menus.
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening menus.
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening menus.
Game eventually loses all audio, then starts freezing for long periods requiring a restart, tends to happen in cutscenes or when opening menus.
Runs good out of the box. Can`t compare with windows, I have no longer windows install
env DRI_PRIME=pci-0000_03_00_0 ENABLE_VKBASALT=1 RADV_PERFTEST=gpl,nggc,sam LD_PRELOAD=/usr/lib/libgamemode.so gamemoderun mangohud %command%
See the clocking comment!
Definately check what type of clock call you use with this game! Character animations are dependant on system clock calls. see https://wiki.archlinux.org/title/Gaming#Improve_clock_gettime_throughput
Other than the frustration of the developers not using an internal game clock, it ran smoothly out of the box after adjusting my system to use TSC
ENABLE_VKBASALT=1 gamemoderun gamescope -S integer -W 3440 -H 1440 -r 144 -f --adaptive-sync --steam --force-grab-cursor -- %command%
I run gamescope, gamemoderun and VkBasalt but that's personal preference. Those aren't required for the game to run.
PS: The report indicates I don't own the game, that's because I play using a family shared library.
Works occasionally. Sometimes makes entire save files unplayable, thank god for autosave. Avoid using fast travel. Can be fixed either by restarting or restarting and then loading an older save file.
some types of foliage flickering, including tall grass used for stealth. It looks so stupid
audio issues
sometimes the audio will also just disappear during regular gameplay
gamescope -W 3440 -H 1440 -r 175 -f --hdr-enabled --force-grab-cursor -- %command%
Works without any launch options. I used gamescope to get HDR working which cause a crash after a few minutes if Nvidia Reflex Low Latency is enabled. After disabling it gamescope and HDR work fine.
game it is running but i have no controlls,at all...ive tried with diff settings,even with one from comunity butill nothing.pls any ideea?
experimental proton
just hope at the moment
Music and voice randomly cut out; no discernable pattern nor fix
30Hz Refresh Rate / 1400Mhz GPU
If the audio for the dialog stops playing, then the game will usually crash shortly thereafter. Happened some early in the game, but frequently during the Burnish Shores DLC.
Update to my previous entry with a lot more playtime on the Deck. Playable for certain, but ultimately I think the game is pushing the limits of the SD hardware.
Performance Tips on Steam Deck
Game consistently gets better frame pacing, and often 2-3 FPS higher when manually setting the GPU clock to 1400MHz.
- Base Game: Set TDP to 13W.
- Burning Shores DLC: The Deck needs the full 15W TDP.
Observations
- The base game and DLC have fundamentally different hardware requirements and Steam Deck performance.
- Both are mostly playable at 25-30 FPS, with dips into the high teens to low twenties during:
- Large cinematic cutscenes.
- Fights against large machines.
Settings can help mitigate dips, but expect sub-30 FPS when it really matters most (e.g., Apex Thunderjaw fights or the boss fight in Burning Shores).
This can make the gameplay frustrating when the Deck struggles to maintain 22-24 FPS.
Opinions on FSR
- Drawbacks:
- Item drop icons become blurry beyond recognition.
- Machines in the distance are blurry.
- The glider looks messy.
- Aloy's hair appears weird.
- FSR was avoided for most of the game but became necessary towards the end of the DLC to maintain low 20s FPS.
Issues with Frame Generation
- Frame generation provides higher FPS but introduces:
- Visual artifacts around the HUD area that looks like screen tearing.
- Input lag and acceleration issues, making aiming difficult.
- FPS still drops into the low 30s during big fights (~15-20fps native), rendering it ineffective.
Stability Issues
- If dialog audio stops working, or the map only shows a black screen, the game is likely to crash within the next few minutes. Tested with Proton 8, 9, and GE-9.
Recommended Settings
Base Game
- Graphics: Low Preset
- Display Resolution: 1280x800
- Dynamic Resolution Scaling: Off
- Anti-Aliasing: SMAA
- Upscale Method: Off
- Frame Generation: Off
Burning Shores DLC
- Graphics: Very Low Preset
- Display Resolution: 1280x800
- Dynamic Resolution Scaling: Off
- Anti-Aliasing: FSR3
- Upscale Method: FSR3
- Upscale Quality: Ultra Performance
- Frame Generation: Off
Currently may require some tweaking depending on your distrobution, but I think it's very enjoyable once workarounds are employed.
ulimit -n 1048576; %command%
Without Launch Options I had set, audio such as speech would cut out, and eventually game would lock up requiring you to force-quit it. Seems to be hitting open file descriptors limit. Setting Launch Options with ulimit -n 1048576; %command% fixed this for me. Max value available may be different, check with ulimit -Hn in console.
The game occaisionally has fraction of a second freezes that usually doesn't affect gameplay for me. If this happens during cut-scenes, audio may be out-of-sync for that phrase, but it fixes itself shortly. Otherwise, game performs pretty well on my setup on Very High graphics settings on a 5120x1440 screen (32/9).
Would likely work with Proton 9 or Proton Experimental, but I was looking into fixing the audio cutout & crash issues. Increasing the soft open file descriptor limit using Launch Options is likely the fix needed. Some distros may have this set to a sufficient value, but Bazzite only allows 1024 by default.
Runs pretty much exactly like natively on Windows. No Graphical Issues, no Crashes/Lags, Just worked.
gamescope --steam -W 1920 -H 1080 -w 2560 -h 1440 -r 144 -b -- %command%
My mouse cursor will not be confined to the game window, even when just moving the camera, making it constantly move onto another monitor. Can be fixed by either A: Playing with a controller, or B: using the '--force-grab-cursor' gamescope argument.
Outside of that, runs like a charm. No issues whatsoever.
With the frequent audio issues and crashing I think it would be a very unfun experience.
Audio randomly stops working, only coming back if I restart the game.
When I alt-tab in loading screens or on launch there is no audio after.
After a while of normal play the audio starts to cut out, then soon after it crashes. As soon as I stop hearing audio I just accept the fact that the game is about to crash. When it crashes it freezes for a moment on screen and I just have to wait for it to close by itself, because system monitor won't even recognize it at that point.
It's not the best experience. SD Setting are max 30FPS, but my SD LCD is frequently in the mid-20's.
Definitely playable, but expect to play in the 26-30 fps range.
I tinkered with the settings a lot, testing various combinations of dynamic scaling, FSR and framegen. Too much input lag and FSR blurriness for my preferences, so FSR & framegen off.
需要一些調整
聲音的部分有機會破音，需要調整piperwire min-quantum = 512 linux的clock source需要調整為tsc，否則整體遊戲會慢動作 現行的著色器已可順利運行，遊戲前建議先跑完著色器更新，舊版會很lag
Pop in/flickering of foliage. Switching from proton version 9 to 8 fixed the flickering.
MANGOHUD=1 gamemoderun %command%
The game seems to be cpu-bound on my hardware compared to running it natively on windows; framegen 3.1 made performance and feel significantly worse on linux compared to windows. Without framegen the game runs fair above 30fps up to 80fps, and offers an overall enjoyable experience
PULSE_LATENCY_MSEC=60 gamemoderun %command%
Voices and music stops randomly after some time
After the sound issue occurs, most times you got a crash soon after
Fully playable - sometimes FPS would drop but I think it's because of my CPU (or the game is not well optimized, who knows). Sometimes voices and music would stop playing and soon after the game starts to ge berserk: map won't display anymore (black screen), the inventory won't work correctly, loading a game would hang. Eventually you either get a crash or a stuck process. The only fix is restarting the game. I couldn't determine a pattern for the bug though (yet). My recommendation is - since the game saves often - as soon as you catch the bug, don't continue playing and just restart the game.
Aside the sound issue it works alrgiht
Audio sometimes dissapears and never returns until game restart
In the DLC map the game crashed.
Андервольт: CPU -50 GPU -50
Видеоядро ставим на лок 1600 MHz
Иногда при смене режима на "оконный", окно открывалось не центрированно по экрану, а уползало "за края". В таком случае помогало включить/выключить "Вертикальную синхронизацию".
Сначала только тач-скрин. Нашёл телеграм канал, в котором парень создал текстовый файл в корневой папке игры и всё заработало. Ищите его на видеохостингах или телеграмме.
На больших открытых локациях идут просадки фпс вплоть до 15 FPS. С этим ничего не поможет, т.к. просто не хватает мощности процессора
Устройство - Steam Deck Oled. Версия игры - 1.5.8. Версия SteamOS - 3.15.19 Установлены:
- Decky Loader - PowerTools (Governor - "Performance")
- CryoUtilities (рекомендуемые настройки, файл подкачки - 16Гб)
- ProtonUp-Qt
- Видеопамять увеличена в BIOS до 4Гб.
Ставим лок на 30 FPS.
Выставляем настройки: Режим экрана - "Полноэкранный"; Разрешение - "1280х800"; Соотношение сторон - "Авто"; Вертикальная синхронизация - "Вкл"; Способ масштабирования - "AMD FSR 3"; Качество масштабирования - "Качество/баланс" (в зависимости от нагруженности сцены); Качество текстур - "Средн."; Фильтрация текстур - "Анизотропная 8х/16х"; Качество теней - "Очень низк."; Тени в экранном пространстве - "Выкл"; Затенение фонового цвета - "SSAO"; Отражения в экранном пространстве - "Откл"; Детализация - "Средн."; Лица в видеороликах - "Производительность"; Качество волос - "Средн."; Качество людей - "Средн./Низк."; Качество рельефа - "Низк."; Качество воды - "Низк."; Качество облаков - "Низк."; Качество прозрачности - "По умолчанию"; Карты паралакса - "Выкл."; Поле зрения - "-15%"; Глубина резкости - "Откл."; Эффект скорости - "0"; Резкость - по вкусу, у меня "4"; Виньетирование - "Вкл." (вкусовщина, но я рекомендую включить, т.к. картинка, на мой взгляд, становится чуть более контрастной/глубокой).
Комментарий:
- Долго сравнивал включенный FSR через "режим окна" и "Полноэкранный" на 1280х800. Разницы в производительности не было, только картинка отвратительная;
- Температуры у меня в маленьких локациях - 50-55гр, в больших до 70-71гр (и на CPU, и на GPU);
- Автономность на данных настройках около 2 часов;
- Играть комфортно, к периодическим заиканиям - привыкается. В случае сильных просадок и Вашего успокоения понижайте указанные выше настройки. Но смысла не будет или будет незначительный;
- В некоторых кат-сценах будут серьёзные просадки. Рекомендую перетерпеть/временно понизить настройки (это не исправит ситуацию, но может облегчить) Хорошей игры и удачи!
with the latest 1.5 patch you can easily reach 60fps during normal gameplay (all low settings, FSR3 frame gen enabled). you can even reach 90fps incertain cases. its honestly impressive what they were able to squeeze out of the steamdeck.
MANGOHUD=1 gamemoderun %command%
RADV_PERFTEST=gpl,nggc,sam
