Thanks for the logs and detailed report!
I have 0fd9:006a Elgato Systems GmbH Game Capture HD60 S+ and it's not enough to make the game crash. I've tried having 1-4 input audio devices enabled. I'm on a slightly newer PipeWire (Server Name: PulseAudio (on PipeWire 0.3.75)).
What the two games have in common is built-in voice chat. I wouldn't be surprised if they were using the same plugin / middleware. On Linux the games don't allow you to select the input device. The selection list is just empty, not even the default device. I think that's an important clue and I'm trying to look into what the game queries and why it might be the case.
The game also calls EnumAudioEndpoints(eCapture) 8 times in short succession which is weird.
Can you share a log of the crash, preferably with Deep Rock Galactic, with PROTON_LOG=+pulse,+mmdevapi,+dsound %command%?
Hi @ivyl, I just came back from the holidays, I did mention that in another issue. Sorry I kept you on hold but I was really far away from the computer :)
I have good news, the issue seems to be solved, I don't know why but it is solved. Here is the log file you wanted:
After you mentioned being on a newer version of pipewire I realized it was some days I hadn't done any update so I just synced with my distro's newest releases.
I updated my kernel from 6.4.3-1 to 6.4.8-1 and this is my Steam Runtime System Information
Hope everything is alright with you, as said I can now enter into the game successfully so something has changed.
Can you share a log of the crash, preferably with Deep Rock Galactic, with
PROTON_LOG=+pulse,+mmdevapi,+dsound %command%?
I think the same crash is happening in Dying Light 2, and Remnant: From the Ashes. Logs are available there.
Assuming it's the same issue, the problem is not resolved in latest Proton Experimental, at least not in Dying Light 2 and Remnant: From the Ashes.
EDIT:
I just tried using pavucontrol to set the configuration of my secondary audio input (BRIO Ultra HD Webcam) to Off and the games all now launch. You appear to be totally right that it's down to having multiple audio input devices.
I don't own DL2 but I can confirm the issue with Remnant and DRG. Both of them tested recently and still yield the same results!
After using pavucontrol to set the secondary (unused) input device configuration to "Off", the games launch using the Proton 8/Experimental default dsound.dll. Tested with both DL2 and Remnant.
@rcbevans Yes, that's the conclusion I came with my previous report too. With Pavucontrol disabling all my audio input sources except the BlueYeti microphone fixed it.
@kisak-valve actually was the one who made me realize first that it's very likely an Unreal plugin bug that handles voice comms shared between games.
@kisak-valve does this count as a successful retest? Or is that something different that's done internally separately?
Hi. The dsound fixes were accepted in Wine's upstream and I've cherry-picked them into Proton. Those should be available on Proton Experimental's bleeding-edge branch (may require Steam restart to pick up the latest update, experimental-bleeding-edge-8.0-55994-20230915 or newer) in ~15 minutes. If this fixes the problem for you feel free to close this issue :-)
The fixes will trickle into the next experimental and later on into 8.0-5.
I have just tested it with all games, this was a complete success and everything works amazingly. I am going to close this ticket now as it's officially resolved.
Thank you everyone, especially thanks to @ivyl and @kisak-valve for helping out a lot in discovering what the problem was and fixing it!
If I can do anything at all in the future to help test things out just ping me and I will gladly help!
Thanks again everyone!
P.s.
As written before this post, the fix will come out officially on Proton 8.0-5, it's also currently temporarily available on the bleeding-edge beta channel of Experimental.
proton 8.0-5x1 2023-09proton experimentalx2 2023-09PROTON_LOG=+pulse,+mmdevapi,+dsoundx2 2023-09dsound.dllx1 2023-09
This issue comes from the realization that many games are connected by this same bug, as discussed on the Deep Rock Galactic issue page and the Remnant: From the ashes one. I would like for others in this issue with a different hardware configuration from mine to test this out and report if they can confirm this bug being reproduced as-well, so we can identify with precision exactly what is causing it.
The current idea is that games made with Unreal 4 or using a specific plugin for voice communications in it are what are causing this issue. If you can test this out with many other games as I did until now we should get a more clear idea!
In this screenshot we can see an example of invalid configuration for playing some specific games on Proton 8:
As you can see here we have the Yeti Stereo Microphone, Trust QHD Webcam and Game Capture HD60 S+ which are all enabled as input devices.
If you want to reproduce this bug you just need to have more than on input device that's enabled and start either of the verified as bugged games, Deep Rock Galactic and Remnant: from the Ashes for now. You can have anything you want other than "Off" into the profile, I used Analog Stereo Input but that's not the only one that I tested it with. You can use even odd profiles, as long as it's not deactivated it will crash the game.
I have made the same exact experiment but this time with many output audio devices, the problem does not exist in that case.
I have tested changing the profile of my only output device to Stereo to remove the 7.1 channel issue but that didn't solve anything either.
Here is a link to the currently most recent comment about it.
You can find under this message the list of my current configuration:
This is what is printed out as a result of lshw -C sound (click on this to see my audio hardware configuration)
This is my Steam Runtime System Information:
https://gist.github.com/Plarpoon/71f189689e369fb75f884ff845760f02
This is my current setup:
Mesa version: Mesa 23.1.3
Driver: AMD Radeon RX 7900 XTX (gfx1100, LLVM 16.0.6, DRM 3.52, 6.4.3-1-default)