Can you please post a Proton log? Non-zero chance that bugs like these are caused by d3dcompiler shenanigans.
no idea how to play this absolute mess of a game but it seems to work fine on my end.
Tried it on my deck and it seemed to work fine, but I am seeing recent reports of others saying it occurred on protondb and the steam community hub for not only killer7, but no more heroes 1 and 2 as well
Can you please post a Proton log? Non-zero chance that bugs like these are caused by d3dcompiler shenanigans.
here: steam-868520.log
Tried it on my deck and it seemed to work fine, but I am seeing recent reports of others saying it occurred on protondb and the steam community hub for not only killer7, but no more heroes 1 and 2 as well
Got the idea to use wined3d from there, it seems to be only AMD GPUs having this issue
I mean I was testing this on an AMD card, tried mesa-git as well for good measure and still can't reproduce, so :shrug:
Ok so after further investigation it looks like some sort of RADV issue specific to RDNA3/4 since it kinda just works everywhere else. There's some... unconventional use of dual-source blending going on but nothing that's obviously broken on our end.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/14878 I've created an issue for this, I am affected on rdna4 but not when using amdvlk, nor on windows
Closing since this is a confirmed driver issue with a fix available.
proton 10.0x1 2026-02proton experimentalx1 2026-02PROTON_USE_WINED3D=1x1 2026-02PROTON_USE_WINED3D=1 %command%x1 2026-02
When entering a level, the game is tinted blue. Using PROTON_USE_WINED3D=1 %command% in the launch options has this not happen.
dxvk:

wined3d:

Software information
killer7
System information