colcaire_irina
Published
Can run just as well as on Windows 10, however the apex-legends-cache r5apex.dxvk-cache is required so playing will be mostly smooth
obs-gamecapture mangohud %command% -dev +fps_max 190
This is not Proton/Linux specific but just because of the game having bad servers from time to time.
A few notes when it comes to running Apex Legends in Linux (since when done right it runs as well as it does on Windows):
- Proton Experimental or Proton-GE is required for this game with DXVK, as well as copying the community-based shader cache from Github (apex-legends-cache) to steamapps/shadercache/1172470/DXVK_state_cache and replace r5apex.dxvk-cache if already existing. Proton 7.0.3 onwards seems to ignore this replaced cache for some reason.
- I use 21:9 1920x800 sometimes because Linux has it activated for some reason, and with Proton-GE it seems to force sharpening filter that I cannot disable because disabling FSR crashes the game. Not a concern if you play normal 16:9 1920x1080.
- You can manually let it be compiled while playing a few times, hence technically choosing 'Yes' when asked if no tinkering is needed, but this is NOT recommended. That means basically solo Q'ing in pubs multiple times until you explore most of the map(s), as the compilation will be severe stutters and freezing when initially being on the map.
S19 Update does not contain the necessary EAC files for Proton EAC Runtime support
PROTON_EAC_RUNTIME=1 DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 VK_ADD_LAYER_PATH=/usr/share/vulkan/implicit_layer.d:$HOME/.local/share/vulkan/implicit_layer.d MANGOHUD=1 VK_INSTANCE_LAYERS=VK_LAYER_MANGOHUD_overlay:VK_LAYER_OBS_vkcapture_64:VK_LAYER_VALVE_steam_overlay_64 gamemoderun %command% -dev +fps_max 240
"The client is not running the anti-cheat, or has failed the anti-cheat authentication".
This error rears its head again as I initially wanted to try out S19 to see if playing Apex could feel compelling again. This occurs regardless of whether I use Proton GE 7-50 (which I used prior to the S19 update), 8-22, Proton Experimental or 8.04. Verifying integrity of Apex files and Proton EAC Runtime has the same issue.
Checking the forums shows that EasyAntiCheat_x64.so appears to be missing leading to this cause. Either watch for updates on the forum and/or wait for new patches.
Works as well as the Windows and macOS version
Worked well whether I was in Pop! OS or Zorin OS, just as fine as it was on Windows. Only time will tell if more stringent anti-cheat measures would be used for this game though, if it can still maintain functionality over Proton
There is an imposter among goose
VK_ADD_LAYER_PATH=/usr/share/vulkan/implicit_layer.d:$HOME/.local/share/vulkan/implicit_layer.d MANGOHUD=1 VK_LOADER_LAYERS_ENABLE="VK_LAYER_OBS_vkcapture_*" %command%
Easy Anti-Cheat is now required by the game, but I don't notice any difference compared to when it didn't have it.
Providing an update to the status of Goose Goose Duck given recently this year, Easy Anti-Cheat has now been implemented into the game. It still works just the same as it was prior to anti-cheat, just ensure the Proton Easy Anti-Cheat Runtime is installed.
Works equally as good as the Windows version (over Proton). Native is OK, but the font rendering looks thinner/less cleaner by comparison
LD_PRELOAD="/usr/lib/x86_64-linux-gnu/libstdc++.so.6 /usr/lib/libgcc_s.so.1 /usr/lib/x86_64-linux-gnu/libxcb.so.1 /usr/lib/x86_64-linux-gnu/libgpg-error.so.0 $LD_PRELOAD" mangohud %command%
When Insurgency was announced to be supported by BattleEye over Proton, it was the time the game worked with anti-cheat VAC secured servers and has remained that way since.
Using the preload options over Zorin OS (to point to additional libraries the game needs) is now required for the game regardless if you want to go native or Proton, in a way that it wasn't during the time I used it on Pop! OS. Thankfully, other than that, it works as smoothly as it was before.
Make sure to have Proton BattleEye Runtime installed
The preload command to get the game running in Proton 7 in the past no longer personally works, but Proton 6 still does, so I'll stick to that.
mangohud %command%
The first time I loaded the game some UI elements went intermittently missing. After reinstalling once, it no longer happens.
Appears to be currently working as well as in native version. Time will tell if stringent anti-cheat measures would be implemented.
Proton Experimental does not work. Using Proton 7.0-4 does work by comparison, albeit with the aforementioned UI elements having an issue the first time. It has not been replicable since the reinstall though.
As long as realistic expectations are set, Proton should provide an acceptable experience with mods possibly looking better
Using ACO 20.1.7 compiler with Launch options: RADV_PERFTEST=aco mangohud
Sometimes while on fullscreen, doing an Alt-Tab between programs such as Brave browser and back to Ravenfield causes the keyboard keys to fail to respond only ingame, force quitting Alt+F4 and reopening normally was needed from my limited testing
While there is a native Linux client, some mods (at least for a few maps like Baneburg) display textures incorrectly when running them in the native Linux version - they show up as colored pink or black instead. Running the game in Proton helps alleviate that, at the expense of seeing slight stuttering and frame drops roughly ~10 fps less than the Windows native version depending on the mod and how many bots/vehicles are visible at a time.
It's not greatly optimized even for native Linux or Windows anyway, so such moments shouldn't detract from the overall experience.
Runs better on Proton than the native Linux OpenGL implementation for the Beta 26. The bugs from Beta 26 on Windows do carry over here tho
I only tried the Beta version 26 at the time of writing this. I cannot attest to the non-Beta version as I am not interested in exploring that currently and would prefer testing the Beta instead. As stated above, the Beta 26 is buggy when it comes to mods due to the Unity update affecting animation behavior when it comes to mods and some collision of objects is affected, so those remain, but aren't any different from the native Windows implementation.
Crashes or fails to load anything as soon as EAC appears
Whichever requirements are needed to enable Linux support with EAC, Embark Studios still haven't enabled it for the Open Beta. Unfortunate but unsurprising.
PROTON_ENABLE_NVAPI=0 PROTON_USE_EAC_LINUX=1 %command%
The FINALS has been a game that every other patch would abruptly not work over Proton. To be fair, some of this is caused by EAC updates (where other games like Apex don't work and also need updating as well), but other times like with this most recent 3.6.0 patch I'm less certain.
Either way, the usual case to get the game working in these times is to find an experimental or hotfix branch that works. This time it's slightly more difficult as you have to specifically choose bleeding-edge as the branch (Right-click Proton Experimental on the Tools sidebar of Steam > Properties > Betas > bleeding-edge - latest and untested) and only after that will the game work again at this time.
DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 PROTON_ENABLE_NVAPI=0 %command%
It seems that for now at least, using the Proton Experimental Bleeding-Edge build (Right-click Proton Experimental on the Tools sidebar of Steam > Properties > Betas > bleeding-edge - latest and untested) is needed, alongside verifying integrity of game files after a new update to bleeding-edge if there is any, to play the game on Linux again. Played yesterday just fine; currently playing right now with only needing to reverify after a bleeding-edge update to get things up & running again.
Embark needs to reupdate for EAC Linux support again to not need bleeding-edge builds like this.
