Deep Rock Galactic (548430)

[jarrard]

Updated Info: This game runs quite well for most, however it still suffers from a %36 performance tax compared to Windows which gives 75fps under 4k while Linux only provides 55fps. To resolve this (assuming you have less then 60fps) you may need to run at a slightly lower resolution such as 1800p.

The game can also experience performance drops in certain areas of hectic combat and explosions which affect proton more then windows in comparison. At present MIC or voice chat may not work for you which hopefully is resolved in the future_. (there is no voice chat indicator for yourself ingame, you must ask other players if it works)_

My Configuration: 4k (1800p ingame) with a second 1080p monitor on the side for reference.

System Information: Pop_OS Specs.txt

No special configurations have been attempted at this stage except for setting permissions correctly to my userid and groupid on the NTFS drive this game is installed on. Also ensuring Proton is installed correctly into the .steam folder (don't try and run it via ntfs), and compatdata is symlinked also correctly (refer to documentation).

NOTE: Some users are having issues getting this running correctly, this could be due to incorrect or corrupt proton install, I've encountered this many times myself, its a very easy trap to fall into!

[jarrard]

Some terminal error readouts from this game, no special debug flags used.

Created OPUS PLC voice encoder
warning: The VAD has been replaced by a hack pending a complete rewrite
AL lib: (WW) GetSymbol: Failed to load jack_error_callback: /home/theriddick/.local/share/Steam/ubuntu12_32/steam-runtime/pinned_libs_64/libjack.so.0: undefined symbol: jack_error_callback
AL lib: (WW) jack_msg_handler: Cannot connect to server socket err = No such file or directory
AL lib: (WW) jack_msg_handler: Cannot connect to server socket
AL lib: (WW) jack_msg_handler: jack server is not running or cannot be started
AL lib: (WW) ALCjackBackendFactory_init: jack_client_open() failed, 0x11
AL lib: (WW) alc_initconfig: Failed to initialize backend "jack"

Not sure if this jack thing is the cause of the slow down but could be responsible for the audio stutters.

[jarrard]

Problem is not related to JACK. I've read reports of it working for people on 1060 cards so not exactly sure what the problem is.

[jarrard]

Tested this with DXVK 0.71 and the issue is even worse there. So it looks like the developer might have updated the game and in the process caused something to break. I'll look into getting this looked at again sometime in the future.

Feel free to provide your own data on the issue, I do know SOME people are not having any issues and that could be due to using a older version of dxvk, something I will need to test.

[h8672]

To me settings didn't work until restart, nothing worked with audio volumes. had to go to the sound settings and lower the volume of the game separately. (So I dont really listen to it as it was so loud...)
I have had problems in shooting with minigun where some bullets wont even spawn and the ammunition is running out a lot faster than when using windows.
The best performance I've gotten is using lowest settings and resolution scale 100%, still lags but I can play it.

[jarrard]

under dxvk I get below 5fps (often 2) and with proton via wine it seems to pulse between 2fps and 60fps depending on where I'm looking. Quite odd.. I have done quite a bit of testing and can't seem to figure anything out..

[lieff]

Seems UE4 game, disable nvapi or fake AMD card can help #165 .

[jarrard]

Yes perhaps just disabling it via lutris no longer works, however I don't think I can edit any source to fix the issue? I'll look into it more.

EDIT: Nothing seems to help with my issue here, perhaps I'm doing something wrong. Steam info still claims my card is a nvidia 1080ti even thought I try and trick it into thinking its amd with those variables.. odd.

Seems I need to use the per game config file now.. sigh

[jarrard]

Update:

Ok faking AMD card seems to have worked (via conf file) even thought it was not fooling steam, the game launched via steam does appear to work without the horrid slowdown now, so yay :)

For proton you can use following command:

DXVK_CONFIG_FILE=/path/to/dxvk.conf %command%

You can use the example given on https://github.com/doitsujin/dxvk/wiki/Configuration

UPDATE: Some further testing is required, still sound issue remains and it seems possible missions don't work. This is a odd one!

[lieff]

For audio try this workaround #943 (comment)

[jarrard]

The game fails to load into missions, often zombies the process. Damn, so close yet so far :(

As for AUDIO fix, yes that did appear to allow me to change volume and get audio controls to work however it did make it worse as it now crashes and has more crackling then before. Perhaps more is needed to resolve that.

[jarrard]

To fix audio fully you need to install xact. The exact command I used without edits, as example ONLY (one whole line)

env WINEPREFIX="/mnt/GamesSSD/SteamLibrary/steamapps/compatdata/548430/pfx" WINEPATH="/mnt/GamesSSD/SteamLibrary/steamapps/common/Proton 3.7 Beta/dist/bin" winetricks xact

Game still goes to black screen when trying to launch down into a mission, hangar works fine now... baby steps it seems. It's possible it doesn't like something about the vendor override,...

I can confirm game runs better with AMD vendor override for NVIDIA users, and that the mission load sequence black screens (process freeze) regardless of vendor settings.
(I tried just nvapi64 disabling, still black screen on mission load and it had lower fps)

[jarrard]

Update:

Game works fine via Lutris and DXVK 0.71 with the AMD override, the missions launch. Not sure whats going on with proton but there ya go. Maybe disabling esync will resolve the issue.

Yep was esync.

[jarrard]

So you need the following to get this game working decently.

• AMD override via dxvk custom config file (if you have NVIDIA card), this will give you a nice performance boost over just disabling nvapi alone!
• xact via winetricks to have proper sound emulation and possibly PULSE_LATENCY_MSEC=60 or other tweaks to remove sound distortion (can also try killall pulseaudio before launching game).
• Increase open files limit so ESYNC can work...

[lieff]

@jarrard What ulimit -aH says on your system? Esync usually do not works because of low open files limit.

[jarrard]

core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 63277
max locked memory (kbytes, -l) 1024
max memory size (kbytes, -m) unlimited
open files (-n) 4096
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) unlimited
cpu time (seconds, -t) unlimited
max user processes (-u) 63277
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited

[lieff]

open files (-n) 4096

Too low, needs to raise. It's described in doc https://github.com/zfigura/wine/blob/esync/README.esync

[jarrard]

Ok I made the edits and will give that a shot.

Yep that fixed it. Cheers,

[h8672]

I have increased open file limit to 65535.
I installed xact before, didn't notice change in performance. Thanks @jarrard for the script 👍
Updating nvapi fixed the problem with minigun bullets and fps. Used the process in #1374 (comment)

My audio codec didn't like pulseaudio module-suspend-on-idle so I disabled it and enabled module-echo-cancel in /etc/pulse/default.pa. It caused frequent freezes when I had mic switch on when playing windowed CS:GO)

Currently I have small frame freezes once in a while in Deep Rock Space, but not as frequent as before. I play Deep Rock Space on windowed mode and max settings.
I disabled ESYNC from proton, I think it helped a little with the freezes, don't really look at it now.
Do you think changing that PULSE_LATENCY_MSEC=60? Where do I add it?

[jarrard]

PULSE_LATENCY_MSEC=60 %command% should work with steam. It may not help, there are pulseaudio configuration files you can tweak timings and such with also.

[DerBunman]

@DerBunman posted on 2018-10-15T17:48:40:

Compatibility Report

* Name of the game with compatibility issues: Deep Rock Galactic

* Steam AppID of the game: 548430

Symptoms

The game wont start since updating to 3.16-1.

It only displays the (non fullscreen) splash screen, after that the screen goes black and the game crashes back to desktop.

The game worked fine with 3.7-8 after installing xact and raising ulimits as described here:
#284

Using proton 3.16-3 the game works fine again.

[alasky17]

The audio issues are fixed with 3.16-5 Beta. Are there any other remaining issues with this title?

[Plarpoon]

@Plarpoon Thank you again for transferring the issue here :) Just to clarify - where exactly are you getting the crash; it sounds like it is after clicking "continue" to load into the character selection hallway, while you are loading into the hallway (before you finish loading in) -- is that accurate?

Also - could you please try getting a log with the following in launch options: WINEDLLOVERRIDES="vcruntime140=b;msvcp140=b;concrt140=b" PROTON_LOG="+vulkan" %command%

For starters don't thank me, I am the one that is very grateful and thanks you instead. It's only thanks to people like you that I could finally ditch Windows months ago and moved entirely to a pure Linux setup. I can now enjoy my freedom but also get to play video-games! Thanks enormously for that!

Having said that, you are absolutely correct, as soon as you boot the game you get first a splash-screen with art, you click on it, then you have a screen with a button "continue" at the bottom right (click here to see the picture). I can see that, I can press that button. It's just that once pressed it will die mid loading-screen and the loading screen itself is extremely long. Which is odd considering that with proton 7.0 it's less than a second long.

Here is the requested log:
steam-548430.zip

Let me know if I can do more to be useful in any way, I would be glad doing so!

P.s.
I had to stop the process manually after it crashed again, informing in case that disturbs the logs.

[alasky17]

@Plarpoon While you are testing Remnant: From the Ashes, could you also see if disabling those same 2 pieces of hardware (Trust QHD Webcam and Game Capture HD60S+) also fixes this failure? Then we can just focus on one title :)

[Plarpoon]

I will as soon as I can boot the PC, will report more ASAP :)

[s0lst1ce]

I am having similar issues with video memory allocation failures even though I clearly have a lot left on my GPU (gtx1080). Closing more applications does help (ex: firefox) but isn't a surefire workaround either. I'm using proton experimental and am otherwise equipped with 16GB of RAM, an i7-8700k and two monitors (if that matters). I can provide additional information if need be.

[shadow7483147]

Spun up a fresh install of Kubuntu on my HP Power Pavilion laptop.
Set up Steam to use Proton Experimental, installed and tried playing the game.
It seems to cause the system to soft shutdown (On screen: Broadcast: system is now shutting down!) within a few seconds after loading onto the title screen.

Proton 8 works with seemingly no issues. Can't really test for perf when you're on a 150W laptop, ha.

[cwylie08]

Replying to #284 (comment)

@kisak-valve From what I can tell this has been merged in the wine project. Is there any way to be able to tell if the proton project is tracking a version of wine that incorporates it? I have been digging in github without much luck.

[kisak-valve]

You can go to https://github.com/ValveSoftware/Proton, select a release branch, then scroll down to the git submodule you're interested in. For example, Proton 8.0-3 (https://github.com/ValveSoftware/Proton/tree/proton_8.0) currently bundles vkd3d @ 28c93a4.

[SortaUnknown]

Having a strange problem where the game will seemingly randomly crash or freeze on random missions at any point, while others are perfectly fine. Playing on an AMD Debian 12 computer, on Proton 8, and using DX12. fsync and esync were disabled as that seems to have reduced the amount of crashing
steam-548430.log

[denharad]

I'm experiencing a rapid memory leak from FSD-Win64-Shipping.exe (close to 5GB consumed a second) when starting DRG with DX11 under Steam Play Proton. Running with DX 12 is not affected. The leak starts after "press any key to continue", otherwise idling at the start screen only consumes about 1.4GB.

I've tried:
Verifying all game files, updating the operating system
Switching Proton to experimental no change, then version 7 which still leaks but does not progress from "initializing".
Removed the related compatdata & shadercache folders to force generation of new copies.

After waiting a couple weeks to see if it would be resolved with an update, the symptoms are still easily reproducible on build 11911576.
System config:
Archlinux - KDE Wayland session running Steam Native
AMD 5950x, AMD RX 6800 XT, 64GB RAM

[notpeelz]

Replying to #284 (comment)

Same issue. The game hangs on the "Initializing..." screen on both DX11 and DX12. Memory leak only happens with DX11.

distro: Arch
kernel: 6.4.12-arch1-1
steam: version 1690583737 (tested both native and flatpak)
proton: 8.0-3
cpu: AMD 3900X
gpu: AMD Radeon RX 6900 XT

I've only noticed this issue today. I played DRG with no issues last week.
MangoHud and obs-vkcapture also both stopped working for all my Steam games.

[P-zee]

Same thing here.
At first glance I'm guessing it has something to do with the Arch Mesa drivers for RX 6800/6900. Maybe share Mesa version as well?

Distro: Arch
Kernel: 6.4.12-arch1-1
Mesa: "1:23.1.6-4"
GPU: Radeon RX 6800
CPU: Ryzen 5800X3D
Proton: Experimental, 8.0-3
Steam version: 1690583737
Game build ID: 11911576

[mbriar]

It's a know issue in mesa 23.1.6, it will be fixed in 23.1.7.

[notpeelz]

Do you have a link to the issue tracking this? (or commit/pr)

[mbriar]

@notpeelz https://gitlab.freedesktop.org/mesa/mesa/-/issues/9717

[shadow7483147]

Hey guys, if you're getting SW CTF shutdowns try underclocking your memory.
CoreCtl will let you choose p-states for your core and memory clocks.
Running comfortably at 76-82'C 60FPS on p-state 1 for both clocks (~650MHz for both), where previously the automatic setting would hammer mclock at p-state 2 (1500MHz for my chipset) and cause the chip to sit at 90'C with only 300MHz on the gpu clock.

Tested on Proton 8, will try switching to proton experimental to check.

And we are solid! No loadscreen instant shutdown, temps are the same as Proton 8.

[1player]

Game does not even start on Proton 9 beta. 5 seconds after pressing PLAY in the library, it crashes. Not even a window appears.

Forcing the use of Proton 8 fixes it.

[Managor]

Works fine for me when using Porton 9 and Proton experimental with an AMD card.

[Zorrototo]

Make sure to do clean prefix when switching Proton version if you have an issue. Especially on a BETA Proton.

[Riven-Spell]

I'm getting regular crashes within about 10 minutes of gameplay on Linux; but the game runs fine on Windows. Crashes on Linux don't seem to output a useful crashlog, and it seems like PROTON_LOG=1 is getting flooded pretty hard.

I've tried disabling Fsync/Esync, I've tried using Proton versions from 6.0-9.0, I've tried using only DX11, tried using safe mode, tried clearing the compatdata, hiding the nvidia GPU, etc. and found no avail.

Seems to run longer before crashing on older proton versions, but that isn't a great fix, because I'd like to use HDR, and newer Proton versions run the game significantly better.

I'm ideally looking for some pointers on troubleshooting this, since I feel like I'm at a dead end.

EDIT: The culprit was gamescope. That's a shame. I wanted to use HDR. Going to test some things and then I'll report an issue over there.

[pquerner]

I've recently purchased the game and running it on this system:

  ./o.                  paco@candybox 
                   ./sssso-                ------------- 
                 `:osssssss+-              OS: EndeavourOS Linux x86_64 
               `:+sssssssssso/.            Host: MS-7D31 1.0 
             `-/ossssssssssssso/.          Kernel: 6.6.60-1-lts 
           `-/+sssssssssssssssso+:`        Uptime: 1 hour, 41 mins 
         `-:/+sssssssssssssssssso+/.       Packages: 1512 (pacman), 37 (flatpak) 
       `.://osssssssssssssssssssso++-      Shell: bash 5.2.37 
      .://+ssssssssssssssssssssssso++:     Resolution: 2560x1440 
    .:///ossssssssssssssssssssssssso++:    DE: Plasma 6.2.3 
  `:////ssssssssssssssssssssssssssso+++.   WM: kwin 
`-////+ssssssssssssssssssssssssssso++++-   Theme: Breeze-Dark [GTK2], Breeze [GTK3] 
 `..-+oosssssssssssssssssssssssso+++++/`   Icons: breeze-dark [GTK2/3] 
   ./++++++++++++++++++++++++++++++/:.     Terminal: konsole 
  `:::::::::::::::::::::::::------``       CPU: 12th Gen Intel i7-12700K (20) @ 4.900GHz 
                                           GPU: NVIDIA GeForce RTX 3080 Lite Hash Rate 
                                           Memory: 8014MiB / 64087MiB

While the first few minutes are fine on this game, suddenly the game becomes extremely angry with fps when I move my mouse. The game can run up to 120fps smoothly and then (after a while, maybe its visible in the logs) any mouse movement makes the game dip fps to 60-70. If I dont touch my mouse the game is 120fps again.

Command to start the game: PROTON_LOG=1 DXVK_FRAME_RATE=144 mangohud %command% (PROTON_LOG only to have the log file, normally not)

Log:
steam-548430.zip

The log file should show a game session where I quit the game after a while due to the issues and then restarting it, reconnecting to a running game session (the issue can happen mid-mission and it will be hard to play that way).
After playing for a while then (which ran just fine) the issue started again and continued to happen until I quit the game.
The youtube video shows how the game ran after the mission was completed with this issue (in the final few minutes), and the loading screen to the "hub ship" happened. (So no loading screen fixes the issue)

This was running on Wayland (to see if it makes a difference), but I had the same on X11. The 120fps cap is enabled from the games setting, but it also happens when set to unlimited fps.
I did not specify any Proton version for the game in steam.
A video of the issue here: https://youtu.be/pkuaqmUweGk

[Zorrototo]

There is a long lasting issue in WINE/Proton with mouse with a high polling rate. Try to reduce the polling rate of the mouse to 250Hz instead of probably currently around 1000Hz. I did this with a kernel setting myself to eliminate this random issue before, but with my new mouse I set the polling rate from the official Logitech tool on Windows and save inside the mouse memory to keep the set polling rate (and there are Linux tools which can also do that depending on the mouse model).

You can look at the Arch WIKI for the tool to check your current polling rate, then you can find a way working for you to set a low polling rate. It could be a kernel parameter, or a dedicated tool for the mouse, or other method. Try with 250Hz polling rate to confirm this is the issue you have. Or try an old low quality mouse (check its polling rate to confirm it is by default 250Hz or lower) and see if you also have the issue with it.

What mouse model is it?

[pquerner]

Thanks for explaining @Zorrototo

I have the Roccat Kone AIMO mouse. I havent had a look yet whats the polling rate. Its just wierd that in the video clip in the end I just used the arrow keys to strafe left/right and have the same behaviour (fps drops).
I didnt touch the mouse at all there (not saying that the mouse didnt receive "vibrating" information or something, because I didnt unplug the mouse or hold it up in the air)

[Zorrototo]

For the issue I'm talking about, unplugging the mouse should solve the issue for a test. It is literally receiving some kind of input from the mouse that drops the FPS to hell.

[simifor]

@pquerner I couldn't reproduce your issue, but the symptoms you describe has been noted by other users in other games, if your issue has the same root cause, then adding LD_PRELOAD="" to the start of the game's launch parameter might avoid the issue while it gets sorted out.

@Zorrototo there was no performance difference on my side when using a 1000hz mouse, it's possible that there are other factors required for the performance issue to occur when using one

[pquerner]

@simifor Yes, I can confirm your fix helps. I just played 1,5hours without issues.
I let the log file running just in case something different is showing:

steam-548430.zip
This logfile should show a complete gameplay session (~1,5h) without any trouble or restarts.

[Zorrototo]

@simifor

@Zorrototo there was no performance difference on my side when using a 1000hz mouse, it's possible that there are other factors required for the performance issue to occur when using one

Using a 1000Hz mouse doesn't create the issue, using a 250Hz mouse fixes the issues if it occurs. You can have no issues at all with a 1000Hz mouse for a long period, the issue may just occur randomly and only fix is to restart the game, or unplug the mouse and switch to one with lower polling rate (or preventive measure is to simply fix forever the mouse polling rate so the issue does not occur at all sporadically). In @pquerner case it has been established it was not the mouse as unplugging it didn't help at all.