have you tried something similar like fort solis , some user put this command WINE_CPU_TOPOLOGY=8:0,1,2,3,4,5,6,7 proton command line...?? it seems have to do with patch 2.0 cpu settings not understood in linux scheduler when settings only works in windows scheduler kernel , i got this help from https://www.protondb.com/app/1931730 for that game stuttering all over place in video that i assume latest mesa-git 24 fix all that problem but now i know why is needed to be use 8 cores only but i see only use 8 threads in that topology...i wonder if i can put 16 threads since i only have 12 core cpu..with SMT on always in linux kernel but in windows kernel is dynamic does differently in core topology is run in user layer, not in kernel layer

another thing HansKristian, if you reading this now or later, i discover something odd in every game coming out in their game dir is they are including a different d3d12core.dll from one another game folder...what does that means now ?? cause in 2 unreal 5 games all have different size in them than your custom wine d3d libraries ?? i just hope microsoft didn't throw a curve ball at you now than year ago it was very quiet from them from years before than lately i see more activity between microsoft and game devs , not sure AMD is back stabbing you now when they are now partnering with phil spencer now , i just keeping heads up whats happening lately

Also had the same problem with RTX 4070 and 535.43.15, so it happens on Nvidia too. I got some breadcrumbs from that Xid 109 and then reproduced the hang with an RX 7600 to get a UMR dump as well. Descriptor QA checks didn't turn up anything.

UMR_logs.zip

As a temporary workaround, it seems like the game works when you set SteamDeck=1 (i.e. putting
SteamDeck=1 %command% in the launch arguments field, or simply playing on Deck).