Pspritechologist
Published
The cursor did not appear immediately upon dying and required I opened and closed the menu before being able to select a respawn location. No idea if this is related to Proton.
During the intro looking out into the great wilderness caused signifigant slowdown, even when the distance itself wasn't being rendered (indoors). This did not occur throughout the rest of the gameplay (which was inside the facility), and the intro otherwise ran fine.
Game freezes on the first loading screen when launched with DX12. DX11 worked out of the box.
-d3d11
Occasionally, usually following an alt-tab, button presses would not be detected properly. This would require me to alt-tab in and out a couple times before the issue would resolve.
I personally found better performance with the launch option above, which forces Direct3D 11.
The game's stability is not perfect, but overall not a huge problem. Crashes would happen reliably before I used sudo sysctl -w vm.max_map_count=214783642, which mostly resolved the instability.
The Easy Anticheat script occasionally needs to be re run for some reason, which requires verifying the game files. This can take some time. I believe this usually follows game updates or potentially Proton version changes, and the game will sometimes crash on launch and other times fail to join games until this is done.
gamemoderun PROTON_USE_EAC_LINUX=1 PROTON_ENABLE_NVAPI=1 %command%
The game seems to need to be reverified frequently otherwise you either crash upon loading into a match or get kicked. This is likely due to reverifying rerunning the anti cheat install script. Sometimes multiple verifications are needed.
I had previously used -dx11 in the launch args as I found it ran signifigantly better for me, but after a recent update the game started freezing during load up at random times never allowing me to actually play. Removing this arg fixed the crashing, but now I need to play with DirectX 12 :(
