[Bug 43935] Wolfenstein 2: The new Colossus does not start, requires VK_KHR_get_physical_device_properties2

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=43935

--- Comment #9 from Dave Airlie <airlied at gmail.com> ---
(In reply to javitonino from comment #7)
> (In reply to Dave Airlie from comment #5)
> > I'd be interested in knowing if the nvidia gets started with the hack patch.
> 
> nvidia + wine-staging 2.19 + vkGetPhysicalDeviceProperties2KHR patch here.
> 
> After the videos and splash screens I get a black screen, with a cursor (a
> white 90º angle). I get audio cues when playing with the keyboard, so the
> menu seems to be working even if it isn't rendering. If I press enter 3 or 4
> times in a row, I get into an intro cinematic (previously on Wolfenstein).
> After the cinematic ends (or if I try to skip it), the screen freezes in the
> last frame from the intro, loses the input grab, and gets stuck, no sound
> nor video.

Oh cool, I've reproduced the same thing on radv here now, pressed enter a few
times, video and hang.

err:ntdll:RtlpWaitForCriticalSection section 0x142fde5f8 "?" wait timed out in
thread 00aa, blocked by 00ab, retrying (60 sec)
err:ntdll:RtlpWaitForCriticalSection section 0x142fde5f8 "?" wait timed out in
thread 00aa, blocked by 00ab, retrying (60 sec)

I get a couple of those, but it doesn't seem to be a gpu hang at least.

-- 
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.