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!

[poperigby]

Yep. Same issue. Would a log be helpful?

[shpinog]

Any plans to fix a broken microphone?

[jarrard]

Guess we'll have to keep roll playing as the mute dwarf.

[kisak-valve]

Deep Rock Galactic, can't click on the menu and mouse not captured

Issue transferred from https://github.com/ValveSoftware/Proton/issues/3538. @Linko-3D posted on 2020-02-17T17:46:31:

Compatibility Report

• Name of the game with compatibility issues: Deep Rock Galactic
• Steam AppID of the game: 548430

System Information

• GPU: GTX 1070
• Driver/LLVM version: Nvidia 418.74
• Kernel version:4.19.0-6-amd64
• Proton version: 5.0-2

I confirm:

• [X] that I haven't found an existing compatibility report for this game.
• [X] that I have checked whether there are updates for my system available.

Symptoms

We can't click on the buttons of the menus, I must hover the mouse en press enter on the keyboard. When entering the game the mouse isn't captured so we can't look around and shoot.

Reproduction

You can directly see the bug after starting the game on the menu. You must use Enter key to valide the button your are hovering. Once you enter the game the mouse is still visible like if it was on the menu, so you can't look arround. But you can use the keyboard to walk and jump. The menus that opens in our base for example to equip our character or select a mission aren't clickable too.

[shpinog]

@Linko-3D This happens with me too, when using AwesomeWM. Most likely a bug that manifests itself in many games. My solution is to minimize the game to the panel (minimize the window), then expand it by clicking on the program in the menu. After that, the mouse is captured in DRG and everything works.

[Linko-3D]

It work for me now since I have relaunched the game. It did that after receiving the message that my perks points were reset after an update.

[newAM]

Is there anything I can do to help with the microphone situation? Everything else works great for me.

[Zorrototo]

No.

[poperigby]

I'm having an issue where alt-tabbing doesn't work. I'll press alt-tab and I lose control of the game, but it doesn't switch to my desktop, and when I alt-tab again, I regain control.

[Zorrototo]

This has been an issue on many games and it affects people 'randomly' because of the many possible combination regarding desktop environment and windows manager, driver version an so on.. I guess.

To avoid alt tabbing issues in any proton games I use virtual desktops and send games on the secondary virtual desktop, and switch virtual desktop if needed.

[RarogCmex]

The game is now crashes. How to dump logs?

[RarogCmex]

Ok, here is UE logs from ~/.steam/steam/steamapps/common/Deep Rock Galactic/Engine/Programs/CrashReportClient/Saved/Logs/

[2020.05.25-14.20.45:650][  0]LogStandaloneRenderer: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_88760B59 [88760B59]
[2020.05.25-14.20.45:652][  0]LogStandaloneRenderer: GammaCorrectionCommon.hlsl:6:11: error: syntax error, unexpected NEW_IDENTIFIER
 Result: DXGI_ERROR_88760B59 [88760B59]
[2020.05.25-14.20.45:655][  0]LogStandaloneRenderer: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_88760B59 [88760B59]
[2020.05.25-14.20.45:657][  0]LogStandaloneRenderer: GammaCorrectionCommon.hlsl:6:11: error: syntax error, unexpected NEW_IDENTIFIER
 Result: DXGI_ERROR_88760B59 [88760B59]

From Steam logs error

23133.119:0120:0124:warn:seh:OutputDebugStringA "[2020.05.25-14.20.45:652][  0]LogStandaloneRenderer: GammaCorrectionCommon.hlsl:6:11: error: syntax error, unexpected NEW_IDENTIFIER\n Result: DXGI_ERROR_88760B59 [88760B59]\r\n"
23133.119:0120:0124:trace:seh:raise_exception code=40010006 flags=0 addr=0x7b00fc3e ip=7b00fc3e tid=0124
23133.119:0120:0124:trace:seh:raise_exception  info[0]=00000000000000af
23133.119:0120:0124:trace:seh:raise_exception  info[1]=00000000009bf850
23133.119:0120:0124:trace:seh:raise_exception  rax=00000000005fbfa0 rbx=00000000009bf850 rcx=00000000005fbf80 rdx=0000000000000000

Full logs see here: rarogcmex.zip

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
    Vendor: X.Org (0x1002)
    Device: Radeon RX 560 Series (POLARIS11, DRM 3.36.0, 5.6.14, LLVM 10.0.0) (0x67ff)
    Version: 20.1.0
    Accelerated: yes
    Video memory: 2048MB
    Unified memory: no
    Preferred profile: core (0x1)
    Max core profile version: 4.6
    Max compat profile version: 4.6
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.2
Memory info (GL_ATI_meminfo):
    VBO free memory - total: 1039 MB, largest block: 1039 MB
    VBO free aux. memory - total: 2884 MB, largest block: 2884 MB
    Texture free memory - total: 1039 MB, largest block: 1039 MB
    Texture free aux. memory - total: 2884 MB, largest block: 2884 MB
    Renderbuffer free memory - total: 1039 MB, largest block: 1039 MB
    Renderbuffer free aux. memory - total: 2884 MB, largest block: 2884 MB
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 2048 MB
    Total available memory: 5120 MB
    Currently available dedicated video memory: 1039 MB
OpenGL vendor string: X.Org
OpenGL renderer string: Radeon RX 560 Series (POLARIS11, DRM 3.36.0, 5.6.14, LLVM 10.0.0)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.1.0-rc4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.1.0-rc4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.1.0-rc4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

[RarogCmex]

Ok, I've found the error: the game does NOT compatible with AMDVLK. After switching to RADV it starts

[timshannon]

Anyone have a workaround for the voice chat issue?

[Zorrototo]

No.

[jarrard]

As far as I know, its unfix-able atm. Requires the attention of a developer.

You could directly contact the game dev and see if they can look into it. It's not hard to spin up a linux install and test these things.

If two people got together and made a private server for testing and tried tweaking wine 'things' then maybe someone could be figured out also, inc looking at logs while activating the voice chat function. But that could take well over a day of messing about, and yield no results.

A work around would be to enable steam voice chat? is that still a thing?

[jarrard]

Anyone else get an apparent game freeze when trying to join someones game?

EDIT: Nevermind, I deleted the gamedata folder and reloaded steam and tried again, works now.

[reid-rigo]

@jarrard I've been getting freezes at mission start too - how exactly did you fix it? I see the issue on proton 5.0.9 but not 4.11-13

[jarrard]

Well make sure your proton is in the user .steam path and not on a separate drive somewhere. I did check the file integrity but it found nothing. Perhaps you didn't delete the prefix?

[Zorrototo]

EDIT: Nevermind, I deleted the gamedata folder and reloaded steam and tried again, works now.

This, He's asking what did you exactly do because deleting 'gamedata' doesn't really mean anything, as well as 'reloading steam', everyone can think of different things for both.

[jarrard]

prefix folder that steam creates for this game under its ID number, and reloading steam was mainly just restarting steam, be sure steam is loaded in runtime mode, if that doesn't work you can try native mode but I hear that can cause problems for other games.

[AnasR7]

I use steam-manjaro and use proton 5.13-1 as a result I can't open the game at all. I have tried to switch to native & runtime but it doesn't work at all. Can you guys help me?

My setting and report in protondb :


[RarogCmex]

Try that:

1. Clear protonprefix of the game.
2. Switch to wayland (important, I have 4x fps drop in xorg)
3. Check if Steam Runtime -- Soldier is installed.

[RarogCmex]

I can play that game in KDE wayland session only :)

[AnasR7]

Try that:

1. Clear protonprefix of the game.
2. Switch to wayland (important, I have 4x fps drop in xorg)
3. Check if Steam Runtime -- Soldier is installed.

i think is the proton problem, because when I tried with the proton 5.0-9 and proton 4.13-11 the game it works. Indeed there are still many problems such as with proton 5.0-9 with not having a sound, Proton 4.13-11 cannot switch applications when Alt + Tab.

and I also tried it with other games like Risk of Rain 2 & Temtem with Proton 5.13-1 and it works perfectly.

3. Check if Steam Runtime -- Soldier is installed.

How to check Steam Runtime -- Soldier ? thanks for advice.

[RarogCmex]

@AnasR7 See there https://github.com/ValveSoftware/Proton/issues/4289

[RarogCmex]

Also check https://github.com/ValveSoftware/Proton/issues/4278

[AnasR7]

I can play that game in KDE wayland session only :)

you right about switching to wayland session, and fps is more stable.

thanks for advice.

[Zorrototo]

I'm not running the game under wayland, and I'm using Proton 5.13, on Manjaro KDE with Nvidia 455 drivers, and it works perfectly fine.

[AnasR7]

I'm not running the game under wayland, and I'm using Proton 5.13, on Manjaro KDE with Nvidia 455 drivers, and it works perfectly fine.

maybe is amd problem ?

[Zorrototo]

I'm not really sure. Maybe if you enable the proton log, and if you run steam from terminal you can have relevant error in one of both logs.

[AnasR7]

I'm not really sure. Maybe if you enable the proton log, and if you run steam from terminal you can have relevant error in one of both logs.

I get the same error Failed to load module: /usr/lib/gio/modules/libgvfsdbus.so what that's mean?

[jarrard]

gvfs is (GNOME Virtual file system) , I'm not sure how much of consequence it is.

How to check Steam Runtime -- Soldier ?

Uninstall the normal steam runtime, then install Soldier. Its in your library tools section which is hidden by default.

[lbibass]

I get a crash every time I try to launch the game for the first time.

`Failed to load module: /usr/lib/x86_64-linux-gnu/gio/modules/libgiolibproxy.so pressure-vessel-launch[2719]: Can't connect to peer socket: Could not connect: No such file or directory

Adding process 2699 for game ID 548430 Adding process 2718 for game ID 548430 Adding process 2719 for game ID 548430 Game removed: AppID 548430 "", ProcID 2692 Uploaded AppInterfaceStats to Steam Exiting app 548430 No cached sticky mapping in ActivateActionSet. `

[RarogCmex]

I found the following issue: in X session Proton 5.13 (DXVK) connects to Intel instead of AMD, so performance of game is awful. Workaround: variable DXVK_FILTER_DEVICE_NAME="AMD RADV" in game launch options

And I found the issue:

The changes in proton 5.13 have changed the preferred gpu for dxvk, so the following options should work for games that use dxvk. (Previously, of igpu and dgpu, dgpu was preferred.)
DXVK_FILTER_DEVICE_NAME="GTX 1050" %command%

Also previously, to use dgpu in vulkan games like doom 2016,
I was using options like VK_ICD_FILENAMES="/usr/share/vulkan/icd.d/nvidia_icd.json", but with the steam runtime soldier won't work. (It worked by Editing _v2-entry-point to disable soldier.)

https://github.com/ValveSoftware/Proton/issues/4289#issuecomment-727137300

[thecsapprentice]

I'm reporting an issue I encountered last night with the game crashing involving (so far) the Drilldozer missions. Symptoms include graphics and audio freezing for several seconds (~5-10), then a brief return of audio, then the whole application dies moments later. This happens for me 100% of the time, thus far, at the moment of activating the Drilldozer or when joining a multiplayer game when it's already running. I'm fairly sure this points to something about the graphics (shaders maybe?) of a running Drilldozer being a problem.

I've seen a few bug reports on this exact issue both on reddit and protondb, but no solutions yet. Nor have I seen anyone post a similar bug report here for Proton. Given the severity of the issue (total crash, progression impeding, high repeatability (at least for me)), I thought it would be best to give it some more attention.

I've attached the proton log below, along with some system information. (first time I've reported an issue here, so let me know if I can do more)

Kernel: 4.8.0-2-amd64 GPU: NVIDIA GTX 1070 NVIDIA drivers: 435.21 Proton Versions tried: 4.11-13, 5.0-10

Note: I was unable to successfully launch the game with Proton experimental or Proton 5.13-4. Additionally, if the shader pre-caching option was enabled in steam settings, my success rate of launching the game was very low. When this option was enabled, it regularly hung at the initial launch window. I do not know if this is related to the crashing issue or not, but I thought it was useful to pass along. I can provide separate logs for the Proton experimental and 5.13-4 crashes, if desired. The attached logs are for both 4.11-13 and 5.0-10.

4.11-13_steam-548430.log 5.0-10_steam-548430.log

[jarrard]

NVIDIA drivers: 435.21 Those seem like VERY old drivers, why not try the 450 / 455.xx ones?

Also kernel 4.8 is quite old also, its up to 5.10 now but I don't know if NVIDIA supports it in their driver yet.

[thecsapprentice]

Hmmm, I suppose they are. I generally am pretty slow to move on these kinds of core updates, since it usually comes along with a bunch stability problems completely unrelated to the issue I'm trying to solve by upgrading. But perhaps it's time to bump everything up again. I'll try with the NVIDIA drivers first and see what happens. This might explain why this bug isn't seeing more attention though, if it's related to my older drivers and kernel.

[thecsapprentice]

Okay. I can confirm that upgrading the NVIDIA drivers to 460 has solved my problem. Where between my old 435 and the current 460 drivers it gets fixed, I can't say. But for anyone else experiencing this problem, the current solution I suppose is to not use outdated stuff like I was.

[eth0OS]

I'm running the game in a very good state. But I believe the in-game microphone won't work, does anybody have any success with it? I'm using Pipewire 0.3.21!

[aeikum]

@eth0OS We're hoping to have a fix for the in-game voice chat issue very soon...

[RarogCmex]

@aeikum That would be fine. Good luck with this endeavor!

[Zorrototo]

@eth0OS We're hoping to have a fix for the in-game voice chat issue very soon...

:heart: and that would fix a so long issue! amazing!

[jarrard]

@eth0OS We're hoping to have a fix for the in-game voice chat issue very soon...

That will be interesting to see happen. Really wondering what the real issue is.

[aeikum]

The build which will hopefully fix voice chat in Deep Rock Galactic is live now on the "next" branch of the Proton 5.13 application. If you'd like to try it out, see #4604 . If all goes well, this build will be set live on the default branch in a few days.

(If you're curious, this is the commit which fixed it: https://github.com/ValveSoftware/wine/commit/f19f65ed074b258cca31ac90b6bb46852aad78a1 )

[eth0OS]

The build which will hopefully fix voice chat in Deep Rock Galactic is live now on the "next" branch of the Proton 5.13 application. If you'd like to try it out, see #4604 . If all goes well, this build will be set live on the default branch in a few days.

(If you're curious, this is the commit which fixed it: ValveSoftware/wine@f19f65e )

Great work you all! I've just tested and now my microphone is working flawlessly! Rock and stone!

[Zorrototo]

Nice! It's working! It's working!!!

[aeikum]

Proton 5.13-6 was released, so voice chat should be working now for all 5.13 users.

[Thann]

I works for me! Thanks everyone =]

[YellowOnion]

Vsync seems broken for me, I always get tearing. Not sure if this is game related, or just a proton/ OS issue.