Fellow Foe
Published
Game doesn't start even with proposed changes, not even famous black screen
I've tried using:
PROTON_USE_D9VK=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_NO_D3D11=1 %command%
And changing DirectX version in my steamapps folder config for this game like proposed in other comments.
I've tried Proton 4.11-13, 5.0-10, 5.13-4.
Blank screen flashes with themed cursor, but then uplay client shows and gets stuck on "Looking for patches"
Tried changing DirectX version to 9 and using proton flags. Seen people reporting running uplay with admin rights on Windows fixing the issue, but I'm not sure how to do that in Proton.
PROTON_NO_ESYNC=1 is required for the textures to load properly
set launch options: PROTON_NO_ESYNC=1 %command% -nointro
Enjoyed 130h of the game, but had to put up with crashes and audio issues. Got decent look with medium LOD, SSR, TAAx8 at unstable 60 fps.
Crackling and missing audio from time to time. Also some audio getting distant/behind the wall. I've tried all solutions I've found including changing samplerate of pulseaudio device as well as providing the flag to the game. Problem persists. It is playable, but it's a bummer when You get an important battle and audio track is missing or overlapping.
While I've had bluetooth receiver connected, even though the controller was off, the hints would be displayed for the controller instead of the keyboard. Unplugging the bluetooth receiver fixed this issue for me.
Most crashing I've encountered was in the beggining of the game in the crowded parts of the game. While I've been doing badlands missions for an entire day I've had just one crash. Otherwise crashes can be as frequent as every 15 min up to 1 hour. From what I've researched it could be due to my dated and simplicistic motherboard.
Also people have been reporting missing textures, which I've encountered barely, which might be related to the use of SSD vs HDD. I did have to install mesa-git from AUR, and it works with linux-lts. Recommended to use gamemoderun %command%
Window keeps moving on the other screen when changing video settings.
AMD FSR is visible and configurable without any additional launch options.
I had to specify vulkan json file with VK_ICD_FILENAMES=/usr/share/vulkan/icd.d/radeon_icd.x86_64.json. The name of the file may vary so just list the files under icd.d and try one after another.
Just before a crash grass starts missing (even though there is memory to spare)
For me crashes are frequent enough, that I can't complete a delivery without rushing. It doesn't help that the game uses checkpoints, which can be Your entire journey.
__GL_THREADED_OPTIMIZATIONS=1 %command%
After launching the game with desired proton version, and closing it, run protontricks 1252330 winecfg and enable emulating virtual desktop for ALL (wont work for Deathloop.exe), set the resolution to the resolution You want to play in. Keep in mind that it will still try to grab your mouse.
Crackling when using invisibility slab
Game crashes if You try to switch the window
Mouse is grabbed when tabbing out using emulate virtual desktop method
Very rare crashes.
Warping issues when connection is not very good, otherwise a great experience.
Given my hardware, even using minimal desktop environment, I had to close web browser to satisfy VRAM requirements of the game. I imagine Windows would have the same issue though.
Works OOTB, no issues in 36 hours of gameplay.
Rarely Cloud save would get stuck and prevent turn progression. Save the game locally and load to fix it.
I haven't experienced any video flipping or anything out of the usual. Even works with ESG mod 1.6.
Can't enjoy a game that is consistently crashing.
Game crashes around every hour. I still have a lot of RAM to spare and a lot of processing and graphic power to spare. The settings fail to save and Your game state is lost.
Disabling FSYNC fixed frequent crashing for me. I managed to get almost 3h of stable gameplay without a crash. It seems to also have reduced some of lag that I was experiencing when voice line was being loaded.
As suggested I've used launch options:
DO=(%command%); "${DO[@]%eg2.exe}../bin/evilgenius_vulkan.exe"
Proton 6.3 didn't work for me. Switched to borderless mode to avoid fullscreen focus problems.
Was stuck on UPlay "Looking for updates" -- switched for UPlay update to 4.11
Vehicle controls didn't work in 4.11 -- switched to 6.3-4
Experienced vegetation flickering in 6.3-4 -- found it fixed in Glorious Eggroll
Mostly works out of the box
Achievements don't work. Completed the game on classic difficulty with counter deck and didn't get a single achievement.
Played 5h with great performance. Works out of the box.
When switching window in fullscreen, the proportions went all messed up, had to switch to windowed mode not to have issues
Mostly WOOTB, with a few minor issues
Probably a game issue: Lines would cut early probably due to movement, lines cut when another is triggered.
When using 1920x1200 resolution with 1080p render scale, it would sometimes switch between cropped and non-cropped view randomly during cutscenes or conversations.
Tabbing out would sometimes prevent window interaction after focusing again, and would lose resolution, selecting "ignore focus" setting fixes the issue.
On old kernel (5.4) I would get crashes due to radeon bug. After switching to modern kernel I got practically no crashes. Game doesn't quit properly though when crashed, and background zombie processes that eat at Your memory are left, so make sure to clean up.
Origin overlay is displayed as windows and if tiled by a window manager, will prevent Origin client (and game) loading until untiled.
Stuck on "Launch Error: Failed to load the anti-cheat module".
Proton EasyAntiCheat Runtime installed, tried multiple Proton versions.
Playable after recent game patches!
When exiting the game sometimes will remain open
If You need to use 5.13, the developers added options to skip the intro, which was causing problems for that Proton version. Otherwise the game seems to start properly now with Proton Experimental and Proton 6.3.3.
Works perfectly, but can warm my PC up, I guess there's a ton of particles it has to keep track of. Seing some people recommendations... PROTON_LOG=1 doesn't actually affect the game, what it does it creates a MASSIVE log file from Proton layer in Your home directory...
Slightly laggy for this kind of game, but still very enjoyable experience
First game was very laggy, probably due to disk being busy. Had some games in which the amount of stuff happening on the screen turned the game into slideshow. Probably will be optimized better with time.
One crash in 5h gameplay and ocassional hangups
Works out of the box
Two crashes in 7 hours of gameplay. Not bad honestly
