The sound=pulseaudio is not doing anything for me. Just waiting for characters to stop talking does. However this won't work for the code scene, as you can't wait them to stop. I also suspected the sound, but didn't come up with the idea to just wait. :)
(Dunno about EQ, which one do you mean? The game one was disabled here already and still crashes)
Yeah, the only way to play now is to get through with the old vkd3d and then swap and wait for the dialogs to finish. But I think the crash is with xaudio, I might have another go to find the exact issue on the weekend, although I'm less motivated now 😅
Just for info, as I posted elsewhere - some of Marvel's GotG crashes do seem connected to fonts/font rendering - disabling subtitles completely seems to fix the crashes when opening the donut logs while someone is talking.
I disabled sound completely and (sound=disabled) there's no xaudio or alsa or pulse being loaded but the crash still happens
The crash seems to have something to do with this https://github.com/vaslabs/vkd3d-proton/commit/a494e323bfad4a8164bf75e1254df6e9b858889d
It's passing at least from the Nova console at the start, if anyone is looking for a workaround to play the game (I don't promise anything, this was trial and error) you can give this https://github.com/vaslabs/vkd3d-proton/actions/runs/1539486080 a go
Edit: I'm on chapter 10, no crashes
Edit 2: finished the game without crashes, rarely got some weird artifacts on snow
@vaslabs Nice! This fixed the Nova console crash for me :) (with AMD RX 570)
What's the deal with nvidia cards here? Still crashing and using latest proton-GE 7-10 which appears to have the PR mentioned above in.
Is the crash with nvidia cards a different issue to this one?
I've created a few builds, this seems to be some invalid access call activated with the recent change for dsv and dynamic dsv
I'm interested to debug more, currently I can't get any useful information (at least to my eye) from proton log (https://github.com/ValveSoftware/Proton/issues/5250#issuecomment-982144924)
I'm also interested to investigate this issue myself as well, just need a few pointers on how to see where the invalid access happens.
I'll have more time to work on it on the weekend, my builds are here, thanks for making it easy to build !
Edit: I'm very rookie with these things but the issue from the wine backtrace points into the xaudio dll
reopen if this is wrong, I'm closing it here
I can confirm it's the sounddoing sound=pulseaudio via winetricks solves the issue for me
Edit: waiting for the dialogs to finish also helps the issue
Edit 2: I was wrong about the sounds, it didn't crash because it happened that I waited for the dialogs to stop