Thanks for looking at it! You know, that's what I thought, but I figured I didn't understand proton well enough to be sure. I was just following Steam's support instructions. I guess I'm dead in the water. Their support wasn't able to fix it, either.

Bug that prevents me from progressing in the game.
On the other side there should be a bucket where you can attach the rope.
I don't know what to do to fix this.

The game works well using DX11, but when you use DX12 hair and wet surfaces tend to render as a "glowing white" texture instead of the proper render on a Intel A750 Arc GPU. Performance is also hit pretty hard compared to using DX11.

Running with Mesa 22.3.1 - kisak-mesa and kernel 6.0.6-76060006-generic on Pop OS.

steam-391220.log

This is a little weird to explain so bare with me here.

i'm using a Dualsense joystick and on windows the game detects it as a DS4 if steam input is disabled

on linux, first of all i changed my dualsense light bar color to steam purple and whenever steam input is on that will be the light bar color, otherwise it will be blue (games that support dualsense natively can behave differently, anyways).

so lately on linux only, by having playstation controller support setting enabled, even if steam input is disable i can tell its there somehow because the light bar is purple, even if the virtual xbox controller that steam input creates is not there its still somehow on, its just no passing any inputs...

and that seems to be interfering in this game in particular because on windows i could have dualshock 4 prompt buttons if steam input was disabled, here its no possible at all because steam input is somehow interfering, and totally disabling playstation controller support simply makes it invisible to the game...

the linux native version of the game does have generic support for all playstation controllers but for the dualsense it enumerates its properties incorrectly and the motion sensors part keeps getting in the way and the only workaround i know is to disable the motion sensor part of the controller on a system level so the game doesn't enumerate it.

this could also be fixed if steam input was also able to expose the dualsense controller and its similar capabilities as a dualshock 4 instead of a generic xbox controller...

The GOG version is having crashes in between camps (sometimes it crashes only by the second camp you find) or even restarts / exit to menu, also sometimes the cutcene at the end of the "THE PROPHET'S TOMB" is all black either with DX11 or 12.

At this point i think i used every proton version but no change.

Using the SteamDeck with latest Bazzite and Heroic launcher.

This is Heroic's log but hopefully you can still get some sense out of it.

launch.log

I've found an issue with this game when setting the renderer to DX12 and SSAA2X: it keeps flickering (can be observed even on the main menu). No problems with the default renderer (DX11). I've tested with Proton 8.0-5 up to Experimental-2025-12-23.

Proton 10.0-4 (RC) logs: steam-391220.tar.gz

Main error logs:

15051.140:0134:02f8:warn:vkd3d-proton:d3d12_command_list_IASetPrimitiveTopology: Ignoring D3D_PRIMITIVE_TOPOLOGY_UNDEFINED.
15051.140:0134:02f8:warn:vkd3d-proton:d3d12_command_list_update_graphics_pipeline: No graphics pipeline bound, skipping draw.
15051.140:0134:02f8:warn:vkd3d-proton:d3d12_command_list_DrawIndexedInstanced: Failed to begin render pass, ignoring draw call.
15051.140:0134:02f8:warn:vkd3d-proton:d3d12_command_list_update_graphics_pipeline: No graphics pipeline bound, skipping draw.

Specs:

• OS: Arch
• Kernel: 6.12.61
• GPU: RX 6700 XT (Mesa 25.2.7)
• CPU: Ryzen 7 5700G (8c/16t)
• DE: Plasma 6.5.3 (wayland)
• Display: 1440p 120hz