VerifiedShow Details
Unknown
The game runs relatively well, Was able to enjoy round 20 exo zombies without issue
Good overall experience, some hitches with the cutscenes causing audio sync, but it worked fine after a restart.
Some audio issues, restarting the game fixed them
Complete random shut downs, but not enough that it could have been Linux to blame
gamemoderun %command$
Crashed about 3 times throughout the course of the campaign
The game plays fine, but I'd avoid it because of this: CVE-2018-20817
When playing the game I did not have any audio issues. When watching cutscenes I had big audio problems while the game was loading next chapter in the background. Sometimes the audio did not play or was cracking. Other issue is that, when playing the game and in-game audio was fine, it was borking sounds from other sources like browser audio. Annoying.
I am surprised how well it plays, you can enjoy the game on linux, even with mentioned slight audio issues. I played only 1 hour, because I decided it was not worth my time after all, but this is not because of they game was running on linux.
This game used to stutter like crazy for me with old versions of Proton, but all of those issues have been resolved. It works great out of the box now with smooth frame delivery.
In Exo Survival, keyboard/mouse input stops working when match is started
Frequent heavy stuttering/hitching, game runs at a consistent 60 otherwise
Non-singleplayer modes can't be launched from singleplayer, game sometimes doesn't close properly
Multiplayer modes (main multiplayer, Exo Survival, Exo Zombies) can't be played offline, even locally, it works when online but this should not be necessary
I enabled also fsr, to improve fps, and some other options
Expect a crash once a level ends, but don't worry about the saves as, once you restart the game, it will continue where you left off.
RADV_PERFTEST=aco %command% PROTON_NO_ESYNC=1 %command% -nocrashdialog -noipx
Proton-5.9-GE-6-ST
Slight stuttering using fullscreen. Borderless-window mode fixes the issue.
Loading times are a bit long even on a SSD, but bearable and not a big deal.
Unfortunately, the game crashes after each level. Usually restarting the game fixes the issue temporarily until the next one.
Takes a bit long to load even on SSD. The crashes are annoying. When you add the load time it can be frustrating.
5.9-GE-4-ST GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.9-GE-4-ST
Crashes at end of each level
Works well, w/ Kernel 5.6 and new proton @ native resolution with decent detail settings - has crashed a few times during a loading screen
Super rare, linked to loading screens
Stuttering and crashing
some stuttering which was due to shader caching being disabled in order to get the first mission even loading
the game crashed always at the exact location in the game
I had to disable shader caching completely in order to get the first single player mission even loading. After that, I was able to play the first mission. However, the game crashed always at the exact location making it impossible to play.
SÓ ASSISTIR O TUTORIAL - SE O VÍDEO LHER FOR ÚTIL DEIXA UM LIKE E COMPARTILHE
Got some cutscenes without sound after a alt+tab. Set screen borderless mode in game options to avoid sound problems. Set controller 'forced off' in game > properties > steam input per-game avoiding messed buttons. Don't know how was on Windows but i feel that loading take too long between chapters.
Load times for single player are very long (10mins), even with an SSD. There is then lots of stuttering once you are in.. Multiplayer works fine but you have to deal with further stuttering whilst the shader caches. Also worth noting almost no one is playing the multiplayer. I'd skip this.
Runs nearly flawlessly after shaders are compiled (happens normally during gameplay). RAM usage seems sane now (I haven't seen it fill up 16GB of RAM even with extended gameplay). Every once in a while the game will freeze and need to be re-opened.
Gameplay is perfect once shaders have compiled. Suggest turning "preload shaders on", loading each map, then turning them off. _____________________________________________________________________________________________________ Only issue is that shaders consume RAM and can quickly fill 8GB if playing different maps. Some maps cannot load with just 8GB. If RAM fills up, system will go extremely slow and can appear frozen. 16GB minimum recommended. If you play many different maps one right after the other, you will eventually reach a point where you need to restart the game to free up RAM.
Unknown(2+ hours with Proton)The game runs solid, 1440p ultra-wide, high/ultra settings, 90-150fps on average. The shader preload can take 10+ minutes which is a minor annoyance.
Unknown(2+ hours with Proton)Turned off vsync, runs perfect without screen tearing (using compiz on Xfce 4.13). Choppy at first due to shader compilation. You can set "Options -> Video -> Video Advanced -> Shader Preload" to on to precompile all shaders the next time you go to start a match. It will take a few minutes, but you only have to do this once for a few maps for smooth gameplay thereafter. No issues playing with other players using Proton. Played for about 3 hours.
Unknown(2+ hours with Proton)I configured preloading shaders to be completely disabled to fix loading times in the config file. Proton is set to use a virtual desktop, with no DLL overrides. I used regedit to disable CSMT and GLSL. I configured my in-game settings to disable problematic graphical effects, such as the settings regarding reflections, etc. I can run multiplayer and singleplayer perfectly with the occasional stutter. With preloading shaders disabled, the game will always stutter a little when entering an area you haven't been before. For a mechanical disk, the load times are too long. On a SSD, people might have better luck. ~3-4 minutes into a match after going around the map, the stuttering disappears, I assume because the game has loaded the map already. With PulseAudio in WINE, I had signifigant audio crackling after playing for an hour or so. I replaced the bottom part of my /etc/pulse/daemon.conf with this: https://pastebin.com/dpUNSfdR
I had to configure these settings for both the singleplayer AND multiplayer prefixes.
NOTE!: In multiplayer, I had a bug where I couldn't move my mouse and my "W" key appeared to be stuck, so I could only run into a wall forever and get shot at. I allowed WINE to capture the mouse, and set a virtual desktop at my resolution (1920x1080, configure it to what you use, such as 2560x1440, 3840x2160, etc). I also set multiplayer to use a Borderless Window, as fullscreen seems to trigger this bug too.
Unknown(2+ hours with Proton)
Loading times are significantly improved if you disable Shader Preload in the Graphics settings. However, this will incur significant stuttering during gameplay until all the shaders have been cached. The stuttering makes the game almost unplayable. When the game isn't stuttering, it performs admirably. I get around 80-100 FPS on my Vega 64.
UnknownExtremely slow loading. First level took 30 minutes to load on an HDD. Crashed when I attempted to change resolution to 4k
Unknown
