VerifiedShow Details
Unknown
Make sure you select Proton before downloading the game, if you select proton after it's done downloading it will re-download again. This will save you time.
game-performance %command%
Proton runs way better than Native, probably problems after latest update. While Native has:
- has mouse input lag problems
- graphical problems, models with black textures in the landscape
- the beast intro movie plays everytime
- crashes on the start of zere's mission
I've felt slowdowns on proton while PCSS was activated, probably bc Nvidia Gameworks is trash.
native version is borked, actually. You need to enter some launch options to start playing
__GL_IGNORE_GLSL_EXT_REQS=1 __GL_THREADED_OPTIMIZATIONS=1 %command%
also idk anything about crossplay with windows users, and how old is linux version, and what's about DLC support on native version it's better to play via Proton than the native version if you want to play as you played on windows, or with your friends if you don't need all this - you can use the native version. Just don't forget about the launch options I mentioned earlier
2hrs + battery life on max settings, it's enough for me but if you plan on playing for longer you might have to lower the settings.
Works flawlessly with highest quality graphics settings on the steamdeck, from start to finish and including The Following DLC. I'd recommand it as a first game to play on the deck when you get it.
gamemoderun %command%
Launching it without steam play caused it to crash the game after a few minutes. Changing to PE and adding the launch options has made it work well
DRI_PRIME=1 %command%
At the moment native is borked after Retouched update but with launch command and GE-10.4 game runs flawlesly. 9/10 at the moment but it'll be 10 after they fix native. Launch option is necessary for laptops to use discrated gpu.
Native version of the game crashes at a point in tutorial. Every time I walk into the shack game crashes. Windows version with proton works wonderfully, played for hours and not a single bug, glitch or crash.
gamemoderun %command%
Works better than the native version.
For gaming laptops: Use DRI_PRIME=1 %command% as launch parameter because the game defaults to the igpu natively and on proton.
Very slow sensitivity in menus - not sure if this can be fixed. Also if you do very slow, precise mouse movements, there is no diagonal control, only up down left or right. e.g.: you can move the mouse in the top right direction, but ingame it only moves your camera up. Precise aiming is impossible.
Significant stuttering
ALT + F4 crashes the game and I must restart Cinnamon with CTRL + ALT + ESC to get my cursor back so I can close the game.
Use Proton. Native is borked!
Runs fine with proton. Native is stuck with black screen (audio plays though, I could even hear the menu-ing sounds).
I tested this game briefly, and native worked perfectly for me. The first start up was a little slow.
slight visual jankiness
I had to use Proton Experimental or GE-Proton to launch the game correctly
Worked out of the box
For me the game ran just fine with or with out Proton in use. I did find that at least in my case, I had to enable Proton to participate in multiplayer games, however. I've played with friends on several occasions for a grand total thus far of 9.5 hours. No issues to report other than without Proton enabled, I would get kicked from multiplayer sessions. I've had sessions where I was the host and/or I joined others that were hosting in the total time we've played thus far.
Works flawlessly
No need to use proton, native version works without problems
Jeu terminé sans aucun problème / Game finished with no problem
Whatever you do, just make sure it's running through proton.
Had a jumpscare first time I ran it natively. My entire screen was wigging out and I thought my system was borked. Turned out it's just because the native port doesn't work properly. Use proton and it works just like on windows.
Proton is very much equal to Windows, and a very pleasant experience with multiplayer working as intended! Native doesn't boot at all.
gamemoderun WINEDLLOVERRIDES="d3dcompiler_47=n;dxgi=n,b" DXVK_STATE_CACHE=1 %command% -nologos
Using MangoHud completely broke my framerates, they were high (around 90-110 fps) but moving the mouse presented horrible choppyness, the fix was removing MangoHud entirely or setting at least MANGOHUD_CONFIG="fps_limit=your_fps,vsync=2"
MangoHud and especially Gamescope will give odd behaviours, Turn off NVIDIA PCSS and Depth of Field for greater performance. Use V-sync if you have Freesync or G-sync, it has no big input lag, a little bit sure but looks and feels great though!
No tinkering ahead
game running flawlessly
Big performance hit when Nvidia PCSS is enabled. Once disabled, it performs very well.
Needed to force the use of Proton 9. Black screen with audio otherwise.
Proton/DXVK version of the game is very solid. Don't bother with the outdated native/OpenGL port.
mangohud MANGOHUD_CONFIG="fps_limit=117,vsync=2,position=top-right,cpu_temp,cpu_power,gpu_temp,gpu_power,cpu_mhz,core_load" WINEDLLOVERRIDES="d3dcompiler_47=n;dxgi=n,b" %command% -nologos
Set anistropic filtering x16 in dxvk.conf, installed Reshade via script for injected anti-aliasing
Disable "NVIDIA PCSS" and "NVIDIA Depth of Field" in graphics options to greatly reduce GPU resource usage with minimal visual quality loss. Possibly because I'm using an AMD GPU, not sure if this applies to Nvidia users.
Works OOTB with some minor quirks. As this is an older and less-demanding title, changing my KDE Power Profile to "Power Save" allows my Ryzen 7700X to remain under 60C w/ boost disabled while maintaining my 4K @ 117 FPS limit. I'm also using a DLAA/SMAA combo via Reshade as a replacement for the in-game anti-aliasing method, and forced Anisotropic Filtering via dxvk.conf (more info linked above).
gamemoderun mangohud --dlsym %command%
Out-of-the-box, Dying Light would start, but i had graphical glitches - either no screen or glitching textures, without the ability to even see the main menu, while audio was fine - with constant prompts that the game is not responding. With GE-Proton9-23, it worked like a wonder.
At first i played with the native version, without proton and with "__GL_IGNORE_GLSL_EXT_REQS=1 %command%" at custom comands, i played multiplayer and the game would randomly close and disconect me. Using proton there was no issue, the game ran smoothly and without any crashes.
Game runs flawlessly on Proton experimental
The game's native Linux support is likely outdated as running it without Proton ends up on a buggy display. You can interact with the main menu but can't see anything.
After testing it with Proton experimental, I had a flawless experience. Played for over two hours at capped 100 FPS and had a smooth experience without any issues.
prime-run game-performance %command%
During periods where lots of audio is playing it, some of it just doesn't play. This only happened twice in my 40 hours played, and only in The Following. Lasted for 5 second.sat most, not sure if this is a Linux or all OS issue though.
No problems whatsoever!
Only tinkering I did was launch flags, since that's required for my hardware. Runs fine under regular Proton aswell!
gamemoderun mangohud --dlsym %command%
Slight mouse "dead zone"
Después de probar varias configuraciones de compatibilidad porque el juego me daba problemas. ProtonHotfix funciono para mi y ahora va sin problemas.
Small shadow issues and sometimes grass rendering black in some places at different times.
Crashes randomly when VSync is enabled.
No issues with audio, graphics, input, or gameplay
