Compatibility Report

Try setting "bHardwareRayTracing=True" in the game's config file, for some reason RT off breaks it

@abarisain Are you experiencing the same issue? What GPU and driver do you have?

Maybe it's not exactly the same problem: I can start the game, see the shader compilation but as soon as I configure brightness the game freezes. Relaunching the game won't get past a black screen (or the first logo).

To "fix" it I enabled hardware ray tracing in the configuration file in the prefix steamapps/compatdata/1449110/pfx/drive_c/users/steamuser/AppData/Local/Arkansas/Saved/Config/Windows/GameUserSettings.ini which of course makes the performance terrible

Toggling it to OFF while ingame makes the game crash instantly.

My environment:

• 14700k
• 5090
• Arch linux (latest)
• NVIDIA oss 580.95.05
• Proton Hotfix (selected by valve)

Hi Everyone,

Try setting "bHardwareRayTracing=True" in the game's config file, for some reason RT off breaks it

This worked, and I have been able to play without many issues, Only 1 crash so far in 10+ hours of gameplay.

@abarisain Are you experiencing the same issue? What GPU and driver do you have?

I am using a RTX 5080, with the NVIDIA 580.95.05 driver.

Replying to https://github.com/ValveSoftware/Proton/issues/9138#issuecomment-3467355023

This was the same issue I was experiencing. I haven't seen much if any reduction in performance, the game seems to perform the same for me in Windows.

From update 1.0.5.0, I am no longer able to workaround this issue by enabling hardware ray tracing (and we shouldn't need to have it enabled to play the game anyways). I'm entirely unable to play the game now, as it freezes right after compiling shaders regardless of ray tracing option.

(PROTON_LOG=1 is generating 100MiB files and I am unable to upload them to github)
https://files.catbox.moe/rnnnly.log

Arch Linux x86_64
Linux 6.17.7-zen1-1-zen
AMD Ryzen 7 7800X3D
NVIDIA GeForce RTX 5080
nvidia-open-dkms 580.105.08-2
Proton 10.0-3, Proton Experimental, Proton Hotfix, GE-Proton10-25

and we shouldn't need to have it enabled to play the game anyways

Of course, no one is saying that, it was a workaround. Haven't tested this update last week but Exeperimental allowed me to boot the game.

https://github.com/ValveSoftware/Proton/wiki/Changelog : "Fixed long wait on every launch of many Xbox Game Studios games including Avowed, Grounded 2, Indiana Jones and the Great Circle, and The Outer Worlds 2." this is the release that fixed it for me

I was able to get the game running again on 1.0.5.0 by setting to true both bHardwareRayTracing and bHardwareRayTracedShadows in ~/.steam/steam/steamapps/compatdata/1449110/pfx/drive_c/users/steamuser/AppData/Local/Arkansas/Saved/GameUserSettings.ini. Still not optimal at all, but at least I can play the game somehow.

Bink2 cutscene audio silent on RDNA4 (RX 9060 XT)
System:
• GPU: AMD RX 9060 XT (Device ID 7590, RDNA4)
• Mesa: 25.2.8
• Kernel: 6.17.0-23-generic
• Ubuntu 24.04, Wayland/PipeWire
• Proton versions tested: 10.0-4, GE-Proton10-26, CachyOS Proton 10.0-20260409, Proton Experimental
Issue:
All Bink2 cinematics play video correctly with subtitles but no audio. In-engine cutscenes work fine. The issue is specific to .bk2 files.
Findings from PROTON_LOG=1:
• Bink threads initialize correctly (BinkAsy0-3, Bink Snd, Bink IO)
• mfplat.dll loads as builtin despite native DLLs installed via winetricks and DllOverrides set in registry
• PULSE_LATENCY_MSEC=200 made audio intermittent with CachyOS Proton, suggesting a PipeWire timing race
• Pausing during a cutscene briefly triggers audio before going silent again
What works:
• ProtonDB reports confirm the game works perfectly on RDNA3 (RX 7800 XT) with Proton 10.0-3 on Manjaro/kernel 6.12
Suspected cause:
RDNA4-specific issue in Bink2 audio initialization timing under PipeWire. The intermittent behavior with CachyOS Proton suggests the fix path exists but isn’t stable.