myxlmynx
Published
Proton-6.10-GE-1 GloriousEggroll
Proton-6.10-GE-1
Proton-6.10-GE-1 GloriousEggroll
Proton-6.10-GE-1
When you Alt-Tab between game and desktop, it will soon occur that the game won't register the ESC key anymore, which is annoying, but you can seemingly fix that by hitting the Alt key in-game. After that, ESC should work again.
After disabling Steam Overlay, no problems with default Proton.
Steam Overlay doesn't work well with this title. Disable Steam Overlay and it's fine.
You need to disable Steam overlay. And to close the annoying "Your graphics driver is not supported" popup from UPlay, use Alt+F2 to bring up the UPlay Overlay and close the popup. No problems otherwise.
--skip-launcher
Using Proton Experimental just because I read about having to use it, but didn't try without. Maybe also runs fine without. Usually, regular Proton works soon after release as well.
Initially I didn't start the game with --skip-launcher, so the launcher popped up. There are 2 settings in there which I disabled: telemetry and warnings about graphics driver versions.
Maybe(?) these 2 settings also are on-by-default when skipping the launcher entirely. So maybe you should first disable those 2 things, before you skip the launcher and start playing the game without the launcher entirely. Not sure if necessary though. Maybe it's just the launcher adding these things on top.
Runs great out of the box on default Proton, just make sure not to Alt-Tab out of the game
When you alt-tab out of the game, it can occur that you can't get into the game anymore
MANGOHUD=1 MANGOHUD_CONFIG=fps_limit=60 %command% --launcher-skip -skipStartScreen
RT settings for ~50-60fps on my HW @ 4K: FSR 2.1 Auto, RT on, RT Reflections off, RT Shadows on, RT Lighting medium, Path Tracing off
Haven't played much yet but so far no problems
gamescope -h 2160 -b -f -e -r 60 -- %command%
Should run well out of the box in most cases using default Proton, but if you run into stability issues see my notes
ENABLE_VKBASALT=1 gamescope -h 2160 -f -e -r 90 -- %command% -nosplash
Deleted/moved intro video files (steamapps/common/Deep Rock Galactic/FSD/Content/Movies/DRG_{Loading,LogoIntro}*.mp4) for faster loadup and less potential crash during intro video (unlimited FPS can cause GPU to crash during intro video). Also using -nosplash which is supposedly disabling the intro videos (as well)
If using DX12 renderer, frequent GPU hangs ("amdgpu ring gfx timeout" and/or "failed to initialize parser -125"). Switching to DX11 renderer gets rid of those hangs (stable experience then). If your GPU crashes during intro video, delete videos and/or use -nosplash. Using e.g. gamescope as an FPS limiter is also recommended (also for other games). gamescope can also help with keeping the mouse cursor inside the game window (also for other games).
Should run well out of the box in most cases using default Proton, but if you run into stability issues see my notes
gamescope -h 2160 -b -f -e -r 90 -- %command% -nosplash
Deleted/moved intro video files (steamapps/common/Deep Rock Galactic/FSD/Content/Movies/DRG_{Loading,LogoIntro}*.mp4) for faster loadup and less potential crash during intro video (unlimited FPS can cause GPU to crash during intro video). Also using -nosplash which is supposedly disabling the intro videos (as well)
This is an updated post. DX12 renderer runs stable for me now. If you experience AMD GPU hangs ("amdgpu ring gfx timeout" and/or "failed to initialize parser -125"), one solution might be to switch to DX11 renderer. But first you should try updating your kernel, your drivers and try out different power saving settings for the GPU (these GPU hangs are likely related to that). gamescope can help with keeping the mouse cursor inside the game window (also for other games).
%command% -nosplash
The game is buggy by itself still. Not a problem of Proton/Steam, game is still in early access.
Played with gamepad
Runs fine out of the box. Occasional crashes can occur but these are the game's fault
Not Proton-related, just game-related. The game generally has some random crash potential. Maybe they fixed it with patches already.
Rare/occasional freezes (game restart required)
MANGOHUD=1 MANGOHUD_CONFIG=fps_limit=60 %command%
Just regular edits enabling better mod support and advanced graphics settings, nothing required for running on Linux
Mouse cursor sometimes isn't properly restricted to the game window on multi-monitor setups
gamescope -h 2160 -b -f -e -r 60 -- %command%
Selected the game to run in Vulkan mode (Steam game properties) and edited steamapps/common/Ghost Recon Breakpoint/BattlEye/BELauncher.ini: change 64BitExe setting to: 64BitExe=GEB_vulkan.exe
About Proton Experimental
I'm not sure if Proton Experimental is technically required, I just followed other advice here. Didn't test different Proton variant.
About Multiplayer
Haven't tried it and don't intend to. So not sure if or how well the anti-cheat works on Linux/Proton.
About my commandline
gamescope is not technically required, I just like using it to impose an outside FPS limit upon the game (in this case, 60), set window parameters (in this case, borderless fullscreen window @ 2160p), and to better contain the mouse cursor within the game window. I use gamescope for a lot of games in that way.
About the game in general
If you played this game when it first released, and didn't like it back then, give it a chance again, they really improved this game significantly over time, and added new content and game modes. I recommend playing in Immersive Mode for much more realism, much less hand-holding and much more immersion of course.
Runs great on default Proton, also in multiplayer
Starting multiplayer missions seems a bit slow, but it's probably fault of the game itself
Runs just fine on default Proton
In rare cases, fullscreen might revert or not work. If that happens, just switch from window to fullscreen in the game options (or vice versa). Solves the issue.
Renamed intro video files to skip them
No issues, played 71h so far
gamescope -h 2160 -b -f -e -r 60 -- %command%
Mouse clicks aren't captured by the game window, meaning you can't click anything in the game window and it all behaves as if you'd clicked outside of the game window
Running the game via 'gamescope' is one solution to the "mouse clicks aren't being captured by the game window" problem. I use the commandline gamescope -h 2160 -b -f -e -r 60 -- %command%" and this solves the issue. [Replace -h 2160 with your native vertical resolution, and -r 60 with your desired framerate limit. -b -f means borderless fullscreen, -e means enable steam integrations]
gamescope -h 2160 -b -f -e -r 90 -- %command%
Using gamescope isn't technically required, I just like using it for the extra features
Runs well out of the box with default Proton, just maybe expect some slight performance issues
Performance isn't as good as it should be in some areas. But it's playable overall. (This was with my old GPU, didn't yet try it with the new one)
Standard DXVK resulted in "Unable to map memory" errors in the proton logfile + related frequent crashes of the game. Switching to PROTON_USE_WINED3D seems to prevent the crashes (so far)
very minor performance lags, not important
Using default DXVK: frequent crashes (during loading of new areas or shortly after) that log VK_ERROR_MEMORY_MAP_FAILED. Using WINED3D instead: so far no crashes
Installing dlcs+mods is a little more involved. The ALOT mod installer doesn't run, but you can get it installed by using the MassEffectModder tool, which also has a Linux version. You can then install the ALOT .mem files with that, and convert .tpf texture files to .mem files and install them as well
Game has frequent annoying, but not game-breaking freezes for at least 5 seconds each time, every minute or so. Seems to usually happen when units die, are selected, or upgraded. This also impacts the other players in multiplayer, because the game time doesn't continue to count down during those freezes, so they'll experience a lag or delay as well during that
Frequent freezes can occur, but since it's an autobattler it's not game-breaking. Still annoying.
Runs great out of the box with default Proton. Maybe needs a bit of tweaking to eliminate any small FPS drops.
Slight FPS drops (significant in this fast-paced gameplay)
Runs out of the box with Proton 5.0.9, multiplayer as well
The game has its share of bugs that are unrelated to running it via Proton. For example, various graphical glitches or (in multiplayer) markers being mixed up, getting stuck in walls, and others. They are usually small bugs, but make sure to save often to prevent losing time. Again, these probably don't have to do with Proton because some Windows friends who I play with in multiplayer also have issues like that
Runs fine, but multiplayer didn't work out of the box. Had to use Proton-6.5-GE-1 (Glorious Eggroll fork) and "protontricks 275850 win7"
Proton-6.5-GE-1 GloriousEggroll
protontricks 275850 win7 # to get multiplayer working
Multiplayer didn't work out of the box, needed to use "protontricks 275850 win7" to fix this
Runs perfectly out of the box with default Proton
Played with gamepad
MANGOHUD=1 MANGOHUD_CONFIG=fps_limit=60 %command%
Renamed intro video files (.mp4) to skip intros
Didn't test default Proton
Proton-6.10-GE-1 GloriousEggroll
Proton-6.10-GE-1
Seems to run perfectly with default Proton out of the box (just tried it shortly though so far)
~30min playtime, but so far no issues (4K non-upscaling, non-RT, maxed out other settings)
MANGOHUD=1 MANGOHUD_CONFIG=fps_limit=60 %command%
Didn't test default Proton
gamescope -h 2160 --adaptive-sync -f -e --force-grab-cursor -- env AMD_VULKAN_ICD=RADV MESA_SHADER_CACHE_MAX_SIZE=10G %command%
Unrelated to the game, just in case someone stumbles upon this and is initially puzzlled: I had about 2-3x less FPS than I should have in this game. At first I thought it's the game, with all the talks of it being buggy/unoptimized etc. Then I noticed my system was also way too slow in other demanding titles. Then I noticed that my enforced GPU power profile was set to "low". I don't know what caused that to change, but once I increased it to "high" I immediately had 3x the FPS in this game. You could use e.g. CoreCtrl for this if you want a GUI tool to set it.
Default Proton didn't work (Steam error popup "compatibility tool failed"), but GE-Proton works.
Renamed video files to skip intro videos
Occasional crashes (game window freezes with a black screen) when transitioning to new areas or reloading a checkpoint. Seemed to happen more often with GE-Proton (9.10) than with Proton Experimental (bleeding edge). Could also be a game bug.
I had the best experience using Proton Experimental (bleeding edge). Using MangoHud to impose a 60 FPS limit wasn't a good idea either - it made the game stutter. Other than that, flawless experience and great performance at Epic + FSR3 + 4k.
Runs great with default Proton, but didn't yet play for long
... and no multiplayer tested yet
Maybe needs commandline "PROTON_SET_GAME_DRIVE=1 %command%", otherwise setup might complain about "low disk space". No problems otherwise.
Run with commandline: PROTON_SET_GAME_DRIVE=1 %command%
With default Proton, some audio isn't playing (e.g. character speech). You can fix that by switching to the custom fork Proton GE.
Used this commandline to fix very poor performance: PROTON_NO_FSYNC=1 taskset -c 0,1,2,3 nice gamemoderun WINE_FULLSCREEN_FSR_STRENGTH=5 WINE_FULLSCREEN_FSR=1 DXVK_ASYNC=1 %command%
Very significant performance problems out of the box
AMD_VULKAN_ICD=RADV PROTON_FORCE_LARGE_ADDRESS_AWARE=true WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command%
If the game doesn't recognize all of your GPU's VRAM, use WINEDLLOVERRIDES="amd_ags_x64.dll=b" %command% as launch option (if you don't, you'll see lots of low-res/washed out textures while playing, as a result of the game compensating for the perceived low VRAM). Running it on Ultra settings requires at least 16 GB VRAM. Shader compilation duration during the first start was quite short on my machine (like 1 minute or so). After that, it runs flawlessly. So I'm tempted to say you can ignore all of the negative Windows-based reviews, but maybe it really is badly optimized and it's just my machine compensating for it. Whatever the case, I had a positive experience on my machine with just that little tweak needed. No stutters, instabilities, or anything.
The game crash bug is annoying but can be avoided by switching Proton versions temporarily. Other than that, game runs fine.
PROTON_NO_ESYNC=1 %command%
Used older GE-Proton 7.16 to avoid a game crash bug when interacting with the hanging corpse, but using this version causes graphical video/menu artifacts. Still, you can use this version to progress further in the game, and then you can probably switch back to a more recent version not having the video/menu artifacts.
Very slight performance hiccups, but probably the game's fault, not Proton/Wine/etc.
Sometimes, game won't start (black screen). But this happens infrequently. PROTON_NO_ESYNC=1 maybe helps, but in my case it probably doesn't. Just try again if it happens.
Using a recent version of Proton, Proton Experimental or GE-Proton, the game crashes shortly after interacting with the hanging corpse. So far this crash has been consistent. Using the older GE-Proton 7.16 helped with this, but caused another (smaller) issue with graphical artifacts in videos. Recommendation: use recent proton by default, but temporarily switch to 7.16 or so when you encounter the crash bug. I didn't try other versions, just these.
gamemoderun %command%
Music randomly stops playing for a time, then resumes again, and so on
Graphical effects when mining sometimes glitch out, but that's most likely a bug within the game
Some minor random fps drops
Game is still in EA so some issues reported might be game-related, not Proton-related. Also haven't tried different settings yet. This is just my initial experience.
Used Proton 9.0 (Beta)
Didn't test Proton < 9.0. This is an updated report for the release version 1.x, ignore the old one. The game works fine now without any issues. Didn't test multiplayer/coop yet.
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command% -dx12
Not sure if the customized commandline was technically required in this case, but I used it anyway after reading other comments. No problems with it (didn't test without).
Runs perfectly out of the box with default Proton, but it does crash occasionally.
Crashes occasionally (randomly).
Runs great in single player using Proton GE (didn't test default Proton). Multiplayer probably doesn't work due to anti-cheat (EAC)
Renamed some intro videos to skip them
Tried multiplayer a while ago (older versions, via Lutris). Didn't work back then due to EAC (you'll get kicked by the server). Haven't tried it via Steam/Proton so far, but be cautious
Runs perfectly out of the box with default Proton
Ubisoft recently enabled EAC for Proton users, meaning multiplayer for Linux players should work now since a couple of days. Just make sure the Proton EAC Runtime is installed in Steam (tools) [though that probably happens automatically when installing the game], and I'd recommend running Steam via firejail or a similar sandboxed environment, or under a different limited user account, since EAC might be considered spyware. On Linux, this is less of an issue because it runs in usermode, but still, anti-cheats like this are generally shady software which you want running with as few rights as possible on your system.
%command% -nolegal
If your gamepad isn't recognized, simply disable Steam Input for the game (it's probably enabled by default). You may want to use the commandline parameter "-nolegal" to skip intros.
MANGOHUD=1 MANGOHUD_CONFIG=fps_limit=60 %command% skiplogos
Rare crashes, not a big deal
The commandline uses MangoHud to set a 60 fps limit for the game, which is supposed to reduce the frequency of crashes. Didn't verify myself, just using it because others wrote it.
Game didn't launch with default Proton (you'll see an error popup that some shell script couldn't be run), which is the reason I switched to GE Proton, but I think they fixed it already in the next Proton version
