Ok, seems i'm not getting the issue if i run ntsync with GEProton10-13 and PROTON_ENABLE_WAYLAND, managed to pull 4 hours without a crash so far.
Not sure if something upstream fixed it or ntsync being the saving grace, would be a first for me that ntsync would solve a crash.
@a3d0n I've had no luck reproducing either issue you mention, at most I got the game (not the system) to temporarily freeze but only once after 3 sessions, and the game continued as if nothing had happened.
If your system hanged there will likely be kernel logs a bout it. Let's say your system hangs and you're forced to reboot, you can check the previous session kernel logs by using journalctl -k -b -1 or journalctl -k -b -1 > kernel.log to store it into a file.
Meanwhile, the unreal crash dialogs mean the game is likely storing crash logs in the prefix, probably somewhere in the AppData folder
@simifor Good catch indeed some dumps are in fact there, il have to re-test Experimental before i can be definitive.
Current setup with GE and NTSync does not yield a crash.
The dev has come forward acknowledging some crash on modern platform on Windows. So could just be a bug that acted weird with the overall system.
So i'm forwarding them the logs with relevant context.
Managed to get a 2 hours of gameplay without a crash compared to 30 minutes or less.
Differences:
mesa 1:26.0.1-1 (seem to be the improvement unless proven otherwise)
mesa 1:25.3.5-1 (and other previous versions)
(Will comment if that changes)
Compatibility Report
System Information
I confirm:
Symptoms
Will either hang and freeze the system forcing a hard reboot or a small UE5 prompt saying a Fatal Crash occurred.
Previous Kernel/Mesa version would signal a ring 0 reset in the system logs, but these no longer occur but the crash persist randomly.
Reproduction
steam-2615540.log
When running something like GE the following will appear in system logs.
coredump-voidbreaker.log
Hope you got all the info you need, you guys rock and let me know if i can test something that will give additional insight or possibly better reproduction of the issue. As i am not sure if its a Proton/WINE, Mesa or Kernel issue still.