Open GrabbenD opened 5 months ago
Outside of staging and GE patches, we also build latest dxvk/vkd3d-proton which can at times regress. Considering you nuked many default options by replacing proton-tkg.cfg content with advanced-customization.cfg's, which lacks both _use_GE_patches
and _use_staging
variables, it's likely to be one or the other, or both.
That being said I just tested the game with a fresh experimental bleeding edge build and it worked OOTB with default settings.
Wasn't this game affected by the lack of shared gpu resources? I did remember trying it when Tkg and others firstly reported how much the patchset was broken in wine after a certain version. It's sad that the game is atrocious to debug
This doesn't apply here as Valve based builds have a working implementation. If we were talking about an upstream based build, of course that doesn't work.
Overview
Here's what I've tried in Arch Linux:
wine-tkg-git/proton-tkg/proton-tkg.cfg
to:After finding a working configuration file I confirmed Fsync + Fastsync aren't causing it by compiling with:
Other than that I've also tried enabling this in
proton-tkg/proton-tkg.cfg
to no avail:How do I actually find which configuration option is causing this issue in
proton-tkg/proton-tkg.cfg
/ how do I get the same experience as Proton Experimental?Logs
When I'm starting Halo Infinite using
$ steam-native
, it crashes instantly without producing any logs which could indicate the issue: