https://bugs.winehq.org/show_bug.cgi?id=48171
Vincent N. vinni5.2001@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vinni5.2001@web.de
--- Comment #21 from Vincent N. vinni5.2001@web.de --- Created attachment 68449 --> https://bugs.winehq.org/attachment.cgi?id=68449 Crash after a few seconds.
Me and a few other have been trying a few things the last few days and got a bit further. Wine 5.19 + Staging as well as the following patches are needed: https://github.com/rbernon/wine/compare/master...wip/gdi32.dll/v1.patch https://pastebin.com/raw/EuBwYFRU https://pastebin.com/raw/uPfN7RmD Latest vkd3d-proton is also needed (this commit to be exact: https://github.com/HansKristian-Work/vkd3d-proton/commit/3a4e555e9c289cf3803...).
All of that combined allows you to get past the initial loading window and a game window appears. However it crashes after a few seconds. Changing the config to skip the intro (649200945 = 1) might give you enough time to see and interact with some of the UI before it crashes.
We noticed some errors/fixmes that appeared somewhat consistently. We believe those might be the current reasons for the crash:
0418:fixme:winsock:server_ioctl_sock Unsupported ioctl c8000024 (device=c800 access=0 func=9 method=0) 0418:fixme:winsock:WSAIoctl unsupported WS_IOCTL cmd (_WSAIORW(IOC_WS2, 36)) 0418:fixme:bcrypt:BCryptOpenAlgorithmProvider algorithm L"3DES" not supported
While not directly related to this game, when running "Call of Duty: Black Ops Cold War" using the same wine build and prefix, the WS_IOCTL error appears every launch and pretty much right before it crashes (yep, unfortunately that one crashes too, but even before it's able to create a window).
Attaches is a normal console output log with a fresh wine build and prefix using the listed patches.