Closed orbea closed 5 years ago
See https://github.com/iXit/Mesa-3D/issues/350#issuecomment-504707197.
I have determined this issue occurs when mesa is compiled with clang-8.0.0, but does not occur with gcc-9.1.0. I have built a full debug build of mesa with no optimizations and still could reproduce this issue.
I am going to close this as a duplicate of issue https://github.com/iXit/Mesa-3D/issues/350.
OS:
Slackware64-current
wine:4.9-staging
(With both 64/32-bit) wine-nine-standalone: https://github.com/iXit/wine-nine-standalone/commit/b41e162549196f0a88c603609d8a69c4bcf44171I got the game
Grim Dawn
from GOG.https://www.gog.com/game/grim_dawn
It apparently can use either
d3d11
ord3d9
, to use the latter.This seems to work just fine, but if wine-nine-standalone is enabled it will hang on a black screen and never start even after waiting around 10 minutes.
I made a trace with apitrace as explained in the wiki.
https://github.com/iXit/wine-nine-standalone/wiki/apitrace
trace: grim_dawn_d3d9.trace.xz.txt
(Remove the
.txt
extension)However upon replaying this trace I get a crash.
wine crash report: grim_dawn_backtrace.txt
Any ideas how to figure out what the problem is?