[Bug 43935] Wolfenstein 2: The new Colossus does not start, requires VK_KHR_get_physical_device_properties2
wine-bugs at winehq.org
wine-bugs at winehq.org
Thu Nov 9 11:20:10 CST 2017
https://bugs.winehq.org/show_bug.cgi?id=43935
--- Comment #26 from Stefan Dösinger <stefan at codeweavers.com> ---
I can see the same hangs, but it is random. I got past that scene after a few
tries. However, a similar hang occurs when leaving the Ausmerzer, and so far I
didn't get past it; I only tried a few times though.
It doesn't seem to be a crash, or at least gdb doesn't pick up any exceptions.
The game continues to run and consume plenty of CPU time. It'll probably need a
+relay log to find out more, or even +all,-snoop. And then finding what's
causing the problem will be like finding a needle in a heystack with the
10-something threads doing work, some of it working as intended, and one piece
subtly broken. It could very well be a side effect of my ReadFileScatter hack.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list