http://bugs.winehq.org/show_bug.cgi?id=9307
Summary: World of Warcraft does not work on wine-0.9.43-52- g308da63 Product: Wine Version: CVS Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-opengl AssignedTo: wine-bugs@winehq.org ReportedBy: vhaarr+wine@gmail.com
Created an attachment (id=7577) --> (http://bugs.winehq.org/attachment.cgi?id=7577) WINEDEBUG=+wgl output
World of Warcraft worked fine on my previous WINE build, 0.9.42 (git tag). Today, when I updated to wine-0.9.43-52-g308da63 (some 40 commits after the 0.9.43 release), WoW stopped working.
Thunderbird on #winehq suggested I file this bug, and also recommended running WoW in D3D mode, which should work while a fix was found for this bug. I haven't tried running it in D3D yet.
As requested by Thunderbird, I attach the output of `WINEDEBUG=+wgl ./wine ~/Games/WoW/WoW.exe 2> dbg.txt' here.
http://bugs.winehq.org/show_bug.cgi?id=9307
--- Comment #1 from Vidar Haarr vhaarr+wine@gmail.com 2007-08-13 16:21:17 --- I forgot to note that WoW doesn't crash or anything, it just spawns a dialog box saying "Your 3D accelerator card is not supported by World of Warcraft. Please install a 3D accelerator card with dual-TMU support.", with an OK button in it, and then exits when I click OK.
http://bugs.winehq.org/show_bug.cgi?id=9307
--- Comment #2 from Vidar Haarr vhaarr+wine@gmail.com 2007-08-13 16:23:04 --- Might also be worth noting that I have set up WoW to run in opengl mode by default, using Config.wtf;
SET gxApi "opengl"
And, like I said, it has been working fine with 0.9.42, until I did a git update and recompiled to 0.9.43-52-g308da63.
Sorry about the spam.
http://bugs.winehq.org/show_bug.cgi?id=9307
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor Keywords| |regression
--- Comment #3 from Lei Zhang thestig@google.com 2007-08-13 18:45:53 --- Can you do a regression test and find the patch that's causing this problem?
http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=9307
Tomas Carnecky tom@dbservice.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tom@dbservice.com
--- Comment #4 from Tomas Carnecky tom@dbservice.com 2007-08-13 19:03:56 --- Bisecting yielded 308da6313ec8dcf0352f312fc1192290cf717f04 as the first bad commit (winex11: Set proper pixel format flags.). The problem is that WoW doesn't like the PFD_SUPPORT_GDI flag which is now being set for all on-screen pixelformats (wine didn't use it before). From MSDN: PFD_SUPPORT_GDI: The buffer supports GDI drawing. This flag and PFD_DOUBLEBUFFER are mutually exclusive in the current generic implementation.. whatever 'current generic implementation' means.
PFD_SUPPORT_GDI was not being set in earlier versions of wine, it was introduced by that bad commit. It is now mapped to GLX_X_RENDERABLE. I will try to disassemble WoW.exe to see where exactly it fails if the flag is set.
http://bugs.winehq.org/show_bug.cgi?id=9307
--- Comment #5 from Tomas Carnecky tom@dbservice.com 2007-08-13 19:50:42 --- Did the disassembly thing: WoW uses only PFs with PFD_DRAW_TO_WINDOW|PFD_SUPPORT_OPENGL set and PFD_SUPPORT_GDI|PFD_GENERIC_FORMAT not set. If WoW finds that the PF doesn't match these exact requirements it will skip and try the next PF. Now since PFD_SUPPORT_GDI is set for all on-screen PFs WoW can't find any suitable PF and fails.
I have a patch ready that makes PFD_SUPPORT_GDI and PFD_DOUBLEBUFFER mutually exclusive (PFD_DOUBLEBUFFER having higher priority), I can submit it to wine-patches, though there have been some concerns in #winehackers whether it's correct to not set PFD_SUPPORT_GDI - wine can render to all on-screen PFs using GDI, so there are no technical reasons not to set it.
http://bugs.winehq.org/show_bug.cgi?id=9307
--- Comment #6 from Vidar Haarr vhaarr+wine@gmail.com 2007-08-14 11:37:15 --- Tested again now with the latest git HEAD (wine-0.9.43-92-g277b254), and the problem persists.
I'm not sure if there have been any commits trying to fix it or not, but I'll be without an internet connection for some time now, so this is the last chance for me to provide any input for weeks.
http://bugs.winehq.org/show_bug.cgi?id=9307
Roderick Colenbrander thunderbird2k@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #7 from Roderick Colenbrander thunderbird2k@gmx.net 2007-08-15 13:27:45 --- The bugfix is in GIT/CVS.
http://bugs.winehq.org/show_bug.cgi?id=9307
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #8 from Dan Kegel dank@kegel.com 2008-01-28 05:24:20 --- Closing all RESOLVED FIXED bugs more than three months old.
http://bugs.winehq.org/show_bug.cgi?id=9307
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |unspecified
-
wine-bugs＠winehq.org