[Bug 59879] New: FlatOut 2 starts with white screen and shader error popup
http://bugs.winehq.org/show_bug.cgi?id=59879 Bug ID: 59879 Summary: FlatOut 2 starts with white screen and shader error popup Product: Wine Version: 11.10 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: tobias.boesch@googlemail.com Distribution: --- Created attachment 81193 --> http://bugs.winehq.org/attachment.cgi?id=81193 Logs from the console when running the game with both versions. FlatOut 2 starts fine with wine staging 11.9 and doesn't start with wine staging 11.10. I have the FlatOut 2 version 1.2. I cannot reproduce this with the demo, as the demo constantly produces the issue. With the 1.2 release I get the issue only from version 11.10. The FlatOut 2 appdb page (https://appdb.winehq.org/objectManager.php?sClass=version&iId=9406) mentions a bug (https://bugs.winehq.org/show_bug.cgi?id=37676) and relates it to the shader issue. But since I only have the issue when running 11.10, I wanted to create a regression bug report. I cannot relate the mentioned bug to the error popup. I added logs from the console when running the game with both versions. -- 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=59879 tobias.boesch@googlemail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |ArchLinux -- 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=59879 --- Comment #1 from tobias.boesch@googlemail.com --- Adding d3dcompiler_47 through winetricks in wine 11.10 fixes the issue again. (Like mentioned on the FlatOut 2 AppDB page) -- 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=59879 Stian Low <wineryyyyy@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wineryyyyy@gmail.com --- Comment #2 from Stian Low <wineryyyyy@gmail.com> --- (In reply to tobias.boesch from comment #1)
Adding d3dcompiler_47 through winetricks in wine 11.10 fixes the issue again. (Like mentioned on the FlatOut 2 AppDB page)
Confirming native d3dcompiler_47 is still all that is needed to fix launch bugs for wine-11.11-205d055e14a as well as wine-staging-11.11-4d000a90 applied atop. Logs reflect DXVK which is considered 3rd party by wine so ongoing compatibility may not be guaranteed. Only wine's gl/WINED3D builtin renderer currently works similar to DXVK. Wine's vulkan/DAMAVAND builtin renderer aims to remove d3dcompiler native dependency but still has some rendering bugs. Here's some latest screenshots for Flatout2 via latest vkd3d/DAMAVAND showing some remaining rendering bugs: https://bugs.winehq.org/show_bug.cgi?id=59303#c3 -- 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=59879 --- Comment #3 from tobias.boesch@googlemail.com --- (In reply to Stian Low from comment #2) This is just informational, right? I don't find clear requests for help or additional information from my side. (Should I test without dxvk?) -- 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=59879 --- Comment #4 from tobias.boesch@googlemail.com --- After creating this bug, I also found the "shadows are red rendering problem" that is also mentioned in the current test result: https://appdb.winehq.org/objectManager.php?sClass=version&iId=9406 I'll create a separate bug for that, but want to mention it here, maybe it's related. -- 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=59879 --- Comment #5 from Stian Low <wineryyyyy@gmail.com> --- (In reply to tobias.boesch from comment #3)
(In reply to Stian Low from comment #2)
This is just informational, right?
Indeed it is just informational: (In reply to tobias.boesch from comment #4)
After creating this bug, I also found the "shadows are red rendering problem" that is also mentioned in the current test result: https://appdb.winehq.org/objectManager.php?sClass=version&iId=9406
I'll create a separate bug for that, but want to mention it here, maybe it's related.
Bugs for Flatout 2 are well known and reported including red shadows so no need to create a duplicate report. https://bugs.winehq.org/show_bug.cgi?id=50888 https://bugs.winehq.org/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bu... Your report raised concerns for me so I retested Flatout2 because one of my patches to fix/hack swapchains was recently merged with staging so I am just confirming that it did not break Flatout2 which seems bugged in the same way as before so basically no change.
(Should I test without dxvk?)
Testing without dxvk reduces false bug reports because wine considers dxvk out of scope so excluding it from tests helps clarify when bugs are not caused by dxvk and instead what wine considers actual bugs worth fixing. My reports for renderer=gl/WINED3D and vulkan/DAMAVAND are tests without dxvk. -- 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=59879 Ken Sharp <imwellcushtymelike@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |d3d-util URL| |https://games.softpedia.com | |/get/Games-Demo/FlatOut-2-D | |emo.shtml Keywords| |download Severity|normal |minor -- 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=59879 --- Comment #6 from tobias.boesch@googlemail.com --- Thanks for clarifying. I thought because switching wine versions back and forth makes the issue appear and disappear, it is a regression. Although this happens on my machine, if this is a known bug, then I'd close this and mark it a duplicate of https://bugs.winehq.org/show_bug.cgi?id=37676 . -- 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=59879 tobias.boesch@googlemail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #7 from tobias.boesch@googlemail.com --- Duplicate identified. *** This bug has been marked as a duplicate of bug 37676 *** -- 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 (1)
-
WineHQ Bugzilla