If possible then try to record a video that shows the issue and attach a Proton/Wine log.

I don't have a log, but here's a video of the problem. It was fixed by e808096d5d9532f31f8b35b44fed263ae6c0502d on game version 1.01.03 and then the issue was introduced again on game version 1.02.00. It appears inside a rectangle in the bottom right and top left of the screen and nowhere else.

OS: Arch Linux x86_64
Kernel: Linux 6.19.11-arch1-1
BIOS (UEFI): 2.A50 (5.41)
Board: MAG B850 TOMAHAWK MAX WIFI (MS-7E62) (2.0)
Init System: systemd 260.1-1-arch
Omarchy: 3.5.0
Omarchy Branch: master
Omarchy Channel: edge
CPU: AMD Ryzen 7 9800X3D (16) @ 5.27 GHz - 48.1°C
GPU 1: AMD Radeon RX 9070 XT (64) @ 2.52 GHz - 46.0°C (995.87 MiB / 15.83 GiB, 6%) [Discrete]
GPU 2: AMD Ryzen 7 9800X3D 8-Core Processor (2) @ 2.20 GHz - 43.0°C (173.77 MiB / 488.15 MiB, 36%) [Integrated]
Memory: 4.56 GiB / 30.40 GiB (15%)
Disk (/): 675.94 GiB / 1.82 TiB (36%) - btrfs
Physical Disk (Samsung SSD 9100 PRO 2TB): 1.82 TiB [SSD, Fixed] - 40.9°C
Display (MAG274QRF-QD): 2560x1440 in 27", 165 Hz [External]
Monitor (MAG274QRF-QD): 2560x1440 px @ 164.835 Hz - 600x340 mm (27.15 inches, 108.18 ppi)
WM: Hyprland 0.54.3 (Wayland)
Vulkan: 1.4.335 - radv [Mesa 26.0.4-arch1.1]
OpenGL: 4.6 (Compatibility Profile) Mesa 26.0.4-arch1.1
OpenCL: clGetPlatformIDs() failed: CL_PLATFORM_NOT_FOUND_KHR
Mesa: mesa 1:26.0.4-1
vulkan-radeon: vulkan-radeon 1:26.0.4-1
libdrm: libdrm 2.4.131-1
linux-firmware: linux-firmware 20260309-1

https://github.com/user-attachments/assets/859ce12a-b1bc-460c-861a-c0ce6681e5af

Try with this build https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/24073166494

That fixes it. For correctness sake I should mention that I built 76c11d2e2b90b0a46dc894508e67e2aaacc2c04d locally and replaced the files bundled in GE-Proton10-34.

Good. Has also been merged in to master now

Try with this build https://github.com/HansKristian-Work/vkd3d-proton/actions/runs/24073166494

Is this straight forward and easy to use? I’m new to Linux/Bazzite and don’t really know where to put this.

The most straight forward way to use this is just to switch to Proton Experimental Bleeding Edge (Beta tab in steam settings for Proton Experimental tool), which already includes these changes.

If it has to be GE proton for HDR or whatever, you replace the d3d12core.dll in $HOME/.local/share/Steam/compatibilitytools.d/GE-Proton10-33/files/lib/wine/vkd3d-proton/x86_64-windows with the one from the posted build.

The most straight forward way to use this is just to switch to Proton Experimental Bleeding Edge (Beta tab in steam settings for Proton Experimental tool), which already includes these changes.

If it has to be GE proton for HDR or whatever, you replace the d3d12core.dll in $HOME/.local/share/Steam/compatibilitytools.d/GE-Proton10-33/files/lib/wine/vkd3d-proton/x86_64-windows with the one from the posted build.

Thank you so much for that explanation! I’ll give it a try later on!

The most straight forward way to use this is just to switch to Proton Experimental Bleeding Edge (Beta tab in steam settings for Proton Experimental tool), which already includes these changes.

If it has to be GE proton for HDR or whatever, you replace the d3d12core.dll in $HOME/.local/share/Steam/compatibilitytools.d/GE-Proton10-33/files/lib/wine/vkd3d-proton/x86_64-windows with the one from the posted build.

Ok so using Proton Experimental did fix the issue I was having, however I can't seem to get FSR 4.1 to show up in the game's graphics settings any longer, it seems it only shows up with Proton GE... I then tried dropping that .dll file but the game would refuse to even launch...

Did you mix up the x86/d3d12core.dll and x64/d3d12core.dll? You need the x64 one.

Did you mix up the x86/d3d12core.dll and x64/d3d12core.dll? You need the x64 one.

I don’t believe so, but I suppose it’s possible. I’ll have to double check.

In any case, I just tinkered with the settings in-game and fully disabled that new graphics option “Displacement Scale” and it seemed to be the root of the problem.

UPDATE: You were right, I used the incorrect .dll haha

All seems to be functioning correctly now, thank you for your help!