shelterx

Hmm... seems like it was the pipe error which @InBetweenNames provided a fix for above, I didn't see the actual error yesterday *blind*. EDIT: Well, it didn't help with NOCOMMON_OVERRIDE_LIBTOOL=yes....

I tried this with a currently installed Epic Games Store game and got could not load ntdll.so (proton-ge-custom). It works fine without the ulwgl patches tho'. So it's something with...

> > Heroic now requires only `ulwgl-run` file to be present in the `tools/runtimes/ulwgl` directory. The script will download the whole runtime as needed > > How do I check...

You have to build this PR yourself, right now it got conflicts with master so best is that you wait until it's merged.

> And there is an error from Chrome: > > ``` > [2006932:2007376:0210/185127.505732:ERROR:vaapi_video_decoder.cc(1249)] failed Initialize()ing the frame pool > ``` This is currently affecting Chrome with Nvidia and it's been...

Ok, so the previous error is gone but there's another one now, with the latest chromium release I have: ``` [184461:184765:0226/154948.136812:ERROR:vaapi_wrapper.cc(2322)] : vaCreateContext failed, VA error: resource allocation failed [184461:184765:0226/154948.136886:ERROR:vaapi_video_decoder.cc(1242)]...

Still crashing with 555.42.02 [tis maj 21 15:48:18 2024] NVRM: Xid (PCI:0000:01:00): 109, pid='', name=, Ch 0000004f, errorString CTX SWITCH TIMEOUT, Info 0x51c04d

This is confusing me so much, sometimes it just crashes almost straight away, sometimes it's like it's never happend and the game runs fine. 555 beta again... First launch, compiled...

FWIW, I tried spoofing a different nvidia GPU architecture, it did not help either. Nor did disabling nvapi.

I might have to eat my words later but vkd3d-https://github.com/HansKristian-Work/vkd3d-proton/commit/e957460ed1aade52300d5dfb9790478cd1ab80d9 and Nvidia 560.31.02 no longer causes XID 109 crashes here. (I don't use the nvidia open driver and have GSP...