April 2020 - Wine-Bugs - list.winehq.org

[Bug 39602] New: World of Warships: game launched thow unhandled exception
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=39602 Bug ID: 39602 Summary: World of Warships: game launched thow unhandled exception Product: Wine Version: 1.7.53 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mazhe(a)alkumuna.eu Created attachment 52768 --> https://bugs.winehq.org/attachment.cgi?id=52768 Console output Hi, I am trying to run the game World of Warships on FreeBSD 10.2 with 32bit wine version 1.7.53 (not staging). I followed procedure described on forums to install directx9, wininet and other dependencies, a procedure that worked on a GNU/Linux (devuan) and a OSX installations. On this FreeBSD however, while the initial installer works, the launched that will then download real game assets and such simply fails with a dialog box saying: An unhandled exception is occured. The application will be restarted With the choice "OK" looping forever with that issue, and "Cancel" exiting. One more information is that there have been report about trying to enable/disable torrent download by edition a plain text config file inside the game, but it did not change anything. Here is the console output of wine, if somebody could take a look... I don't see why it's working even on OSX but not FreeBSD... Thanks -- 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.

2 19

[Bug 39565] New: World of Warships: working in GNU/Linux (Devuan), but not FreeBSD: out of memory?
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=39565 Bug ID: 39565 Summary: World of Warships: working in GNU/Linux (Devuan), but not FreeBSD: out of memory? Product: Wine Version: 1.7.53 Hardware: x86 OS: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: mazhe(a)alkumuna.eu Created attachment 52713 --> https://bugs.winehq.org/attachment.cgi?id=52713 Application error message I have been able to install and play the game world of warships on GNU/Linux (Devuan Linux), but copying the wine prefix, I cannot run it on FreeBSD as I am getting a "out of memory" message. This is a bit strange, as I should have plenty available... I am using the packaged version of wine development version. I've attached the exact program error message and wine trace, if anybody can give me pointers... -- 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.

2 13

[Bug 39347] New: World of Warships 0.4.x/0.5.x: incorrect water surface height calculated for unknown reasons, causing ships to appear floating in the air
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=39347 Bug ID: 39347 Summary: World of Warships 0.4.x/0.5.x: incorrect water surface height calculated for unknown reasons, causing ships to appear floating in the air Product: Wine Version: 1.7.51 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Created attachment 52441 --> https://bugs.winehq.org/attachment.cgi?id=52441 focht's nagato "floating" in port after return from game (water surface level too low) Hello folks, that game got me hooked up at bit (= less time on bugs *g*). Unfortunately I frequently encounter a nasty in-game bug that surfaces after a certain amount of time/actions. I created a support ticket at wargaming.net with screenshots along with some information. The ticket hang in pending queue for ~1 week only to be answered by a generic form "please update your graphics drivers". Oh well. I mentioned this issue during talks with WineD3D folks at WineConf 2015. It seems this issue was already known to CodeWeavers (Stefan Doesinger, Matteo Bruni, Caron Wills). It's not known yet if this is a Wine bug, a bug with the wargaming engine or graphics drivers. There was a hint from Caron to try "low" water rendering setting but I figured out the bug is present there too but much less noticeable (smaller water surface "drop" value). It seems I could force the in-game water surface level drop multiple times by moving the ship near an island/land mass and then zoom in/zoom out with island in view (couldn't reproduce consistently though). If the water drop happened once - it stayed forever - even the ships in port floated in the air. Exiting and restarting the client solved the issue. I encountered the bug with WoWS 0.4.0 upgrade for the first time. Previous 0.3.x version didn't show it but also crashed more frequently hence there never was a time when the client ran for consecutive (hour long) game sessions. I briefly looked at the game engine and found some game engine locations related to water rending properties along with their float representations. Since I didn't want to mess up my account by live-debugging/dumping game engine data (which could be considered hacking) I refrained from doing further investigation. A builtin offline simulation mode would have been nice ... but well. Tested with recent Wine 1.7.5x version. Graphics used for testing (all exhibit the same problem): Intel Haswell HD4600 with FOSS Intel/Mesa: ---- snip --- OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.3 (git-ccef890) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.6.3 (git-ccef890) OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.3 (git-ccef890) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: ---- snip --- NVIDIA GeForce GTX 850M, NVIDIA binary drivers (via optimus): ---- snip --- OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GTX 850M/PCIe/SSE2 OpenGL core profile version string: 4.4.0 NVIDIA 352.21 OpenGL core profile shading language version string: 4.40 NVIDIA via Cg compiler OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.5.0 NVIDIA 352.21 OpenGL shading language version string: 4.50 NVIDIA OpenGL context flags: (none) OpenGL profile mask: (none) OpenGL extensions: ---- snip --- NVIDIA GeForce GT 425M with FOSS Nouveau/Mesa: --- snip --- $ glxinfo | grep -i opengl OpenGL vendor string: nouveau OpenGL renderer string: Gallium 0.4 on NVC1 OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.6.3 (git-ccef890) OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.6.3 (git-ccef890) OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 10.6.3 (git-ccef890) OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: --- snip --- Attached are some screenshots. Regards -- 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.

2 12

[Bug 43785] New: New Critical Error World of Warships 0.6.11
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=43785 Bug ID: 43785 Summary: New Critical Error World of Warships 0.6.11 Product: Wine Version: 2.12 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: major Priority: P2 Component: kernel32 Assignee: wine-bugs(a)winehq.org Reporter: captmatt95(a)yahoo.ca Created attachment 59298 --> https://bugs.winehq.org/attachment.cgi?id=59298 Screen shot of error message. Game crashes on launch. Recently updated the game to 0.6.11. I have also done several software updates to see if that was the issue. -- 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.

2 6

[Bug 42519] New: WorldofWarschips crashes at start
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=42519 Bug ID: 42519 Summary: WorldofWarschips crashes at start Product: Wine Version: 1.8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Wh1sper(a)zockertown.de Distribution: --- Created attachment 57410 --> https://bugs.winehq.org/attachment.cgi?id=57410 backtrace of wine wine-1.8.6 (Debian 1.8.6-5) WorldofWarships 0.6.1.1 -- 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.

2 5

[Bug 45973] New: World of Warships Crashes upon start
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=45973 Bug ID: 45973 Summary: World of Warships Crashes upon start Product: Wine Version: 3.17 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: chrisspen(a)gmail.com Distribution: --- Created attachment 62530 --> https://bugs.winehq.org/attachment.cgi?id=62530 .crash file Installation of World of Warships using 32-bit Wine 3.17 happens smoothly, but upon launching the installed game, it spends a couple minutes "loading" and then crashes. The generated .crash and .dmp files are attached. Also attached is the PlayOnLinux bash script used to setup the Wine environment. -- 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.

2 6

[Bug 43515] New: World of Warships 0.6.9 crashes with Critical Error Occurred
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=43515 Bug ID: 43515 Summary: World of Warships 0.6.9 crashes with Critical Error Occurred Product: Wine Version: 2.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: ankouslash(a)yahoo.co.jp Distribution: --- Created attachment 58905 --> https://bugs.winehq.org/attachment.cgi?id=58905 Error dialog World of Warships (WoWs) 0.6.9 crashes with Critical Error Occurred. This seems to be same error as #4314 but the workaround (changing Windows version on winecfg) doesn't effect. Wargaming releases update of MacWrapper (wine Wargaming's custom for MacOS) to fix this problem: https://na.wargaming.net/support/kb/articles/813 Steps to reproduce: 1) Choose Application menu > wine > Programs > World of Warships > World of Warships (Launched WoWSLauncher.exe) 2) Click "Play" (Launched worldofwarships) 3) Click "Connect!" Repeatability: Always Version: wine 2.14 wine-mono 4.7.1 wine-gecko 2.47 on ArchLinux(x86_64) WINEARCH=win32 Windows version on winecfg: Windows10, 7 and XP I confirmed Thx -- 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.

2 8

[Bug 43609] New: World of Warships Crash
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=43609 Bug ID: 43609 Summary: World of Warships Crash Product: Wine Version: 2.0.2 Hardware: Other OS: Mac OS X Status: UNCONFIRMED Severity: critical Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: captmatt95(a)yahoo.ca Created attachment 59025 --> https://bugs.winehq.org/attachment.cgi?id=59025 This is the screen shot of the error message Updated to the most recent wrapper for World of Warships, and the most recent game update. The game now crashes when you start the game. (Pressing PLAY) I submited a ticket with wargaming but they advised to contact you. Attach is the screen shot of the error message. I was unable to run the debugger. -- 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.

2 6

[Bug 43412] New: World of Warships: CEF screens cannot be displayed
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=43412 Bug ID: 43412 Summary: World of Warships: CEF screens cannot be displayed Product: Wine Version: 2.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: Andreas.Schallenberg(a)Eurobild.com Distribution: --- This bug is very similar to #42707. When in WoWS port screen there are several management screens that use CEF. Those cannot be opened. When trying, an additional half-transparent layer is created on top the graphics, three dots are written on top (this should be replaced by the screen title if working) and in the middle of the screen there's an anchor symbol with an animation. On the top right corner a hint is displayed to press ESC to leave. Nothing else is being displayed. Pressing ESC brings you back to the original screen and the transparent layer is removed. This happens at least with: - Inventory screen - News screen - Clan screen - "Invite a friend" Environment: - Wine version is 2.13, downloaded from build.opensuse.org/Emulators - Host is (uname -a): Linux jordan 4.4.74-18.20-default #1 SMP Fri Jun 30 19:01:19 UTC 2017 (b5079b8) x86_64 x86_64 x86_64 GNU/Linux - Game version is 0.6.8.1 Tahoma font package installed, no wrapper like PlayOnLinux is used, Windows version set to 10 (same behavior as setting to 7). -- 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.

2 11

[Bug 47096] New: World of Warships 0.8.3.x client crashes when post-battle results screen is about to be displayed
by wine-bugs＠winehq.org Feb. 13, 2021

Feb. 13, 2021

https://bugs.winehq.org/show_bug.cgi?id=47096 Bug ID: 47096 Summary: World of Warships 0.8.3.x client crashes when post-battle results screen is about to be displayed Product: Wine Version: 4.7 Hardware: x86 OS: Linux Status: NEW Severity: normal Priority: P2 Component: directx-d3dx11 Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, encountered with their 0.8.3.x update which added various features and also removed legacy stuff (DX9). * support for DX11/XD12 (Vulkan) * support for 64-bit client (they still ship 32-bit one too) ... * profit! That update is kinda messy, it introduced a number of bugs which look like Wine and non-Wine issues, but it's hard to tell. Vodka stronk, Tovarish! https://forum.worldofwarships.com/forum/266-support/ https://na.wargaming.net/support/en/products/wows/article/10746/ To reproduce that particular crash at post-battle results: Join any game and finish it. Alternatively, create a training room with 1 bot. It crashes immediately before the battle results screen is about to be displayed. Doesn't matter if 32-bit or 64-bit client is used. Also Wine-Staging vs. plain Wine has no effect. The game has an own crash reporting tool which writes out crash dumps: --- snip --- $ find drive_c/Games/World_of_Warships/bin32/crashes/ drive_c/Games/World_of_Warships/bin32/crashes/ drive_c/Games/World_of_Warships/bin32/crashes/WorldOfWarships32-2019-04-29_11-47-15.crash drive_c/Games/World_of_Warships/bin32/crashes/WorldOfWarships32-2019-04-28_18-22-53.crash drive_c/Games/World_of_Warships/bin32/crashes/WorldOfWarships32-2019-04-28_20-30-51.crash ... --- snip --- --- snip --- Application C:/Games/World_of_Warships/bin32/WorldOfWarships32.exe crashed 04.29.2019 at 12:47:21 Message: Unhandled exception Hash: 11898 EIP: 0x0000000000C70127 Current thread #9 native trace: (0) : WorldOfWarships32.exe!0x00C70127 (0) : WorldOfWarships32.exe!0x00D925A3 (0) : WorldOfWarships32.exe!0x00D9270D (0) : WorldOfWarships32.exe!0x00D8A018 (0) : WorldOfWarships32.exe!0x00A8C40E (0) : WorldOfWarships32.exe!0x00B14B79 (0) : WorldOfWarships32.exe!0x00B14B79 (0) : WorldOfWarships32.exe!0x00A83853 (0) : WorldOfWarships32.exe!0x00A7EC11 (0) : WorldOfWarships32.exe!0x00A7C173 (0) : WorldOfWarships32.exe!0x00A127FB (0) : KERNEL32.dll!call_process_entry System info: OS Name: Windows 7 OS Version: 6.6 SP1 OS Architecture: x86_64 Memory info: Virtual memory: 64Kb/4194175Kb (1%) Working set (process physical memory): 1802200Kb/4194175Kb (42%) Commit charge (working set + process page file usage): 1648804Kb/4194175Kb (39%) Global physical memory: 5635652Kb/16302720Kb (34%) Global commitable memory (physical + pagefile): 5702212Kb/24527484Kb (24%) System info: APPLICATION = DISPLAYDEVICE 0 = \\.\DISPLAY1, X11 Windowing System, PCI\VEN_0000&DEV_0000 --- snip --- With a debugger attached to grab the exception before the crash reporter: --- snip --- ... 002e:fixme:d3d11:d3d11_device_CheckFormatSupport iface 0x1b8968, format 87, format_support 0x32b15c partial-stub! 002e:fixme:d3d11:d3d11_device_CheckFormatSupport iface 0x1b8968, format 87, format_support 0x32b15c partial-stub! Unhandled exception: page fault on read access to 0x00000074 in 32-bit code (0x0000000000c70127). Register dump: CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b EIP:00c70127 ESP:0032b220 EBP:0032b228 EFLAGS:00010202( R- -- I - - - ) EAX:0032b244 EBX:07eec39c ECX:00000000 EDX:00000000 ESI:00000000 EDI:8012ddc4 Stack dump: 0x000000000032b220: 00000000806396bc 00d925a30032b250 0x000000000032b230: 000000000032b244 0000000080639680 0x000000000032b240: 0000000500000000 00000000019eb9c4 0x000000000032b250: 00d9270d0032b264 806396808012ddc0 0x000000000032b260: 0032b290ffffffff 07494e8000d8a018 0x000000000032b270: 0000000000000000 3ce5d3cf019d12e0 0x000000000032b280: 07494e8007eec340 01a0bee800000000 0x000000000032b290: 00a8c40e0032b2bc 034300d003434180 0x000000000032b2a0: 019d12e00032f818 407b3def84478000 0x000000000032b2b0: 407b3d7c9a600000 0032b2d03ce5d3cf 0x000000000032b2c0: 3ce5d3cf00b14b79 03434d8c03434080 0x000000000032b2d0: 00b14b790032b2e4 0032f4a03ce5d3cf Backtrace: =>0 0x0000000000c70127 EntryPoint+0x25d8a8() in worldofwarships32 (0x000000000032b228) 1 0x0000000000d925a3 EntryPoint+0x37fd23() in worldofwarships32 (0x000000000032b250) 2 0x0000000000d9270d EntryPoint+0x37fe8d() in worldofwarships32 (0x000000000032b264) 3 0x0000000000d8a018 EntryPoint+0x377798() in worldofwarships32 (0x000000000032b290) 4 0x0000000000a8c40e EntryPoint+0x79b8e() in worldofwarships32 (0x000000000032b2bc) 5 0x0000000000b14b79 EntryPoint+0x1022f9() in worldofwarships32 (0x000000000032b2d0) 6 0x0000000000b14b79 EntryPoint+0x1022f9() in worldofwarships32 (0x000000000032b2e4) 7 0x0000000000a83853 EntryPoint+0x70fd3() in worldofwarships32 (0x000000000032b32c) 8 0x0000000000a7ec11 EntryPoint+0x6c391() in worldofwarships32 (0x000000000032fe18) 9 0x0000000000a7c173 EntryPoint+0x698f3() in worldofwarships32 (0x000000000032fe74) 10 0x0000000000a127fb EntryPoint+0xffffffffffffffff() in worldofwarships32 (0x000000000032fec0) 11 0x000000007b472c52 call_process_entry+0x11() in kernel32 (0x000000000032fed8) 12 0x000000007b47557a start_process+0x149(entry=<couldn't compute location>, peb=<couldn't compute location>) [/home/focht/projects/wine/mainline-src/dlls/kernel32/process.c:1256] in kernel32 (0x000000000032ffd8) 13 0x000000007b472c5e start_process_wrapper+0x9() in kernel32 (0x000000000032ffec) 0x0000000000c70127 EntryPoint+0x25d8a8 in worldofwarships32: movl 0x74(%esi),%eax Wine-dbg>info process pid threads executable (all id:s are in hex) >0000002d 34 'WorldOfWarships32.exe' 00000067 30 \_ 'cef_browser_process.exe' 00000032 13 \_ 'WargamingErrorMonitor.exe' 00000023 4 'explorer.exe' 0000000e 5 'services.exe' 0000001e 4 \_ 'winedevice.exe' 00000019 3 \_ 'plugplay.exe' 00000011 4 \_ 'winedevice.exe' 00000008 1 'winedbg.exe' 00000029 1 \_ 'WorldOfWarships32.exe' Wine-dbg>info thread process tid prio (all id:s are in hex) 00000008 winedbg.exe 00000009 0 0000000e services.exe 00000020 0 ... 0000000f 0 00000011 winedevice.exe 00000018 0 ... 00000012 0 00000019 plugplay.exe 0000001d 0 0000001c 0 0000001a 0 0000001e winedevice.exe 00000025 0 ... 0000001f 0 00000023 explorer.exe 00000028 0 ... 00000024 0 00000029 WorldOfWarships32.exe 0000002a 0 0000002d (D) C:\Games\World_of_Warships\bin32\WorldOfWarships32.exe 0000005f 0 ... 0000002f 0 0000002e 1 <== 00000032 WargamingErrorMonitor.exe 00000049 0 ... 00000033 0 00000067 cef_browser_process.exe 00000087 0 ... 00000068 0 Wine-dbg>info share Module Address Debug info Name (265 modules) PE 330000- 362000 Deferred ortp PE 370000- 3a4000 Deferred ilu_x86r PE 3b0000- 3be000 Deferred gettext_x86r PE 400000- 2695000 Export worldofwarships32 PE 26a0000- 28f3000 Deferred resil_x86r PE 9960000- 9af2000 Deferred wgc_api PE 10000000-1049e000 Deferred vivoxsdk ELF 7a800000-7a939000 Deferred opengl32<elf> \-PE 7a820000-7a939000 \ opengl32 ELF 7ae21000-7ae3c000 Deferred kerberos<elf> \-PE 7ae30000-7ae3c000 \ kerberos ELF 7ae3c000-7ae5b000 Deferred concrt140<elf> \-PE 7ae40000-7ae5b000 \ concrt140 ... ELF 7b2e4000-7b388000 Deferred winex11<elf> \-PE 7b2f0000-7b388000 \ winex11 ELF 7b388000-7b400000 Deferred libgmp.so.10 ELF 7b400000-7b831000 Dwarf kernel32<elf> \-PE 7b420000-7b831000 \ kernel32 ... ELF 7bc00000-7bd2c000 Deferred ntdll<elf> \-PE 7bc10000-7bd2c000 \ ntdll ... ELF 7c429000-7c530000 Deferred msvcr120<elf> \-PE 7c450000-7c530000 \ msvcr120 ELF 7c530000-7c65f000 Deferred msvcp140<elf> \-PE 7c570000-7c65f000 \ msvcp140 ... ELF f7310000-f734a000 Deferred dxgi<elf> \-PE f7320000-f734a000 \ dxgi ELF f734a000-f73ba000 Deferred d3d11<elf> \-PE f7350000-f73ba000 \ d3d11 ... ELF f7f22000-f7f4b000 Deferred ld-linux.so.2 ... --- snip --- Trace log doesn't reveal much. NOTE: The failure for DX12 is expected on my system, stock Bumblebee setup (NVIDIA + Intel GPU) doesn't work with Vulkan. --- snip --- $ pwd /home/focht/wine-games/wineprefix64-wargaming/drive_c/Games/World_of_Warships/bin32 $ WINEDEBUG=+seh,+process,+loaddll,+d3d,+winediag,+d3d11,+dxgi wine ./WorldOfWarships32.exe >>log.txt 2>&1 ... 002a:trace:loaddll:load_native_dll Loaded L"C:\\Games\\World_of_Warships\\bin32\\WorldOfWarships32.exe" at 0x400000: native ... 002a:trace:d3d:wined3d_dll_init Application name WorldOfWarships32.exe\Direct3D. 002a:err:winediag:wined3d_dll_init Setting multithreaded command stream to 1. 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\d3d11.dll" : builtin 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\dxgi.dll" : builtin 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\wined3d.dll" : builtin 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\opengl32.dll" : builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\opengl32.dll" at 0x7a820000: builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\wined3d.dll" at 0xf71d0000: builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\d3d9.dll" at 0xf7520000: builtin 002a:trace:d3d:wined3d_dll_init Application name WorldOfWarships32.exe\Direct3D. 002a:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0. 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\d3d9.dll" : builtin 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\wined3d.dll" : builtin 002a:trace:loaddll:free_modref Unloaded module L"C:\\windows\\system32\\opengl32.dll" : builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\opengl32.dll" at 0x7a820000: builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\wined3d.dll" at 0xf71d0000: builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\dxgi.dll" at 0xf7520000: builtin 002a:trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\d3d11.dll" at 0xf73a0000: builtin 002a:trace:d3d:wined3d_dll_init Application name WorldOfWarships32.exe\Direct3D. 002a:err:winediag:wined3d_dll_init Setting multithreaded command stream to 0. ... 002a:trace:d3d:wined3d_adapter_init_gl_caps adapter 0x19cc50. 002a:trace:d3d:wined3d_adapter_init_gl_caps GL_RENDERER: "GeForce GTX 850M/PCIe/SSE2". 002a:trace:d3d:wined3d_adapter_init_gl_caps GL_VENDOR: "NVIDIA Corporation". 002a:trace:d3d:wined3d_adapter_init_gl_caps GL_VERSION: "4.4.0 NVIDIA 418.56". 002a:trace:d3d:wined3d_parse_gl_version Found OpenGL version 4.4. 002a:trace:d3d:wined3d_check_gl_call Querying context profile call ok /home/focht/projects/wine/mainline-src/dlls/wined3d/adapter_gl.c / 3421. 002a:trace:d3d:wined3d_adapter_init_gl_caps Got a core profile context. 002a:trace:d3d:wined3d_adapter_init_gl_caps GL extensions reported: ... 002a:fixme:d3d11:d3d11_device_CheckFormatSupport iface 0x1bcca8, format 87, format_support 0x33b15c partial-stub! 002a:trace:d3d:wined3d_device_get_wined3d device 0x1c99d8. 002a:trace:d3d:wined3d_device_get_creation_parameters device 0x1c99d8, parameters 0x33b110. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_1D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_2D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_3D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_RENDER_TARGET, resource_type WINED3D_RTYPE_NONE, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_DEPTH_STENCIL, resource_type WINED3D_RTYPE_NONE, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format Requested WINED3D_BIND_DEPTH_STENCIL, but format WINED3DFMT_B8G8R8A8_UNORM is not supported for depth/stencil buffers. 002a:fixme:d3d11:d3d11_device_CheckFormatSupport iface 0x1bcca8, format 87, format_support 0x33b15c partial-stub! 002a:trace:d3d:wined3d_device_get_wined3d device 0x1c99d8. 002a:trace:d3d:wined3d_device_get_creation_parameters device 0x1c99d8, parameters 0x33b110. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_1D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_2D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_SHADER_RESOURCE, resource_type WINED3D_RTYPE_TEXTURE_3D, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_RENDER_TARGET, resource_type WINED3D_RTYPE_NONE, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format wined3d 0x1ae7c0, adapter_idx 0, device_type WINED3D_DEVICE_TYPE_HAL, adapter_format WINED3DFMT_UNKNOWN, usage 0, 0, bind_flags WINED3D_BIND_DEPTH_STENCIL, resource_type WINED3D_RTYPE_NONE, check_format WINED3DFMT_B8G8R8A8_UNORM. 002a:trace:d3d:wined3d_check_device_format Requested WINED3D_BIND_DEPTH_STENCIL, but format WINED3DFMT_B8G8R8A8_UNORM is not supported for depth/stencil buffers. 002a:trace:seh:raise_exception code=c0000005 flags=0 addr=0xc70127 ip=00c70127 tid=002a 002a:trace:seh:raise_exception info[0]=00000000 002a:trace:seh:raise_exception info[1]=00000074 002a:trace:seh:raise_exception eax=0033b244 ebx=07efc39c ecx=00000000 edx=00000000 esi=00000000 edi=250a48dc 002a:trace:seh:raise_exception ebp=0033b228 esp=0033b220 cs=0023 ds=002b es=002b fs=0063 gs=006b flags=00010202 002a:trace:seh:call_stack_handlers calling handler at 0x128e9fe code=c0000005 flags=0 002a:trace:seh:call_stack_handlers handler at 0x128e9fe returned 1 002a:trace:seh:call_stack_handlers calling handler at 0x128e342 code=c0000005 flags=0 002a:trace:seh:call_stack_handlers handler at 0x128e342 returned 1 002a:trace:seh:call_stack_handlers calling handler at 0xa12ed6 code=c0000005 flags=0 002a:trace:seh:_except_handler4_common exception c0000005 flags=0 at 0xc70127 handler=0xa12ed6 0x33aefc 0x33ae5c cookie=22cdb7b4 scope table=0x1755f68 cookies=-2/0,-52/0 002a:trace:seh:_except_handler4_common level 0 prev -2 filter 0xa12824 002a:trace:seh:_XcptFilter (c0000005,0x33ad68) 002a:trace:seh:_except_handler4_common filter returned CONTINUE_SEARCH 002a:trace:seh:_except_handler4_common reached -2, returning ExceptionContinueSearch 002a:trace:seh:call_stack_handlers handler at 0xa12ed6 returned 1 002a:trace:seh:call_stack_handlers calling handler at 0x7b4a0f90 code=c0000005 flags=0 ... --- snip --- I've debugged up to the call site. There is a string reference to "Scaleform::SharedTexture::createTexture - unable to create RenderTarget". That code path is indeed taken. The final crash seems to be sloppy programming (NULL pThis, member deref). --- snip --- 00D92530 | 55 | push ebp | 00D92531 | 8BEC | mov ebp,esp | 00D92533 | 83EC 14 | sub esp,14 | 00D92536 | 8379 3C 00 | cmp dword ptr ds:[ecx+3C],0 | 00D9253A | 56 | push esi | 00D9253B | 8D71 3C | lea esi,dword ptr ds:[ecx+3C] | 00D9253E | 75 56 | jne worldofwarships32.D92596 | 00D92540 | 8B51 28 | mov edx,dword ptr ds:[ecx+28] | 00D92543 | 8D41 0C | lea eax,dword ptr ds:[ecx+C] | ; [ecx+C]:"SharedTexture_RenderedWorld" 00D92546 | 50 | push eax | 00D92547 | 6A 02 | push 2 | 00D92549 | FF71 2C | push dword ptr ds:[ecx+2C] | 00D9254C | 8BCE | mov ecx,esi | 00D9254E | E8 CD79EEFF | call worldofwarships32.C79F20 | 00D92553 | 83C4 0C | add esp,C | 00D92556 | 84C0 | test al,al | 00D92558 | 75 3C | jne worldofwarships32.D92596 | 00D9255A | 833D D8B99E01 10 | cmp dword ptr ds:[19EB9D8],10 | 00D92561 | B8 C4B99E01 | mov eax,worldofwarships32.19EB9C4 | 00D92566 | 68 F0E96801 | push worldofwarships32.168E9F0 | ; "Scaleform::SharedTexture::createTexture - unable to create RenderTarget\n" 00D9256B | 0F4305 C4B99E01 | cmovae eax,dword ptr ds:[19EB9C4] | 00D92572 | 8945 F8 | mov dword ptr ss:[ebp-8],eax | 00D92575 | 8D45 F0 | lea eax,dword ptr ss:[ebp-10] | 00D92578 | 50 | push eax | 00D92579 | C745 F0 00000000 | mov dword ptr ss:[ebp-10],0 | 00D92580 | C745 F4 05000000 | mov dword ptr ss:[ebp-C],5 | 00D92587 | C745 FC 00000000 | mov dword ptr ss:[ebp-4],0 | 00D9258E | E8 7DECD7FF | call worldofwarships32.B11210 | 00D92593 | 83C4 08 | add esp,8 | 00D92596 | 8B0E | mov ecx,dword ptr ds:[esi] | NULL pThis 00D92598 | 8D45 F4 | lea eax,dword ptr ss:[ebp-C] | 00D9259B | 6A 00 | push 0 | 00D9259D | 50 | push eax | 00D9259E | E8 7DDBEDFF | call worldofwarships32.C70120 | *boom* 00D925A3 | 5E | pop esi | 00D925A4 | 8BE5 | mov esp,ebp | 00D925A6 | 5D | pop ebp | 00D925A7 | C3 | ret | --- snip --- Not sure if there is anything useful that can be deduced from this for the D3D folks ;-) Off-topic/on a personal note: I enjoyed that decent game for quite some time (since open beta) .. but Wargaming turned it into a terrible game experience with their CV design/CV rework. I hope many people vote with their money. $ wine --version wine-4.7 Regards -- 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.

2 7