machinedgod
Published
Worked out of the box for me, but I switched to 6.3-8 (to lock down the version).
I didn't try the RTX.
Crashes out before it starts the game
This game used to be native. Dev silently pulled down Linux support (I found that out by sheer accident), so you're dependent on Proton.
I tested with GloriousEggroll, Steam Linux Native and Proton Experimental (6.4.x) and neither one works.
Works very much as expected
If you're running a tiling WM (xmonad), make sure to set the WM name to LG3D. WIthout that, game wouldn't run for me.
Remember to switch Proton to 3.7, and optionally use PROTON_USE_D9VK (works fine without it too, cutscenes included).
This made me think the issue might be with D9VK, so I tried Proton 5, both with ESYNC=0 and USE_WINED3D, however cutscenes remained choppy.
Whatever - use Proton 3.7, ESYNC, and you're good to go.
Doesn't launch with any proton version available, including GE.
It usually shows splash screen, then fullscreen image, then hangs in black screen for awhile and then crashes out.
It is playable and finishable, but it ain't pretty
Seems to be the shader bug, related to textures. Meshes seem fine.
Worked out of the box.
I run tiling WM, and running game initially creates a tiny window - I have to push it to fullscreen manually. If, during gameplay, I try to resize the window it'll again take on that tiny form; resizing it to fullscreen afterwards will leave UI elements (such as radar) disproportionally small.
Tried all tricks listed here
Tested protons from 4.11 onwards. Tried protontricks. No dice. Starts up, flashes the window, then closes.
GE
Game wouldn't just crash - it'd reboot my machine. I don't know if this is caused by GPU overheating, but system logs say nay.
This is nowhere near Platinum rating: launching the game consistenly is nearly impossible.
First, game is going to verify what is the newest GPU driver for windows, and unless you have that version, it'll show you the window offering Play or Open Browser To Download - but if you click Play, it'll just close itself.
Second, I've tried all official Proton versions since 5.3, across 6.4 over to Experimental, and I've tried 3 versions of Eggroll (5.12, 6.4 and 6.15). I also tried various suggested flags (NO_ESYNC, GFX_VENDOR) and combinations of Doom's flags - nothing works.
I think the launching issue really is with driver version; if the version doesn't match official Windows version, game won't start because - I'm assuming AntiCheat will think drivers have been tampered with. There might be a way to modify a driver's reporting version (haven't checked/tried) but if my assumption is true - even a semi-smart AntiCheat would also verify driver's hash, and bail out for same reason (maybe even earning you some sort of permaban, so tread carefully)
Launch options mentioned in other poster's notes (__GLX_VENDOR and Doom launch parameters).
The game sometimes just wouldn't want to launch, only to launch again a day or two after. I realized, after some research - that this is the DRM being triggered. Once it triggers, it'll refuse to launch the game for 24h.
Originally DRM was preventing me from running, and every time I'd move laptop between networks, it'd refuse to run a game for 24h.
Thing is - for past two weeks, this got automagically fixed, by itself. Only thing I can fathom might've affected it, is that I updated vulcan packages on my system. Currently, it just runs without issues, even when I switch networks, and I can have as long playsessions as I want.
Point is, if everything seems to be fine, but game just refuses to launch, and doesn't leave any logs, try again in 24h and see if something changes.
__GLX_VENDOR_LIBRARY_NAME=whateverman
Denuvo
Took me awhile to figure this out, but - every now and then, game would refuse to run. It would show the taskbar with ID icon, and then just close.
The reason is Denuvo gets triggered with cached shaders, because these are downloaded to speed up runnin games!
Go to Steam -> Settings -> Shader Precaching and simply uncheck Enable shader pre-chaching.
This makes it run every time.
Note: for one reason or another, with shader precacheing disabled - I can't get Deep Rock Galactic to run.
6.15 Glorious Eggroll
Refuses to run.
- dialogue warning about outdated drivers
- click Play
- shows taskbar with ID software icon
If it decides to run, after 2-3 seconds the game would launch. If it decides not to - it'd keep taskbar up for about 5-6 seconds, and then just close.
I thought this is Denuvo being triggered because I spotted a pattern: when my laptop would hook up to a different WiFi, it would refuse to run, and then it wouldn't run for about 24h. Then, it'd run normally and continue running normally until I switch WiFi again.
I realized that, when I disable shader cacheing, it'd keep running no matter the WiFi - but once game got updated, it would just refuse to run, period.
I enabled shader cacheing back, it started working with the old pattern. For the past week, since last cosmetics update - it doesn't launch at all.
I'm back at a point that I stated during the first report for this game:
Way too unstable with launching to be enjoyable.
Denuvo? (I read articles that it was removed?)
Until someone figures out why this game runs or doesn't run at random - it is more frustrating than anything, to want to play, and then not be able to.
__GLX_VENDOR_LIBRARY_NAME=whateverman PROTON_NO_ESYNC=1 %command% +com_skipIntroVideo 1
As poster before me said - boot into LTS kernel (my version is currently 5.10.68-1-lts)
Wanted to test previous poster's suggestion, and it worked like a charm. If you're on Arch (like we are), its enough to install linux-lts kernel and boot into it, rather than downgrading.
Doesn't work again, either kernel 5.14 or 5.10
Same story: I open to driver information dialogue, I close it, a taskbar with ID icon appears, stays on for about 4-5 seconds, then disappears.
At first, I managed to have it run by restarting X if I'd put my laptop to sleep - but now it just won't budge no matter what.
Tried all offered Proton versions, and tried all options suggested by others (including the -novid and -w/-h setup), but to no avail.
Interestingly enough - I don't get just the black screen hang, I get the error dialog, clearly stating that it can't find "materials/console/background_??.vtf" file.
Now, this is exactly the same error I get with one other game, E.Y.E. Divine Cybermancy - so if I, or someone else, figures out issue for either one of these two games, I'm sure both'll get fixed!
Tried making various uppercase/lowercase symlinks and copies of that background.vtf file, thinking that maybe file loading was counting on case insensitivity - nothing. Just for kicks, I tried USE_WINED3D too, but nothing.
Once window loses focus, game crashes to black screen
Change launch command to:
PROTON_USE_WINED3D=1 %command% -w 1920 -h 1080
The -w and -h flags add custom resolution to source engine.
Appendix:
if you check previous issues I had with this and all other Source titles, it was complaining it can't find data. I've fixed it thanks to protontricks giving me a tip, so here's an explanation for anyone having same issues.
I've been lugging my $HOME with me for over 10 years, and somewhere down that line, steam changed the name of one directory from SteamApps to steamapps.
What happened is that half of my stuff would reside in SteamApps and other half in steamapps - which on windows would not happen of course.
To fix all SourceEngine 'cant find' errors, simply merge all data from SteamApps into steamapps, and perhaps reinstall few games (I had to do it with DRG for example).
[UPDATE 32] Crashes as soon as mission starts.
No audio at all.
Black screen for few seconds, then crash every time mission is about to start
It used to work flawlessly prior to update 32, and I was noticing these issues on experimental branch as well, but thought they'll be polished out. Turns out, not.
As soon as loading is finished on the mission screen, I get black screen and then few seconds later, a crash. Audio is missing completely.
Will go and try to debug this a bit and come back with another report.
I looked at the logs and noticed that the issue was access violation, but couldn't deduce what is the address (around 0x0000002a) referring to. In their steam community pages, they mention recurring error with intel drivers, which causes access violation on 0x00000005 , but it made no sense to me that the issues are graphical, since game launched into the droppod hub normally.
I tried multiple flags (WINED3D, NO_ESYNC, disabling LARGE_ADDRESS_AWARE), etc, no dice.
Eventually, I started forcing/testing different proton versions, and 5.13-1 worked fine. Lighting seems slightly saturated, but I'm not sure if this is true or not.
Worked out of the box for me.
Low FPS if you use settings higher than Medium. Can be improved a lot by tinkering with Display options. HIGHLY likely not related to Proton, but suffers same issue on Windows too (has been noted in forums).
Keeps crashing out with an error dialog saying it can't find 'materials/console/background01_widescreen.vtf'
The case in the filesystem is different ("Console" rather than "console") so I thought that might be the issue. I added a symlink. Nada. Copied whole directory. Nada.
I used PROTON_LOG=1 to get more information and it seems like the game wants to start in a 1920x1080 resolution, and then it can't find the background image for it.
I tried enabling floating mode for it so that it doesn't have to stretch itself, but still nothing, and found -window and -noborder options in forums. Nada.
I tried renaming everything inside EYE to use lowercase. Nada. After restoring the names, I tried modifying .cfg file, which does file/dir inclusions, to use correct-case directory paths. Nada.
Finally, I thought the working dir might be off, so I copied everything from inside EYE directory to the outer level. Still nada.
I can't get past that error dialog.
Switching the window focus crashes the game
Change launch command to:
PROTON_USE_WINED3D=1 %command% -w 1920 -h 1080
The -w and -h flags add custom resolution to source engine.
Appendix:
if you check previous issues I had with this and all other Source titles, it was complaining it can't find data. I've fixed it thanks to protontricks giving me a tip, so here's an explanation for anyone having same issues.
I've been lugging my $HOME with me for over 10 years, and somewhere down that line, steam changed the name of one directory from SteamApps to steamapps. What happened is that half of my stuff would reside in SteamApps and other half in steamapps - which on windows would not happen of course.
To fix all SourceEngine 'cant find' errors, simply merge all data from SteamApps into steamapps, and perhaps reinstall few games (I had to do it with DRG for example).
Starts a black screen, the pops dialog that says "Fatal error"
I only tried Steam Play, didn't try tinkering. Your mileage may vary, but I'm not invested enough into EA title with 2 reviews to try and get it to work.
Deleted compatdata and used winetricks to install dotnet4, but should've probably used protontricks instead. In any case, minimum amount of tinkering.
Game works without PROTON_USE_WINED3D flag, but it is a slideshow. Maybe it'd be worthwhile experimenting with D9VK, but using NO_ESYNC.
Just use the custom command: PROTON_USE_WINED3D=1 %command%
On my hardware, game like this should fly in 100fps at least (and it does without WINED3D
So... if you don't use WINED3D, FPS will fly (at least for me), and drop steadily until it becomes a slideshow (12FPS), across approx. 60 minutes of gameplay. Restarting the game (fully quit, not just to main menu) will restart the issue, so you can basically play well for 60 minute sessions.
On the other hand, if you use WINED3D, the FPS will severely drop to begin with, to around 25-30, and I put SSR and Sky refs to Low to maintain stable 30fps. I played for over 3h and FPS didn't degrade, but its just not really as comfy as +60FPS.
Your pick, basically.
Worked out of the box, online and all.
Sometimes it slows down to like 5FPS. Settings don't affect a thing. Probably an issue with game itself.
I actually don't know if it has an AntiCheat.
Couldn't get past UPlay login
This bug is tracked in 2017 on winehq, and apparently closed due to a bugfix (initializing memory struct with zeroes) but I couldn't get it working.
I tried:
- setting wineprefix to correct compatdata, then using winetricks to add corefonts, crypt32 and some other modules from winehq appdb Gold suggestions
- disabling dx11 libraries in winecfg
No dice. UPlay wouldn't let me use offline mode unless I login at least once, and trying to login would immediately pop network error.
I tried winetricks winehttp as suggested somewhere, but then the stdout shows error log about unsupported network feature and suggests using winsock.
Proton-GE 6.15
Game crashes out every 10-15 minutes on a random thing
Proton version 5.13 and disabling FSYNC and ESYNC fixed the crashing issue every 10 minutes. I've had 2h playsession, no problem.
Here and there, you'll probably experience massive frame drops for few seconds - but this is a game bug, and something win players experience too.
Proton-GE
You dont have to install a Proton fork (Glorious Eggroll) to enjoy the game; it works just fine with Steam default however - you won't be able to see any ingame movies, such as intro or little tutorial movies. Those aren't important at all to the gameplay so... if you don't want to bother for 100% experience, you dont have to.
GloriousEggroll (6.15)
For one reason or another - the game is completely silent. Fully playable, but, mute.
Worked out of the box for me
I actually don't know if there's an anticheat?
Some reports mention audio: I use PulseAudio on my system and everything works out of the box, not just for this game - but all Proton games. I strongly recommend you use it at the very least when you run Proton.
At the time of writing this, 6.3-8 is default stable Steam version. For me, it boots to main menu, where game asks you to press any key to start.
It'd crash after I'd press the key.
4.11 works great (kernel 5.10, package linux-lts on arch)
Game would show black screen without the flag. If window would be resized, you could see the graphics, but the moment you stop - it goes all black. The flag fixed it.
GloriousEggroll
After clicking Save and Quit, game goes back to main menu - but Continue button is grayed out. Since the game just launched, its possible this is a developer error.
Works out of the box, sans the movies
The movies wouldn't play for me, in the game (displaying the raster bars instead). Switching to Proton GE fixes it, as it does in all other games displaying the same issue.
Tried all Protons (3.7 to 5.0-6) and wine 5.5
It launches, reserves screen space for a window, then crashes clean out after 2 seconds. Log shows something in the game exe itself threw an exception. Didn't bother tracing out what exactly, but I pasted the stacktrace from PROTON_LOG at the bottom.
I have tried changing game.ini to make game run in windowed mode, to no change.
I have tried overriding d3dx9 with winetricks - no change.
I am suspecting that game doesn't like my tiling WM deciding what the window size should be. If you're using tiling WM and this is crashing, I suggest launching the game in floating mode and see what happens.
I tried floating steam instead and letting the game take over whole screenspace, but again - no changes.
Proton log:
...
Threads:
process tid prio (all id:s are in hex)
00000008 steam.exe
0000002c 0
00000009 0
0000000e services.exe
00000028 0
00000022 0
0000001a 0
00000015 0
00000014 0
00000013 0
00000010 0
0000000f 0
00000011 plugplay.exe
00000017 0
00000016 0
00000012 0
00000018 winedevice.exe
0000001f 0
0000001e 0
0000001d 0
0000001c 0
0000001b 0
00000019 0
00000020 winedevice.exe
00000025 0
00000024 0
00000023 0
00000021 0
00000026 winedevice.exe
0000002b 0
0000002a 0
00000029 0
00000027 0
0000002d explorer.exe
00000033 0
00000032 0
0000002f 0
0000002e 0
00000036 (D) Z:\home\john\.local\share\Steam\SteamApps\common\King's Bounty - The Legend\KB.exe
00000051 0
0000004e 2
0000004d 15
0000004c 15
0000004b 0
00000046 15
00000045 0
00000044 0
00000043 0
00000042 0
00000041 0
00000040 -2
0000003f -2
0000003e -2
0000003d -2
0000003c -2
0000003b -2
0000003a -2
00000039 0
00000038 0
00000037 0 <==
...
Command: ~$ protontricks 449610 d3dcompiler_47
Few seconds after starting the drive, game locks up then crashes
Tried all proton versions I have installed from 4 to 6, and 3 Eggroll versions (5.21, 6.4 and 6.15). Same issue everywhere. Also tried with NO_ESYNC and NO_FSYNC, same issue.
Works flawlessly after this morning's update.
My previous report mentions a lot of test, but dev has updated the game, and now it just works normally with stock proton 6.3-6, no extra flags or tweaks.
Its OK, it is very playable, but rift battles will just make you uselessly clicking around
Tested both with default Vulkan and WINED3D, Vulkan's performance is worse, but D3D has missing textures and zbuffer issues.
When opening rifts in the world - game would suffer unplayable stuttering, strong enough that your char can get killed just because the world keeps being updated (audio too), but rendering runs in 0.5fps.
Crashed once while playing during those 2h. Could be not Proton-related, but just a quirk of a game itself.
I am not sure which anticheat they use, but it isn't causing issues (unless FPS drops are due to it)
Worked out of the box for me
Some reports mention that talking into the communicator doesn't make the ghost respond, due to this being Cortana feature. I haven't try this but from what I heard, it doesn't really matter - as long as you make any sort of noise into the communicator, you'll provoke the ghost. What you'll miss out on is ghost responding in contextually appropriate manner (eg. "Where are you?" -> "Behind you")
Worked out of the box, minus the movies.
One of the minigame includes vacuuming the sand, and there's a significant FPS drop on this minigame. EVERY other minigame works just fine.
Don't know.
For the tutorial movies, you should try running Proton GE (or install the Proton patch that lets you see videos). However - running the game with GE made my FPS drop to unplayable across the board.
In addition, as mentioned - the vacuum minigame is borderline unplayable (FPS drops to 1-2Hz)
Works fine, crashes the moment you look at a blood splatter.
Game chrashes SteamVR every time there's blood splatter. From tutorial and on. Unplayable.
Joined another people's lobby and played for a bit, then made my own and had someone join - we played together without a hitch for about 2h.
So, I changed few things since last time I tried it: I prioritized both "vrwebserver" and Requisition's exe as processes, and I limited power used by GPU to 55W (from default 80W). Also, game received an update. I don't know which one of these fixed it, but now everything works as normal.
During nightfall, from high up, you can see reflection artifacts in the water on high enough settings.
Unless you cap FPS to around 40, it stutters.
Glorious Eggroll
In addition not not being able to see movies, I experienced weird camera jitter when focusing to another window, then focusing back on the game.
I restarted and switched to Proton GE (mainly to fix the movies), but camera jitter never came back, even if I kept focusing other windows constantly.
So... works fine with default settings, but probably better with GE.
Works 99% out of the box.
Movies don't work on standard Proton, and using GE makes the game not load.
If you want to see the movies, you might want to tinker more. I just skip through them.
Works out of the box with minor problems.
Lighting looks blown out in few cutscenes, textures missing
Crashed once for no reason, after about 45 minutes playing (just before saving Amanda). Started the game again, everything was fine.
Game says it can't start fullscreen mode, and then runs normally. I run tiling WM without decorations so it looked like fullscreen to me.
Works out of the box
Framerate seems tied to refresh rate, when vsync is on. My monitor refreshes at 144Hz and the game was quite literally unplayable.
If you experience the same issue, and you know your refresh rate is very high - try disabling VSync in options, it should fix it.
There will be bugs - but that's normal for an EA title, not related to Proton.
Game generally runs smooth, but sometimes scrolling causes a spike in very low FPS (drops to 2FPS or so)
GloriousEggroll
I used ProtonGE because I read some people had issues with movies.
Aside that, game sometimes experiences strong FPS drops, but I read that this issue exists on windows, so its not Proton related.
Works out of the box, better than for my Win friends (who have occassional crashes, hahaha)
Works out of the box, nothing to worry about
1-2 stuttering when level loads. Very probably not a Proton/platform issue and highly likely, same thing happens on the native platform.
Maybe your hardware will do better than mine. Who knows.
For RTX2060, game runs very choppy, with average of 12-16FPS or so. Marginally improved by setting all settings to low, but choppines is still there. Quite probably because its alpha and will be improved over time.
Crashed about one hour into gameplay, after I changed all the graphical settings for the 3rd time.
Crashes out during level loading
Tried few proton versions (including GE) and NOESYNC flag someone suggested. Nothing helped, crash is consistent.
Glorious Eggroll 6.21
I was able to run the game with two Steam-provided versions: Experimental and 6.3-8. The game would launch normally and when I'd start a new game - it'd block when the intro movie was supposed to be shown. I waited, tried to skip it, but no dice. I tested with few other GE versions (6.4, 6.15, 6.20) but neither one even launched the game.
At the time of writing this, 6.21 (the hotfix patch) is the newest GE release; that one launched the game and it all works fine.
Works out of the box.
During animations that preclude conversation, there'll be garbage at the bottom of the screen, while the properly rendered screen slowly slides in place. Lasts for 1-2 seconds then its all good.
If you run multi-monitor setup, during conversations in the game - mouse will be locked in a rectangle representing conversational UI on the main monitor - regardless of which monitor is game displayed on. Easily fixable by playing the game on the monitor that's marked as primary.
GloriousEggroll 6.4
Game will crash here and there, but very rarely and long playsessions (2h+) are normal.
Couldn't get past Origin launcher
I use tiling WM, so the moment I launch origin - my screen gets covered in numerous tiles.
The black window owned by the actual game shows up, and then I get the dialogue saying that its not possible to allocate enough VRAM to launch.
Tried numerous Proton versions (including few eggroll fork versions), all the same behaviour.
Properties -> General -> Set Launch Options -> "PROTON_USE_D9VK=1 %command%"
Flawless. Didn't even realize its not native client.
A note worth mentioning - spatial audio works without issues, as long as you use PulseAudio.
It works great, with crashes here and there - but I believe these are just game bugs, not Proton-only bugs.
About once every 2h, I get "Fatal error" and game just closes. Its not a big of a deal because game loads fast, and saves itself all the time during playing, so nothing is lost.
Just wanted to add a positive note - game works very well with focus switching and all (auto-pauses itself).
Works out of the box (minus intro animation)
After selecting new game and difficulty, you'll be greeted with black screen. Not to worry, this is when animation is supposed to be playing. Just hit "Esc" and enjoy the game.
Won't progress past loading screen
I tried with various versions of proton: official 5.13, 6.3, and eggroll 5.21, 6.4 and 6.15. I also tried with NO_ESYNC flag. I also tried messing with game's options.
Nothing changes, can't load into a game.
Proton GE (Glorious Eggroll)
Just go on GitHub, follow instructions on how to install Proton-GE and add it to Steam, and use it.
