[Bug 58671] New: [Damavand] Sonic3D crashes after the main menu + rendering regression
http://bugs.winehq.org/show_bug.cgi?id=58671 Bug ID: 58671 Summary: [Damavand] Sonic3D crashes after the main menu + rendering regression Product: Wine Version: 10.0 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: user.pecheniok(a)gmail.com Distribution: --- Created attachment 79255 --> http://bugs.winehq.org/attachment.cgi?id=79255 Log from a version with correct rendering The first part of the title is pretty self-explanatory, but the second is a bit more interesting. in the first releases of the 10 series, it used to render correctly, but around wine 10.9-10.10 it started rendering solid colors on top of crashing. Not sure if I'll be able to run a bisect, so I'll maybe try to find some prebuilt versions, but 10.0 rc3 had the game rendering correctly, while 9.21 crashed before launching. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #1 from Zak <user.pecheniok(a)gmail.com> --- Created attachment 79256 --> http://bugs.winehq.org/attachment.cgi?id=79256 Log from 10.14 Most of it is just those lines 01e4:err:d3d:wined3d_context_vk_apply_draw_state No pipeline layout set. 01e4:err:d3d:adapter_vk_draw_primitive Failed to apply draw state. vkd3d:01e4:err:shader_signature_merge Failed assertion: !(e->mask & f->mask) vkd3d:01e4:err:shader_signature_merge Failed assertion: !(e->mask & f->mask) 01e4:err:d3d_shader:shader_spirv_compile_shader Failed to compile shader, ret -4. repeated several thousand times. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 Zak <user.pecheniok(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://gamejolt.com/games/ | |sonic3d/28626 -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 Stian Low <wineryyyyy(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy(a)gmail.com --- Comment #2 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Zak from comment #0)
Not sure if I'll be able to run a bisect, so I'll maybe try to find some prebuilt versions, but 10.0 rc3 had the game rendering correctly, while 9.21 crashed before launching.
GE-Proton has recently become the basis against which I test WineHQ bugs for workarounds. Archives may fulfill some prebuilt wine testing needs: https://github.com/GloriousEggroll/proton-ge-custom/releases It includes patches outside wine-staging which often fix bugs still present for wine-staging alone. Here's how I run it: STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/any/Downloads/GE-Proton9-27/files/share STEAM_COMPAT_DATA_PATH=/home/any/Downloads/GE-Proton9-27/files/share WINEPREFIX=/home/any/Downloads/GE-Proton9-27/files/share/default_pfx/ /home/any/Downloads/GE-Proton9-27/proton waitforexitandrun explorer ~/.wine equivalent will be created at: ~/Downloads/GE-Proton9-27/files/share/pfx Sometimes manually copying ~/Downloads/GE-Proton9-27/files/share/default_pfx as pfx before running the command is required (because the command doesn't copy some files over from default_pfx?) Other times, like for Sonic3D.exe, manually copying default_pfx as pfx isn't necessary (at least for 9-27 release). 9-27 works at 60 FPS. The next release 10-1 crashes at launch. Later versions do not crash at launch but exhibit low FPS thereafter describe by: https://bugs.winehq.org/show_bug.cgi?id=58575 GE-Proton9-27 matching vanilla wine low FPS may suggest something fairly major and significant changed. Bisect still needed to further narrow. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #3 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Stian Low from comment #2)
GE-Proton9-27 matching vanilla wine low FPS may suggest something fairly major and significant changed.
Typo correction: Later releases* matching vanilla wine low FPS may suggest something fairly major and significant changed. GE-Proton9-27 is the last version right before 10 that doesn't crash and runs at 60 FPS. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #4 from Zak <user.pecheniok(a)gmail.com> ---
9-27 works at 60 FPS. The next release 10-1 crashes at launch. Later versions do not crash at launch but exhibit low FPS thereafter describe by: https://bugs.winehq.org/show_bug.cgi?id=58575
A bit confused here, 9.27 is based on wine 9 right? For me it doesn't even launch with the vulkan renderer on wine 9.21 and doesn't run at 60 in wined3d. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #5 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Zak from comment #4)
A bit confused here, 9.27 is based on wine 9 right? For me it doesn't even launch with the vulkan renderer on wine 9.21 and doesn't run at 60 in wined3d.
GE-Proton releases follow and match wine releases so yes, 9-27 is a wine 9.27 build. GE-Proton-9-27 and GE-Proton-9-21 both run it at 60 FPS. Starting GE-Proton-10-1, FPS drops around 10. How are you launching it? With some apps you can just run (for instance): /home/any/Downloads/GE-Proton9-27/files/bin/wine64 explorer However for Sonic3D.exe these errors are thrown without launching via proton: 00d0:err:shell:HCR_GetFolderAttributes should be called for simple PIDL's only! 00d0:fixme:exec:SHELL_execute flags ignored: 0x0000000c 01f0:err:module:import_dll Library libvkd3d-1.dll (which is needed by L"C:\\windows\\system32\\wined3d.dll") not found 01f0:err:module:import_dll Library libvkd3d-shader-1.dll (which is needed by L"C:\\windows\\system32\\wined3d.dll") not found 01f0:err:module:import_dll Library wined3d.dll (which is needed by L"C:\\windows\\system32\\d3d8.dll") not found 01f0:err:module:import_dll Library d3d8.dll (which is needed by L"Z:\\home\\any\\Downloads\\Sonic3D.exe") not found 01f0:err:module:import_dll Library libvkd3d-1.dll (which is needed by L"C:\\windows\\system32\\wined3d.dll") not found 01f0:err:module:import_dll Library libvkd3d-shader-1.dll (which is needed by L"C:\\windows\\system32\\wined3d.dll") not found 01f0:err:module:import_dll Library wined3d.dll (which is needed by L"C:\\windows\\system32\\ddraw.dll") not found 01f0:err:module:import_dll Library ddraw.dll (which is needed by L"Z:\\home\\any\\Downloads\\Sonic3D.exe") not found 01f0:err:module:loader_init Importing dlls for L"Z:\\home\\any\\Downloads\\Sonic3D.exe" failed, status c0000135 Here is the exact command I use to launch Sonic3D.exe: STEAM_COMPAT_CLIENT_INSTALL_PATH=/home/any/Downloads/GE-Proton9-21/files/share STEAM_COMPAT_DATA_PATH=/home/any/Downloads/GE-Proton9-21/files/share WINEPREFIX=/home/any/Downloads/GE-Proton9-21/files/share/default_pfx/ /home/any/Downloads/GE-Proton9-21/proton waitforexitandrun explorer Just replace the path with whatever version of GE-Proton you are using. Proton may patch wined3d and the other files so may differ from vanilla wine to fix issues. However for Sonic3D.exe, even GE-Proton has broken FPS suggesting something major enough changed that it propagates even through all the GE-Proton patches which normally resolve these types of bugs. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #6 from Zak <user.pecheniok(a)gmail.com> ---
How are you launching it?
Just doing a wine Sonic3D.exe in the terminal (I have a separate wineprefix with the vulkan renderer enabled, but that should not matter)
Proton may patch wined3d and the other files so may differ from vanilla wine to fix issues.
However for Sonic3D.exe, even GE-Proton has broken FPS suggesting something major enough changed that it propagates even through all the GE-Proton patches which normally resolve these types of bugs.
Also, I just retested on wine 9.21. You were right, the situation is not as bad as on wine 10, however, there are some severe fps drops at certain points that are present in wine 10 as well, and also a lot of weird stuttering. This is weird, because when I was testing for that bug report you mentioned, wine 9 was running worse than 10, but I'm not sure if I was testing that on X or not because wayland is sometimes 10-15 fps higher with that game. Just retested on 10.0 rc 3 in wined3d before replying. I was kind of shocked, but at least on wayland, it runs at an almost flawless 60 fps with no stutters. Sometimes the hub drops a frame or 2(or more), unlike 8.21, but there are no frame drops in a specific spot both 9.21 and later versions of wine 10 struggle with. You mentioned the game crashing on 10.1, so I think the problem with the performance was introduced there. I will update the appropriate bug report with that. However, this bug report is specifically about problems with the wined3d Vulkan backend, so maybe we should discuss anything related to performance with the OpenGL backend in the other bug report you linked. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #7 from Stian Low <wineryyyyy(a)gmail.com> --- (In reply to Zak from comment #6)
How are you launching it?
Just doing a wine Sonic3D.exe in the terminal (I have a separate wineprefix with the vulkan renderer enabled, but that should not matter)
How are you enabling the wined3d vulkan renderer for the separate wineprefix? `winetricks renderer=vulkan` is the method I typically use for vanilla wine. GE-Proton uses dxvk to supplement broken parts of vanilla wined3d. But yeah it shouldn't matter if you're using default gl renderer for vanilla. The interesting part is GE-Proton uses dxvk but seems to mirror the same FPS drop as the corresponding vanilla wine releases. So whatever is broken seems to be shared between vanilla wine and GE-Proton regardless of the renderers chosen. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #8 from Zak <user.pecheniok(a)gmail.com> --- (In reply to Stian Low from comment #7)
How are you enabling the wined3d vulkan renderer for the separate wineprefix? I set a key in the registry responsible for the backend to vulkan. Don't exactly remember which one right now.
I made quite an interesting discovery today: looks like the bug related to the game is located in the dx8/9 implementation. I tried to use d3d8to9 to promote the game to dx9 or dgVooDoo to promote it to dx11, but it still didn't render correctly. However, with both active at the same time, the game suddenly started rendering correctly and worked at a flawless 60fps even through 2 translation layers. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #9 from Zak <user.pecheniok@gmail.com> --- As of 11 rc1, the game renders correctly again, but still crashes. The last lines in the log now are: 0180:fixme:ddraw:ddraw7_WaitForVerticalBlank iface 0C390B60, flags 0x1, event 00000000 stub! 0180:fixme:mciqtz:MCIQTZ_mciSet MCI_SET_AUDIO_LEFT not implemented yet 0208:err:quartz:BaseMemAllocator_Decommit Waiting: 1 0180:fixme:mciqtz:MCIQTZ_mciSet MCI_SET_AUDIO_LEFT not implemented yet wine: Unhandled page fault on read access to 00000018 at address 7A18DB5B (thread 01e4), starting 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.
http://bugs.winehq.org/show_bug.cgi?id=58671 --- Comment #10 from Zak <user.pecheniok@gmail.com> --- As of wine 11 the game still crashes. I suspect this is related to a wider damavand issue likely specific to d3d9 (because it doesn't happen when running through dgvoodoo) where changing the resolution the game is rendered at results in a crash. That explains why running the game through translation layers avoids the crash: likely the feature is supported in d3d11 but not yet in d3d9. This game changes the rendering resolution when entering the hub, which is where the crash happens. -- 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.
participants (3)
-
WineHQ Bugzilla -
WineHQ Bugzilla -
WineHQ Bugzilla