http://bugs.winehq.org/show_bug.cgi?id=14000
Summary: ATI and unable to find a suitable iPixel Format Product: WineHQ Bugzilla Version: unspecified Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: bugzilla-unknown AssignedTo: wine-bugs@winehq.org ReportedBy: celticht32@aol.com CC: celticht32@aol.com
In trying to work through and get Everquest2 to work on my T60p with ATI's latest drivers I kept on getting a unable to find an appropriate iPixel Format.
Debugging the code I found the following in
dll\wined3d\context.c
on line 148 the if statement there is irrelevent because of the line above it. by removing the if around the statment it seems to now have resolved the issue.
here is the fix I did
if(DepthStencilFormat != WINED3DFMT_D24S8) FIXME("Add OpenGL context recreation support to SetDepthStencilSurface\n");
DepthStencilFormat = WINED3DFMT_D24S8;
/* if(DepthStencilFormat) { Changed June 19,08*/ getDepthStencilBits(DepthStencilFormat, &depthBits, &stencilBits); /* } */
Now I do not get the error anymore.
Also I changed line 173 - 181 to one if statement instead of 3 like so :
if ((cfgs->redSize != redBits) || (cfgs->greenSize != greenBits) || (cfgs->blueSize != blueBits) || (cfgs->alphaSize != alphaBits)) continue;
Can others getting the iPixel Format error test the above fix and tell me if it breaks anything or fixes it..
http://bugs.winehq.org/show_bug.cgi?id=14000
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|bugzilla-unknown |directx-d3d Product|WineHQ Bugzilla |Wine Summary|ATI and unable to find a |Everquest2 - unable to find |suitable iPixel Format |a suitable iPixel Format | |with ATI
--- Comment #1 from Lei Zhang thestig@google.com 2008-06-25 11:19:36 --- The product field should be set to "Wine"
http://bugs.winehq.org/show_bug.cgi?id=14000
--- Comment #2 from Vitaliy Margolen vitaliy@kievinfo.com 2008-06-29 00:35:13 --- *** Bug 14072 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=14000
--- Comment #3 from Austin English austinenglish@gmail.com 2008-12-29 10:58:40 --- Is this still an issue in current (1.1.11 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=14000
--- Comment #4 from chris ahrendt celticht32@aol.com 2008-12-30 11:08:12 --- will have to check...
chris
http://bugs.winehq.org/show_bug.cgi?id=14000
--- Comment #5 from Austin English austinenglish@gmail.com 2009-06-30 11:36:32 --- Is this still an issue in current (1.1.24 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=14000
chris ahrendt celticht32@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #6 from chris ahrendt celticht32@aol.com 2009-06-30 12:14:05 --- No this does not occur anymore...
http://bugs.winehq.org/show_bug.cgi?id=14000
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org 2009-07-03 12:19:42 --- Closing bugs fixed in 1.1.25.