Compatibility Report

I wanna add new stuff here :
The game works but takes a little bit to start, like 10 o 20 seconds.
Works on Proton 5.13 , but with the latest update of Proton 5.0, it requires Vulkan 1.1 and asks that i have to update my Nvidia Drivers.

I have a Radeon R9 390, and when I start this game up, it's either a completely-black screen, or flickering every other frame - sometimes it's flickering to black, sometimes it's flickering to garbage VRAM data.

I also have issues. First thing is that sometimes when the game starts, the screen is just black. Then at other times, I can see the game but it is flickering. The worst problem is, that when it is not black and not flickering and I can start a game, after a couple of minutes it will freeze, render garbage to one of my other monitors and just crash my X (or wayland).
I have tried several proton and the latest GE versions. All the same. Switching around usually fixes the black screen / flickering, but they all crash my X session after a couple of minutes.

I have tried with disabling vulkan by using PROTON_USE_WINED3D=1, but somehow MangoHud still says its using Vulkan. I then figured the game uses a Vulkan renderer and, according to the discussions in the steam forums, there seems to be issues with the games renderer. So not sure if anything can be done about these crashes within proton.

sysinfo
Proton log

@smirgol Are you still able to reproduce on your Navi?

Unfortunately yes. All the problems mentioned still exist. It either renders a black screen, or it flickers and if it does none of both, which is rare and can only be achieved with switching the prefix back and forth between different versions, it will crash my X when loading a save or after playing for a very few minutes.

Can you attach the output of vulkaninfo?

Here it is:
vulkaninfo.txt

With Proton 6.3-8 it finally seems to run pretty stable for me. No flickering, no crashes.

I'm still seeing the previously described behavior. Main menu flickers, GPU crashes ingame. Have to restart X to get the session going again.

vulkaninfo.txt
steam_sys_info.txt
journalctl.txt
steam-760650.log

Probably the interesting bit:

amdgpu: The CS has been cancelled because the context is lost.
00:08:26.499684|RENDER         | 682:transfer.cpp                   Vulkan 1.1 graphics API system call failed.
Update your video card drivers at:
https://www.nvidia.com/download/index.aspx
or
https://www.amd.com/en/support

( vkQueueSubmit( _transfer_queue, 1, &submit_info, nullptr ) )

Return code: VK_ERROR_DEVICE_LOST
X connection to :99.0 broken (explicit kill or server shutdown).

@brandonegbert Are you still able to reproduce your problem with up-to-date Mesa?

Yes.
steam-760650.log
vulkaninfo.txt
System Info: https://gist.github.com/brandonegbert/9aa15a320b4f62fce21620d4ad8c3ec6

Video Card:
    Driver:  AMD AMD Radeon RX 5700 XT (navi10, LLVM 13.0.1, DRM 3.46, 5.18.0-zen1-1-zen)
    Driver Version:  4.6 (Compatibility Profile) Mesa 22.1.0

I can actually reproduce this easily, there is a TON of Vulkan validation errors which means this is likely a game bug.

Yes, got past the loading screen with that and didn't have any obvious corruption. Only played for a minute so not sure if there would be errors in longer session. I'll try a longer session in the next day or two to confirm.

steam-760650.log

Looks like that's already used as a default for vkd3d as a workaround, any downsides to using it?

Yep, played for a couple hours and it seemed fine the entire time.

No GPU hangs and no flickering now?

Yep, same experience as it was on Windows. No flickering, GPU hangs, or visible artifacting. Performance seemed about as I would expect as well.

I merged this workaround in RADV today https://gitlab.freedesktop.org/mesa/mesa/-/commit/fe9f1d064af05464e5a31c74ea0d063b8c20611d