Was told to make a issue here to track it and maybe get a hands on lookover by a dev.
Note that the crash is being worked around in mesa main by spoofing another vendor id, but IMO the cause for the crash should be looked at.
Jusant crashes on Linux when it sees a Intel vendor id, unrelated to the old XeSS crashes as the game doesn't support it. This is both on actual Intel GPUs but also other vendors (AMD at least) when spoofing as intel, which i assume rules out a ANV bug.
@K0bin Did give me a vkd3d-proton build with some extra logging to see if anything was going wrong on the vkd3d-proton side, but i gather it didn't look so.
A maybe theory is that it could be about Intel emulated 64bit atomics, but nothing have been confirmed
Was told to make a issue here to track it and maybe get a hands on lookover by a dev.
Note that the crash is being worked around in mesa main by spoofing another vendor id, but IMO the cause for the crash should be looked at.
Jusant crashes on Linux when it sees a Intel vendor id, unrelated to the old XeSS crashes as the game doesn't support it. This is both on actual Intel GPUs but also other vendors (AMD at least) when spoofing as intel, which i assume rules out a ANV bug.
The line of interest from a Proton log is
Log with trace enabled: steam-1977170.log
@K0bin Did give me a vkd3d-proton build with some extra logging to see if anything was going wrong on the vkd3d-proton side, but i gather it didn't look so.
A maybe theory is that it could be about Intel emulated 64bit atomics, but nothing have been confirmed
K0bin build with extra logging: steam-1977170-K0bin-build.log
Software information
Jusant
System information