Ben

First try after my comment ... and it crashed within 10 minutes. Overall a bit longer than before, but it did crash. Here's the new [journal.log](https://github.com/user-attachments/files/17562698/journal.log) attached :)

OK? I had it running all the time with `journalctl -b 0 >> journal.log`? Is there an option to let it output endlessly?

I've recorded with `sudo journalctl -b 0 -f > journal.log` now and I think I've got something useable. Game ran for approx 5 minutes - got some time between start...

Here's a I've did with `PROTON_LOG=1 %command%`. Part 1: [proton_part1.log](https://github.com/user-attachments/files/17564202/proton_part1.log) Part 2: [proton_part2.log](https://github.com/user-attachments/files/17564203/proton_part2.log) Here's the part shortly before the crash until after the game got terminated: ```Ruby 7103.976:0278:03b8:warn:vkd3d-proton:dxgi_vk_swap_chain_wait_worker: Failed to...

@17314642 > Also, not that it will solve anything, but could you limit fps so that gpu load will always be lower than 98% and test if game crashes in...

Sure thing, here you go @17314642 ``` ben@benDesk:~$ sudo journalctl --list-boots IDX BOOT ID FIRST ENTRY LAST ENTRY -20 1d2c891de61d46f885d30fe97da10345 Sat 2024-10-26 00:46:50 CEST Sat 2024-10-26 01:44:43 CEST -19 8e4a6e703a564b028ce3d016a41e20fa...