Proton: 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 https://github.com/ValveSoftware/Proton/issues/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 https://github.com/ValveSoftware/Proton/issues/943#issuecomment-417854312

[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 :+1:
Updating nvapi fixed the problem with minigun bullets and fps. Used the process in https://github.com/ValveSoftware/Proton/issues/1374#issuecomment-420547987

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.

[kisak-valve]

Deep Rock Galactic doesn't start anymore

Issue transferred from https://github.com/ValveSoftware/Proton/issues/1751.
@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

System Information

• GPU: GTX980ti
• Driver/LLVM version: 396.54
• Kernel version: 4.18.0
• Link to full system information report as Gist: https://gist.github.com/DerBunman/2cc98b29464caf7585d65fddd635908f
• Proton version: 3.16-1

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.

steam-548430.log

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:
https://github.com/ValveSoftware/Proton/issues/284

Reproduction

Start the game with proton 3.16-1 enabled.

[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?

[svenstaro]

I can't start the game on 3.16-6 Beta. It shows as running but nothing happens.

System Information
GPU: 1080Ti
Driver/LLVM version: 415.25
Kernel version: 4.19.10
Proton version: 3.16-6 Beta

[svenstaro]

Actually it _does_ appear to work if I force use of 3.16-6 Beta under Settings -> Steam Play -> Advanced -> Use this tool -> Select 3.16-6 Beta.

It appears that otherwise, this game uses a different tool instead, though I don't know which.

[ghost]

@kisak-valve

Whitelist Request

• Deep Rock Galactic
• 548430

System Information

• GPU: RX 570
• Driver/LLVM version: Mesa 18.3.1 & LLVM 7.0.0
• Distro: Solus
• Link to full system information report as Gist
• Proton version: 3.16-6

I confirm:

• [✔] that pressing the Play button in the Steam client is sufficient.

Issues

• [✔] I haven't experienced any issues.
• [⌛] There are no issues left open for this game. Needs retest from other players...

[kisak-valve]

Is anyone else seeing an issue with this game and Proton 3.16-6 that would block it from being whitelisted?

[jarrard]

Sorry haven't played the game for 6months, I should probably give it another go sometime :)

[h8672]

Just tested using GTX 1060 6GB, nvidia driver 415.25 and proton 3.16-6 beta. After updating proton, deleting game folder 548430 from compatdata the game made the first installation again and started to work well without additional parameters or settings. :+1:

[jarrard]

Fresh install XFCE Antergos and game doesn't launch for me, probably fixable but that isn't the point. If you need to dig into the dirt of it to fix problems then it isn't working.

GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to ProcessingInstallScript with ""
installscript_posix.cpp (355) : Assertion Failed: strCommonRedistForeignInstallPath != ""
installscript_posix.cpp (355) : Assertion Failed: strCommonRedistForeignInstallPath != ""
installscript_posix.cpp (355) : Assertion Failed: strCommonRedistForeignInstallPath != ""
installscript_posix.cpp (355) : Assertion Failed: strCommonRedistForeignInstallPath != ""
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/riddick/.config/openvr/openvrpaths.vrpath'
wine: /mnt/GamesSSD/SteamLibrary/steamapps/compatdata/548430/pfx is not owned by you
GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to SynchronizingCloud with ""
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/riddick/.config/openvr/openvrpaths.vrpath'
wine: /mnt/GamesSSD/SteamLibrary/steamapps/compatdata/548430/pfx is not owned by you
GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to SiteLicenseSeatCheckout with ""
GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to CreatingProcess with ""
GameAction [AppID 548430, ActionID 3] : LaunchApp waiting for user response to CreatingProcess ""
GameAction [AppID 548430, ActionID 3] : LaunchApp continues with user response "CreatingProcess"
Game update: AppID 548430 "", ProcID 29226, IP 0.0.0.0:0
>>> Adding process 29226 for game ID 548430
GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to WaitingGameWindow with ""
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
GameAction [AppID 548430, ActionID 3] : LaunchApp changed task to Completed with ""
>>> Adding process 29227 for game ID 548430
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/riddick/.config/openvr/openvrpaths.vrpath'
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.
wine: /mnt/GamesSSD/SteamLibrary/steamapps/compatdata/548430/pfx is not owned by you
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/riddick/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
wine: /mnt/GamesSSD/SteamLibrary/steamapps/compatdata/548430/pfx is not owned by you
>>> Adding process 29228 for game ID 548430
>>> Adding process 29229 for game ID 548430
Game removed: AppID 548430 "", ProcID 29226 
No cached sticky mapping in ActivateActionSet.

Probably easy fix, but again fresh install, and this shouldn't be happening.

Could be corrupt files also, seems the update is downloaded corrupt so I can't test the game at this time. Not sure the issue.

EDIT: Yeah I forgot to setup my NTFS drives correctly, forgot you need uid=1000,gid=1000,umask=000 problems be had, also big_writes helps a big with performance.

[jarrard]

Seems the game does nothing when you go into the drop ship to do a mission. Just does %0 process and stalls forever? anyone experiencing this?

XFCE Latest Proton beta and Nvidia Vulkan beta drivers.

Uggg, you know what it is, that damn open file limit... Biggest pitfall of steamplay, requiring people to do these adjustments to drive mounts and file limit sizes.

[ghost]

a̶̶m̶̶d̶̶ ̶̶g̶̶r̶̶a̶̶p̶̶h̶̶i̶̶c̶̶s̶̶ ̶̶c̶̶a̶̶r̶̶d̶̶s̶̶ ̶̶h̶̶a̶̶v̶̶e̶̶ ̶̶g̶̶p̶̶u̶̶ ̶̶h̶̶a̶̶n̶̶g̶̶s̶̶ ̶̶w̶̶h̶̶e̶̶n̶̶ ̶̶p̶̶l̶̶a̶̶y̶̶e̶̶r̶̶s̶̶ ̶̶f̶̶i̶̶g̶̶h̶̶t̶̶ ̶̶a̶̶g̶̶a̶̶i̶̶n̶̶s̶̶t̶̶ ̶̶s̶̶u̶̶c̶̶h̶̶ ̶̶o̶̶p̶̶p̶̶o̶̶n̶̶e̶̶n̶̶t̶̶s̶̶.̶

̶f̶̶r̶̶o̶̶m̶̶ ̶̶t̶̶h̶̶e̶̶ ̶̶p̶̶r̶̶o̶̶t̶̶o̶̶n̶̶ ̶̶p̶̶o̶̶i̶̶n̶̶t̶̶ ̶̶o̶̶f̶̶ ̶̶v̶̶i̶̶e̶̶w̶̶,̶̶ ̶̶i̶̶t̶̶ ̶̶r̶̶u̶̶n̶̶s̶̶ ̶̶o̶̶u̶̶t̶̶ ̶̶o̶̶f̶̶ ̶̶t̶̶h̶̶e̶̶ ̶̶b̶̶o̶̶x̶̶ ̶̶b̶̶u̶̶t̶̶ ̶̶t̶̶h̶̶e̶̶ ̶̶m̶̶e̶̶s̶̶a̶̶ ̶̶d̶̶r̶̶i̶̶v̶̶e̶̶r̶̶ ̶̶o̶̶n̶̶f̶̶o̶̶r̶̶ ̶̶a̶̶m̶̶d̶̶ ̶̶g̶̶r̶̶a̶̶p̶̶h̶̶i̶̶c̶̶s̶̶ ̶̶c̶̶a̶̶r̶̶d̶̶s̶̶ ̶̶c̶̶a̶̶u̶̶s̶̶e̶̶s̶̶ ̶̶g̶̶p̶̶u̶̶ ̶̶h̶̶a̶̶n̶̶g̶̶s̶̶ ̶̶s̶̶o̶̶ ̶̶t̶̶h̶̶a̶̶t̶̶ ̶̶t̶̶h̶̶e̶̶ ̶̶w̶̶h̶̶o̶̶l̶̶e̶̶ ̶̶p̶̶c̶̶ ̶̶c̶̶o̶̶m̶̶e̶̶s̶̶ ̶̶t̶̶o̶̶ ̶̶a̶̶ ̶̶s̶̶t̶̶a̶̶n̶̶d̶̶s̶̶t̶̶i̶̶l̶̶l̶̶ ̶̶f̶̶o̶̶r̶̶ ̶̶i̶̶t̶̶ ̶̶t̶̶h̶̶e̶̶r̶̶e̶̶ ̶̶i̶̶s̶̶ ̶̶o̶̶n̶̶e̶̶ ̶̶w̶̶a̶̶l̶̶k̶̶a̶̶r̶̶o̶̶u̶̶n̶̶d̶̶:̶
Edit: Fixed

[megatog615]

Deep Rock Galactic's Update 21 doesn't seem to start. The game doesn't save logs at all, just crash dump files. It shows the splash image(normal), then goes to a black screen(normal) for a time before it crashes.

I'm using AMDVLK to handle Vulkan, though I have tested it with and without launch options just to be certain.

[ghost]

I can confirm it even withouit dxvk the game wont start so its maybe a proton issue.

[megatog615]

The developer updated the engine from Unreal Engine 4.19 to 4.21. Is there a bug report just for Unreal Engine 4? Perhaps some references could be made so we can all work together.

[ghost]

The game works fine in wine 4.0

[ghost]

and works in proton too

[ghost]

@megatog615 if you enter the game just wait..a bit. This is what i did :smiley:

[megatog615]

It should be noted here that the developer put out a hotfix which fixes the problem.
https://steamcommunity.com/games/DeepRockGalactic/announcements/detail/1750114627268690376

I wonder if the crash only occurred on wine and they fixed it just for us?

Hopefully one day they decide to just make a native port, since Unreal Engine 4 can be compiled for Linux.

[ghost]

@kisak-valve you can remove "mesa drivers" this bug got fixed with Mesa 18.3.3

[megatog615]

Unfortunately I think update 21 killed ingame voice chat. I can hear others using it(presumably from Windows) but it does not function for me or my friend(who also plays with Steam Play).

[aport]

Same issue with voice transmit here. PulseAudio is showing the input stream and it responds to audio, but the game does not transmit.

[jarrard]

cant seem to get this working anymore. just shuts down.

Seems the latest proton beta is broken. 3.16-4 appears to work.
Can't even uninstall -8 beta, complains about missing shared content... whatever

[kisak-valve]

Hello @jarrard, please add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[jarrard]

ok,
I had it run once, but now it won't again. I think proton is gutting itself somehow.
Get lots of these

OSError: [Errno 22] Invalid argument: '/' -> '/mnt/GamesSSD/SteamLibrary/steamapps/common/Proton 3.16 Beta/dist/./share/default_pfx/dosdevices/z:'

Think I know whats going on, it might be failing to create the wine sub system... odd, the drives are mounted correctly. AND it works via lutris wine dxvk...

I'll reset steam play, maybe I closed steam before it was finished creating the wine subsystem which can sometimes take a while if its installing loads of stuff.

[jarrard]

it only creates a empty steam log file, nothing to post.

[jarrard]

Ok got it working, what I did was disable steamplay, delete all the compat folders and proton folders and installed proton tools in steam.

Then started steam runtime (native probably works also) and enabled steamplay again with latest proton selected, THEN I had to download redistrubution stuff and THEN manually installed proton 3.16-8 tool (otherwise it would not install it for me), THEN it started installed the directx stuff as it should and the game launched fine...

what a bother... :)

[kisak-valve]

Reviewing recent history of this issue report, the whitelist request is blocked pending evaluation of the voice chat transmission issue.

[jarrard]

Yes I will be testing that out tomorrow sometime. Will let you know, however its sometimes hard to find people who also use voice.

[Rabcor]

I was just playing this game for 4 hours straight, though I didn't actually use the in-game voice chat so I can't say anything about it, but besides that one possible failure point, the game ran perfectly. I installed, played, got 100+fps the entire time, no problems with alt-tabbing either, everything was silky smooth from top to bottom.

[vilnius-leopold]

I also wanted to confirm the issue with the in-game voice chat (I'm on ubuntu 18.04) . I was playing with a friend (he's on windows). I was able to hear him on my end just fine, but he could not hear me.
Apart from that everything seems to work really well.

[jarrard]

I have used voice chat in this game before but that was quite a way back in early access. Been a while.

[megatog615]

It has not worked since the developers upgraded to the latest version of UE4.

[Zorrototo]

Any progress on fixing the non working voice chat? if needed I can provide logs or whatever, just ask.

[aport]

Since Proton 4.11-1, the game will crash when hitting enter key to bring up in-game chat. Proton 4.2-9 works fine

[Zorrototo]

Same here.

[kisak-valve]

Hello @aport, @Zorrototo, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

[Zorrototo]

Here is log after I force close the game which is frozen:
steam-548430.zip

Here is log with previous version of Proton 4.2-9:
steam-548430_proton429.log

I did exactly the same in both instances, I opened game, loaded into game, and pressed the Enter key to bring up text chat. It instantly crashes on proton 4.11

[alasky17]

@aport @Zorrototo @kisak-valve I'm not sure if it is necessary to gather more information at this time. It seems to be the same failure as MORDHAU text boxes described here: #2629

One of the additions to 4.11-2 caused certain things that were previously getting stuck and working by default to now get farther and then fail with a new unimplemented feature. This regression seems to mainly have affected text boxes in games with new steamclient apis. We hope to fix this very soon.

[Zorrototo]

by the way, the intro video do not play at all since forever, not sure it is a known issue.

[MrJakob99]

Hey, I was upgrading my Ubuntu from 16.04 to 18.04 and afterwards Deep Rock (I played it 81 hours before) wouldn't work properly any more. At first I could go into the hunger and select a mission, but after starting the mission I got a blackscreen freeze.
The strange this is, that once the game was in the update queue. I started it (there wasn't really an update downloaded) and I was able to play again. I did on mission with a friend (Windows), we failed and than we both got stuck at the mission lost screen, but sound and animations were still normal, so no real crash. We both force closed it.
After that the game won't start again. Non of the proton versions that steam has to offer work for me.
(the exact same thing happened with Mordhau -> didn't work -> update queue -> crash -> not starting anymore ... and as far as I know from this threat, both games have something like the same issue, is that right?)

[jarrard]

The upgrade probably reset some of your settings such as max open files etc..

[MrJakob99]

Here is my log:

steam-548430.log

[MrJakob99]

The upgrade probably reset some of your settings such as max open files etc..

Can I do something about it ?

[kisak-valve]

Hello @MrJakob99, err:winediag:FILE_CreateFile Too many open files, ulimit -n probably needs to be increased and eventfd: Too many open files are the lines of interest in your log. There's some documentation at https://github.com/zfigura/wine/blob/esync/README.esync that should help.

[MrJakob99]

Thanks for the help, I will be looking into this deeper tomorrow.

[aeikum]

The in-game chat regression should be fixed in Proton 4.11-3. Please retest.

[Zorrototo]

Indeed it seems to be fixed.

Still remaining issues:

• no intro video playing, just black screen
• no voice chat

[MrJakob99]

Thanks for the help, both games are working perfectly fine now.
I also can say that the chat box bug is fixed

[jarrard]

voice chat use to work. so odd

[Zorrototo]

It never worked for me.

[jarrard]

It never worked for me.

I think last time I tried it was back in proton 3.7 days, quite far back now. Maybe it still works for me, but I can't test it atm due to no GPU.

[thratkin]

I get this weird graphical glitch sometimes. It only seems to appear when you look in direction between west and south. I mostly have it on eliminations, though there was one during a mining expedition too. I don't know if this is a Proton-specific bug or not.

I'm on GTX 1050 with the latest driver (430.40-5).

[jarrard]

reminds me of when nvidia switched to the new compiler, this sort of thing happened until it was fixed..

[ghost]

@NheelYolis You can see if its a proton bug if you try the game over lutris (without tkg-protonified)

[thratkin]

The problem is, this bug isn't easy to reproduce. It appears randomly in certain (unknown to me) rare circumstances. In gaps between 20-30 missions or so. I'll try to reproduce, but I don't play the game too often. I use PROTON_LOG=1 now, so if it pops up again, at least I can provide some logs.

I'm not even sure if it exists in Proton 4.11-3 at all, I was playing the game with 4.2-9 until the text input was just recently fixed.

[jarrard]

Does it happen on specific missions near specific objects like reflective crystals etc..

[thratkin]

Does it happen on specific missions near specific objects like reflective crystals etc..

Like I said, I mostly had it on eliminations. And it only seems to appear when you look in direction between south and west. If you look at the second screenshot, you can see a glitched selection (which probably was a Glyphid Brood Nexus).

[jarrard]

Yeah probably compiler flipping out. Not sure if you can switch to the older compiler any more but might be worth a test. Also you could try turning graphics details off or to low.

[thratkin]

Also you could try turning graphics details off or to low

I'll try to do that next time I encounter this bug.

[d10sfan]

I'm having issues with this game, where when I click the continue button in the newsletter screen, the game will show a black screen and then crash. I've been able to play plenty of other proton and native games.

steam-548430.log

[jarrard]

Just played a game then, will confirm MIC does not work. Other then that it ran pretty good at 4k with high settings.

MIC works under windows. Also windows gives %36 better framerate, I wonder if its possible to improve this sometime down the line for Unreal 4 engine games (which this game is).

[rodrigoale]

Good Afternoon, i've bought this game yesterday but i can't run this game with proton. I've tested proton 3.7, 3.16 and 4.11. I open the game and load the title screen but it freezes my system.

Here is the log running with proton 4.11

steam-548430.log

[thratkin]

@rodrigoale I open the game and load the title screen but it freezes my system.

If it freezes your system, it probably has to do something with video card drivers. Check journalctl for any errors. If you use NVIDIA, try the Vulkan beta driver (it is available in AUR if you use an Arch-based distro).

You could try to record an apitrace and share DXVK logs to provide more info.

[rodrigoale]

@rodrigoale I open the game and load the title screen but it freezes my system.

If it freezes your system, it probably has to do something with video card drivers. Check journalctl for any errors. If you use NVIDIA, try the Vulkan beta driver (it is available in AUR if you use an Arch-based distro).

You could try to record an apitrace and share DXVK logs to provide more info.

my videocard is intel hd620 (notebook). i run perfectly with windows 10 but unfortunately it crashes with linux. I will try to logthe apitrace and share it. thnx

[jarrard]

You may want to try the Intel Gallium3D drivers, the latest version as I hear their quite good.

There is not much experience here with getting these games working on Intel iGPU's because performance of those chips are often quite low and not desirable.
BUT I hear the Gallium3D drivers perform better then under Windows intel drivers.

I would search up howto get them installed for your iGPU and distro.

Here is a recent article about it.
https://www.phoronix.com/scan.php?page=article&item=mesa193-iris-september

[rodrigoale]

You may want to try the Intel Gallium3D drivers, the latest version as I hear their quite good.

There is not much experience here with getting these games working on Intel iGPU's because performance of those chips are often quite low and not desirable.
BUT I hear the Gallium3D drivers perform better then under Windows intel drivers.

I would search up howto get them installed for your iGPU and distro.

Here is a recent article about it.
https://www.phoronix.com/scan.php?page=article&item=mesa193-iris-september

I fix the problem using the launch option PROTON_USE_WINED3D=1 %command%

The game is running without problem now but i will check the link you send me. Thanks for your help.

[jarrard]

PROTON_USE_WINED3D=1, this bypasses DXVK so you may not get the best performance in this configuration.

It would be worth trying to get a log with DXVK enabled, chances are your desktop isn't 100% crashed and might be recoverable by switching terminal ie. Alt-F2, or doing a tty login via your mobile or laptop to kill the xorg desktop process /restart it.

Also try running the game in a smaller window mode so you can still see the desktop.

[Zorrototo]

Any news on having the microphone to work in this game soon? The game relies on cooperation and not being able to communicate is really annoying in this game. Would be glad to provide any needed relevant information @kisak-valve just tell me.

[jarrard]

It is a tad annoying, the game doesn't have a mic active indicator to make things worse.

[Zorrototo]

I see the mic icon for people on Windows speaking in game, are you talking about a bug in Proton or something else?

[jarrard]

You won't see a mic icon for YOURSELF, the game does not have one.

[Zorrototo]

OK yes but that is not a proton issue.

[jarrard]

Yes, but it does make it very hard to test this sort of issue since many people will not even respond even if it did work. You need to actually type in chat, get them to say I CANT HEAR YOU in order to verify it does not work.

[Zorrototo]

You can have the intro video to play if you apply this fix <Link removed by moderator> Point to the game prefix as explained in the read me.

[jarrard]

Yes that is also needed for games like The Outer Worlds. I think there is some legal issues with MF which is why wine/dxvk/proton does not install it for you, even tho MANY games require it for ingame media playback. Real pickle!

[kisak-valve]

Hello @Zorrototo, the workaround you suggested is legally problematic and has been removed.

[Zorrototo]

Ho OK. I didn't know.

[Adam-Cass]

I'm not sure if I should open a new issue or not but I've found a problem with Deep Rock Galactic and the latest version of Proton. When running the game with Proton 4.11-10 after about 20 minutes the mouse will bug out such that looking around becomes very jittery and stuttery. Restarting the game temporarily fixes the issue. I'm guessing this is related to the changes in mouse handling that came out in the latest patch. Forcing Steam to use Proton 4.2-9 fixes the issue.

[kisak-valve]

Hello @Adam-Cass, this is the right place to discuss issues with Deep Rock Galactic running on Proton. Also sounds like you've encountered #3316.

[jarrard]

Yeah the mouse issue is a new bug that affects several games from what I've read.

[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.

[rigoleto]

@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.

1. 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:

```I think there are two issues with proton 5.13 and steam runtime soldier.

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