http://bugs.winehq.org/show_bug.cgi?id=15449
Summary: WoW WotLK crashes when entering the world on ati graphic cards Product: Wine Version: 1.1.5 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: gwydion.dot@morrigan.ch
Created an attachment (id=16333) --> (http://bugs.winehq.org/attachment.cgi?id=16333) Wine log
WoW WotLK crashes when entering the world on ati graphic cards. This happens when using opengl mode or directx mode.
System: AMD64 Phenom ATI 4870 with Catalyst 8.9 Debian Lenny AMD64
OpenGL: Game crash cause of minimap error. Played with config file and xorg.conf there is no solution to fix it.
Please check attachment 1, 2, 3 and 4 for more details.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #1 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:38:46 --- Created an attachment (id=16334) --> (http://bugs.winehq.org/attachment.cgi?id=16334) WoW internal log
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #2 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:39:25 --- Created an attachment (id=16335) --> (http://bugs.winehq.org/attachment.cgi?id=16335) WoW config
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #3 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:40:07 --- Created an attachment (id=16336) --> (http://bugs.winehq.org/attachment.cgi?id=16336) xorg config
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #4 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:43:17 --- Direct X:
Game crash too on character selection. This time a with a "The memory could not be "written".".
See attachment 5 and 6 for more details.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #5 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:43:58 --- Created an attachment (id=16337) --> (http://bugs.winehq.org/attachment.cgi?id=16337) WoW internal log in DX mode
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #6 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-28 16:44:14 --- Created an attachment (id=16338) --> (http://bugs.winehq.org/attachment.cgi?id=16338) Wine log in DX mode
http://bugs.winehq.org/show_bug.cgi?id=15449
Manuel Gysin gwydion.dot@morrigan.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|manuel |
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #7 from Manuel Gysin gwydion.dot@morrigan.ch 2008-09-30 20:52:51 --- Got DX9-Mode working with:
[Software\Wine\Direct3D]
"DirectDrawRenderer"="opengl" "OffscreenRenderingMode"="fbo" "PixelShaderMode"="enabled" "VertexShaderMode"="hardware" "UseGLSL" = "disabled"
OpenGL is still crashing.
http://bugs.winehq.org/show_bug.cgi?id=15449
Josh Jones joshorjeff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |joshorjeff@gmail.com
--- Comment #8 from Josh Jones joshorjeff@gmail.com 2008-10-01 14:34:26 --- The minimap render target bug is also affecting PTR builds. It looks similar to this bug: http://bugs.winehq.org/show_bug.cgi?id=2603
However I've looked through old fixes for that bug and nothing has worked for me on the PTR (I dont have a beta key but this looks like the same issue). I've tried the "original" addon that hides the minimap, and tried to make my own. But I guess it still gets loaded in a way that causes the error before it gets hidden. -d3d mode works alright for me (Radeon X1650, fglrx 8.47.3 wine 1.1.4) but the framerate really is too low for an enjoyable playing experience. I'm downloading the latest PTR patch now but I doubt it will fix anything.
I've not really added much here to what others have already said, but I think its worth pointing out that the PTR is affected, considering its changes will be on the live servers presumably within a few weeks.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #9 from Roderick Colenbrander thunderbird2k@gmx.net 2008-10-03 14:33:10 --- Attach a log using WINEDEBUG=+wgl. I suspect that WoW wants to use pbuffers for the minimap (at least on Nvidia it uses pbuffers for some stuff) but ATI doesn't offer this anymore since a while.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #10 from Josh Jones joshorjeff@gmail.com 2008-10-03 16:07:31 --- Created an attachment (id=16451) --> (http://bugs.winehq.org/attachment.cgi?id=16451) Minimap render target crash with WINEDEBUG=+wgl
"trace:wgl:X11DRV_SwapBuffers (0x13e570)" line is repeated continually while the game is running in the char select screen, login screen, etc. but everything seems fine.
http://bugs.winehq.org/show_bug.cgi?id=15449
Josh Jones joshorjeff@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #16451|application/octet-stream |text/x-log mime type| |
http://bugs.winehq.org/show_bug.cgi?id=15449
Lei Zhang thestig@google.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #16451|text/x-log |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #11 from Manuel Gysin gwydion.dot@morrigan.ch 2008-10-06 13:12:43 --- Created an attachment (id=16509) --> (http://bugs.winehq.org/attachment.cgi?id=16509) Wine log in OpenGL mode
Tested with newest ptr patch with the ati catalyst 8.9.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #12 from Josh Jones joshorjeff@gmail.com 2008-10-07 11:52:20 --- Can anyone think of a way to disable the minimap entirely, rather than just hiding it with an addon which doesn't seem to solve the problem. It seems that the bug is directly associated with the minimap. In old WoW releases you could override parts of the Blizzard lua code using a FrameXML folder, but nowadays this seems to just renamed at each run to FrameXML.old and ignored.
Since the patch will probably be released in a week or two, I'm keen to find a way to continue playing without having to shell out early for a new graphics card.. :)
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #13 from Manuel Gysin gwydion.dot@morrigan.ch 2008-10-07 12:48:49 --- This will not solve the problem. I tested some addons that hide the minimap but the minimap will be rendered in 3.0 too when it's not displayed.
What we need (until ati fix it) is a hack that says that the minimap would be rendered.
But I'm not familiar with wine hacking and so I don't know where to changes the lines of code.
http://bugs.winehq.org/show_bug.cgi?id=15449
Michael jacobs.48@wright.edu changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jacobs.48@wright.edu
--- Comment #14 from Michael jacobs.48@wright.edu 2008-10-11 18:00:34 --- I'm an ATI user who was getting this same error. I was able to get around this by finding the source of the error in Wow.exe and disabling the entire subroutine.
The has gotten around the error but disabled the minimap entirely.
Other than no minimap the game seems to be running fine. Haven't encountered any errors yet.
Here is the edited Wow.exe file:
WARNING: Use this entirely at your own risk. No idea if this could potentially get you banned but I haven't been yet. Make sure you have a backup of wow.exe
ALSO: I've only tested this to work with WotLK Beta version 3.0.2.9061 and so I have no idea if it'll work with later versions.
http://files.filefront.com/atifixedwowexe/;12039262;/fileinfo.html
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #15 from Manuel Gysin gwydion.dot@morrigan.ch 2008-10-11 23:42:49 --- Nice work but I think this is the wrong way to solve it.
Do you know which method are called within wine?
Maybe we can hack there something, we only need at the end that wow thinks all is right.
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #16 from Josh Jones joshorjeff@gmail.com 2008-10-12 09:39:51 --- I believe the issue with fglrx at the moment is that pixelbuffer support is broken. And the minimap uses pbuffers (thats why its white indoors). At least thats what I've read :)
Unfortunately I know pretty much nothing about DirectX and similarly nothing about the wine source code. I guess we need to find where wine queries for pbuffer support and work from there?
I'm looking at dlls/wined3d/texture.c, specifically this bit:
static HRESULT WINAPI IWineD3DTextureImpl_GetSurfaceLevel(IWineD3DTexture *iface, UINT Level, IWineD3DSurface** ppSurfaceLevel)
But I've never even looked at DirectX programming before. Am I in the right area?
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #17 from Manuel Gysin gwydion.dot@morrigan.ch 2008-10-12 17:54:19 --- I'm not sure (can't fine the fav's to the patches) but I think the file dlls/winex11.drv/opengl.c is it.
More information on pbuffer, ati and wine:
http://bugs.freedesktop.org/show_bug.cgi?id=12054 http://bugs.winehq.org/show_bug.cgi?id=11826#c19
Very old ati patch:
http://www.winehq.org/pipermail/wine-patches/attachments/20060915/9be67c90/x... http://www.winehq.org/pipermail/wine-patches/2006-September/030669.html
http://bugs.winehq.org/show_bug.cgi?id=15449
--- Comment #18 from Michael jacobs.48@wright.edu 2008-10-14 20:09:21 --- I do realize that this is entirely the wrong way to go about solving this but as someone who is trying to teach myself assembly language I decided to have another go at it with the disassembler.
This time around instead of disabling the entire subroutine I found where exactly it was checking for the errors and tried disabling each of the two comparisons. By disabling the first I was able to get around the error without disabling the minimap.
Here's my revised wow.exe file with (at least for me) a working minimap:
Again, disclamers:
WARNING: Use this entirely at your own risk. No idea if this could potentially get you banned but I haven't been yet. Make sure you have a backup of wow.exe
ALSO: I've only tested this to work with WotLK Beta version 3.0.2.9061 and so I have no idea if it'll work with later versions.
http://files.filefront.com/fixedminimapwowexe/;12062918;/fileinfo.html
http://bugs.winehq.org/show_bug.cgi?id=15449
Adys adys.wh+winehqdotorg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh+winehqdotorg@gmail.c | |om
--- Comment #19 from Adys adys.wh+winehqdotorg@gmail.com 2009-01-23 00:51:44 --- (In reply to comment #16)
I believe the issue with fglrx at the moment is that pixelbuffer support is broken. And the minimap uses pbuffers (thats why its white indoors). At least thats what I've read :)
Unfortunately I know pretty much nothing about DirectX and similarly nothing about the wine source code. I guess we need to find where wine queries for pbuffer support and work from there?
I'm looking at dlls/wined3d/texture.c, specifically this bit:
static HRESULT WINAPI IWineD3DTextureImpl_GetSurfaceLevel(IWineD3DTexture *iface, UINT Level, IWineD3DSurface** ppSurfaceLevel)
But I've never even looked at DirectX programming before. Am I in the right area?
I don't get it -- is this a bug in Wine or in ATI drivers then? If Wine is not in fault, best to close this, no?
http://bugs.winehq.org/show_bug.cgi?id=15449
Manuel Gysin gwydion.dot@morrigan.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |WONTFIX
--- Comment #20 from Manuel Gysin gwydion.dot@morrigan.ch 2009-01-23 17:20:48 --- It's an ATI bug!
http://bugs.winehq.org/show_bug.cgi?id=15449
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Austin English austinenglish@gmail.com 2009-01-26 03:02:08 --- Closing.
-
wine-bugs＠winehq.org