[Bug 29097] New: Worms Armageddon produces a black screen on boot when used with OpenGL DDraw renderer (GDI works fine)
http://bugs.winehq.org/show_bug.cgi?id=29097
Bug #: 29097 Summary: Worms Armageddon produces a black screen on boot when used with OpenGL DDraw renderer (GDI works fine) Product: Wine Version: 1.3.28 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-ddraw AssignedTo: wine-bugs@winehq.org ReportedBy: muzerakascooby@gmail.com Classification: Unclassified
Created attachment 37501 --> http://bugs.winehq.org/attachment.cgi?id=37501 terminal output logs for WA with OpenGL and GDI.
When Worms Armageddon is started with the OpenGL renderer (the default, remember), a black screen is produced. The frontend appears to work despite it (you can hear the menu sound effects when you mouseover/click buttons), but obviously you can't see anything, aside from a few white marks on a few screens that could be the borders to certain controls (which can also be seen when similar bugs occurred for different reasons on Windows). I have not confirmed whether or not ingame works, but I can if it is deemed relevant to the bug - I have a feeling it probably will, because ingame stuff is in general a lot better-coded than the frontend of WA ;).
I've attached the terminal output from running Worms Armageddon with OpenGL first and GDI second so you can compare and contrast - note especially line 7 of the OpenGL output.
As usual, the same bug almost definitely applies to Worms World Party, but due to the difficulty in getting it running with wine (bug 2082), I do not wish to test for sure. (For the record, Worms Armageddon's latest updates have a workaround for bug 2082 that is enabled when wine is detected, but at the cost of being able to minimise once ingame - not usually a problem when you are running in a virtual desktop).
There are no demos of these games that can be run under wine (again, bug 2082), unfortunately, so you'll have to buy Worms Armageddon if you want to test yourself.
Initial discussions of this bug took place in bug 28217.
http://bugs.winehq.org/show_bug.cgi?id=29097
Vladimir Panteleev thecybershadow@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |thecybershadow@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=29097
--- Comment #1 from Murray Colpman muzerakascooby@gmail.com 2011-11-15 18:27:05 CST --- Just tested ingame; it actually doesn't work (nothing appears to be rendered, just blotches of the wine virtual desktop colour). That would probably imply the bug also occurs in Worms 2. I will test Worms 2 tomorrow when I'm actually at my computer (just using VNC at the moment).
(Worms 2, if you didn't know, uses a very similar engine ingame as Worms Armageddon, but has a different frontend made mostly with standard Windows controls and running in a window rather than using DirectDraw. However, the difference is, Worms 2 ingame works normally, whereas running Worms Armageddon ingame without enabling the Use DesktopWindow workaround for bug 2082 causes a black screen. I don't know whether this workaround is inherent in Worms 2's code (as there is no minimise game button in Worms 2, it is possible), or if there is something else going on with this. I will ask a developer.)
http://bugs.winehq.org/show_bug.cgi?id=29097
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |94ae743ea668e49d40ae4e2dc5f | |e1f5d9be018cb
http://bugs.winehq.org/show_bug.cgi?id=29097
--- Comment #2 from Henri Verbeet hverbeet@gmail.com 2011-11-16 11:19:03 CST --- Created attachment 37507 --> http://bugs.winehq.org/attachment.cgi?id=37507 patch
Does this patch help?
http://bugs.winehq.org/show_bug.cgi?id=29097
--- Comment #3 from Murray Colpman muzerakascooby@gmail.com 2011-11-16 14:00:17 CST --- That patch appears to fix the problem.
Having complications in testing Worms 2, as cdemu has died on me, but I am still trying!
http://bugs.winehq.org/show_bug.cgi?id=29097
--- Comment #4 from Murray Colpman muzerakascooby@gmail.com 2011-11-16 15:21:08 CST --- Note that, if Use Desktop Window is disabled (remember, WA normally produces a black screen in this circumstance, even under GDI), the same error as before the patch ("err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for DirectDraw!, expect problems") appears on the screen. Of course, this may be venturing into the territory of bug 2082, I don't know, so feel free to ignore this for now until a if or when a solution for that bug is finally worked out.
http://bugs.winehq.org/show_bug.cgi?id=29097
--- Comment #5 from Henri Verbeet hverbeet@gmail.com 2011-11-18 10:23:50 CST --- Should be fixed by 8e6f5c34a2c657fa714d3d59f7918953dc84d883.
(In reply to comment #4)
Note that, if Use Desktop Window is disabled (remember, WA normally produces a black screen in this circumstance, even under GDI), the same error as before the patch ("err:d3d_surface:d3dfmt_p8_init_palette This code should never get entered for DirectDraw!, expect problems") appears on the screen. Of course, this may be venturing into the territory of bug 2082, I don't know, so feel free to ignore this for now until a if or when a solution for that bug is finally worked out.
Yeah, that sounds like the existing bug.
http://bugs.winehq.org/show_bug.cgi?id=29097
Henri Verbeet hverbeet@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |8e6f5c34a2c657fa714d3d59f79 | |18953dc84d883 Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #6 from Henri Verbeet hverbeet@gmail.com 2011-11-23 11:12:41 CST --- Resolving FIXED.
http://bugs.winehq.org/show_bug.cgi?id=29097
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|directx-ddraw |directx-d3d
http://bugs.winehq.org/show_bug.cgi?id=29097
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2011-12-02 13:33:47 CST --- Closing bugs fixed in 1.3.34.
http://bugs.winehq.org/show_bug.cgi?id=29097
Murray Colpman muzerakascooby@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|FIXED |
--- Comment #8 from Murray Colpman muzerakascooby@gmail.com 2011-12-05 10:57:04 CST --- No, the new version does not fix the bug, reopened.
http://bugs.winehq.org/show_bug.cgi?id=29097
Murray Colpman muzerakascooby@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #9 from Murray Colpman muzerakascooby@gmail.com 2011-12-05 10:58:48 CST --- Apologies, was being completely stupid. Reclosing.
http://bugs.winehq.org/show_bug.cgi?id=29097
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #10 from Dmitry Timoshkov dmitry@baikal.ru 2011-12-05 11:05:26 CST --- Closing again.
-
wine-bugs＠winehq.org