http://bugs.winehq.org/show_bug.cgi?id=28201
Summary: Diablo III D3D error when restarting graphics Product: Wine Version: 1.3.26 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: adys.wh@gmail.com
When restarting the graphic engine in D3, a message box pops up complaining "An error occured reseting D3D. Click OK to retry". Havent found any workaround.
No relevant terminal output when it happens. I have a +d3d trace but it looks quite useless (just a lot of spam, cant really tell when the error happens). What kind of debug channels could be useful?
http://bugs.winehq.org/show_bug.cgi?id=28201
Stefan Dösinger stefandoesinger@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefandoesinger@gmx.at
--- Comment #1 from Stefan Dösinger stefandoesinger@gmx.at 2011-08-27 16:57:49 CDT --- Sounds like something's failing in IDirect3DDevice9::Reset(), a +d3d,+d3d9 log might help. Please kill the game asap after the error, preferably with kill -9 to make sure the game doesn't add too much spam after the problem occurred.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #2 from Jerome Leclanche adys.wh@gmail.com 2011-08-27 19:31:05 CDT --- adys@azura ~ % cat out.txt | grep Reset trace:d3d9:IDirect3DDevice9Impl_Reset iface 0x134098, present_parameters 0xa1bab50. warn:d3d9:reset_enum_callback Resource 0x11187ad0 in pool D3DPOOL_DEFAULT blocks the Reset call.
Killed with wineserver -k a second after the message showed up.
120MB uncompressed, 1600kB compressed. Can't attach it.
http://dedimine.com/public/d3d3dd3d9.txt.bz2
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #3 from Stefan Dösinger stefandoesinger@gmx.at 2011-08-28 03:37:04 CDT --- (In reply to comment #2)
120MB uncompressed, 1600kB compressed. Can't attach it.
lrzip usually does wonders on logfiles.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #4 from Stefan Dösinger stefandoesinger@gmx.at 2011-08-28 04:07:15 CDT --- Created an attachment (id=36127) --> (http://bugs.winehq.org/attachment.cgi?id=36127) Unset the depth stencil before reset
It looks like the unreleased resource is a INTZ depth stencil texture. The d3d9 refcount is 0, so the app did its job and released it, but it still exists in wined3d. The logfile confused me a bit, but the only reason to keep the surface around is if it is currently assigned as depth stencil. This patch unsets the depth stencil before checking if any D3DPOOL_DEFAULT resources are left.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2011-08-28 12:06:54 CDT --- Patch works wonderfully. I do get a few errs tho:
fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. fixme:d3d:resource_check_usage Unhandled usage flags 0x8. err:d3d_surface:surface_set_texture_name Surface has SFLAG_INTEXTURE set, but no texture name. err:d3d_surface:surface_modify_location Surface 0x10543ba8 does not have any up to date location.
http://bugs.winehq.org/show_bug.cgi?id=28201
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2012-03-05 13:51:49 CST --- (In reply to comment #5) Stefan, was this patch ever sent?
http://bugs.winehq.org/show_bug.cgi?id=28201
sleijeri@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sleijeri@gmail.com
--- Comment #7 from sleijeri@gmail.com 2012-03-22 18:45:31 CDT --- This is not prob fully related but i WINEDEBUG=+d3d and it printed following and didnt launch:
trace:d3d:InitAdapters iPixelFormat=135, iPixelType=0x21a0, doubleBuffer=1, RGBA=32/32/0/0, depth=0, stencil=0, samples=0, windowDrawable=0 trace:d3d:InitAdapters iPixelFormat=136, iPixelType=0x202b, doubleBuffer=0, RGBA=16/0/0/0, depth=24, stencil=0, samples=0, windowDrawable=0 trace:d3d:InitAdapters iPixelFormat=137, iPixelType=0x21a0, doubleBuffer=0, RGBA=16/0/0/0, depth=24, stencil=0, samples=0, windowDrawable=0 trace:d3d:InitAdapters iPixelFormat=138, iPixelType=0x202b, doubleBuffer=1, RGBA=16/0/0/0, depth=24, stencil=0, samples=0, windowDrawable=0 trace:d3d:InitAdapters iPixelFormat=139, iPixelType=0x21a0, doubleBuffer=1, RGBA=16/0/0/0, depth=24, stencil=0, samples=0, windowDrawable=0
Might be related to error
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
which im also getting printed all the time also.Havent tested with patch thou.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #8 from sleijeri@gmail.com 2012-03-22 19:20:05 CDT --- (In reply to comment #7) ok i guess there wasnt any special on that print as did later print log file and it started without anyproblem. I can attach the log file if anyone wants to take a look.
http://bugs.winehq.org/show_bug.cgi?id=28201
lyon@pvfree.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |lyon@pvfree.net
--- Comment #9 from lyon@pvfree.net 2012-03-26 12:49:46 CDT --- Guys, any reason why the patch has not been commited yet? Does it need more confirmations?
http://bugs.winehq.org/show_bug.cgi?id=28201
Stefan Dösinger stefan@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefan@codeweavers.com
--- Comment #10 from Stefan Dösinger stefan@codeweavers.com 2012-03-27 04:37:03 CDT --- It needs tests.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #11 from lyon@pvfree.net 2012-03-27 07:18:07 CDT --- Unit tests or real app tests? I might go through some and report.
http://bugs.winehq.org/show_bug.cgi?id=28201
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #12 from Jerome Leclanche adys.wh@gmail.com 2012-03-27 07:19:43 CDT --- Unit tests.
confirming
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #13 from sleijeri@gmail.com 2012-03-27 08:40:25 CDT --- I dunno but tried to patch it against latest 1.4 stable and got following error
patching file dlls/wined3d/device.c Hunk #1 succeeded at 5294 (offset -364 lines). Hunk #2 FAILED at 5753. 1 out of 2 hunks FAILED -- saving rejects to file dlls/wined3d/device.c.rej
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #14 from lyon@pvfree.net 2012-03-27 08:52:50 CDT --- Created attachment 39565 --> http://bugs.winehq.org/attachment.cgi?id=39565 modified for 1.4+
(In reply to comment #13)
I dunno but tried to patch it against latest 1.4 stable and got following error
The code seems to have been changed slightly since then, here's a patch version that's working against 1.4 and 1.5.
http://bugs.winehq.org/show_bug.cgi?id=28201
abel.thorne@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |abel.thorne@free.fr
--- Comment #15 from abel.thorne@free.fr 2012-03-29 11:22:37 CDT --- I have not really tried to launch the game through Wine (I did it but had multiple problems and didn't perform more tests, will try again when out of beta) but this might be a bug related to the game itself and not Wine.
Since the last patch (beta 15), whenever I run the game on Windows, the Diablo III.exe process starts twice, resulting in the same error message (on a grey screen) when the second process start (looks like it can't initialize the display twice). I then have to kill the second process (which hangs, using 33% of CPU usage) before I can switch back to the game normally, display the login screen and log into Battle.net.
The problem has been reported by other players so it is probably a generic bug from the beta version, although it might be specific to some configuration (e.g. only happens with Windows XP, or only happens with the french client).
Has anybody checked if this is the behaviour that happens with Wine?
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #16 from lyon@pvfree.net 2012-03-29 12:39:36 CDT --- (In reply to comment #15)
Has anybody checked if this is the behaviour that happens with Wine?
Yes, as reported by William here: http://bugs.winehq.org/show_bug.cgi?id=28898#c54
And happened to me once as well.
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #17 from lyon@pvfree.net 2012-04-19 05:07:25 CDT --- Stefan, any plans on finishing the tests and pushing the patch in soon?
http://bugs.winehq.org/show_bug.cgi?id=28201
Mike Mestnik cheako+winehq@mikemestnik.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cheako+winehq@mikemestnik.n | |et
--- Comment #18 from Mike Mestnik cheako+winehq@mikemestnik.net 2012-04-24 12:30:16 CDT --- I didn't have this issue and I applied the modified for 1.4+ patch.
Ubuntu Precise binaries available here, only 32bit tested: https://launchpad.net/~cheako/+archive/wine4diabloiii/
http://bugs.winehq.org/show_bug.cgi?id=28201
Alexey Loukianov mooroon2@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mooroon2@mail.ru
--- Comment #19 from Alexey Loukianov mooroon2@mail.ru 2012-05-14 21:13:59 CDT --- I can confirm this bug to affect Diablo III under Wine 1.5.4 on my workstation. Proposed patch fixes the problem, so it might "count" as a real world testing/confirmation that the patch works. Still I'me pretty sure AJ wouldn't accept this patch until we would have some complementing unit tests available in a separate patch.
http://bugs.winehq.org/show_bug.cgi?id=28201
Adam Bolte boltronics@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |boltronics@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=28201
Todd Mokros tmokros@tmokros.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tmokros@tmokros.net
http://bugs.winehq.org/show_bug.cgi?id=28201
--- Comment #20 from Henri Verbeet hverbeet@gmail.com 2012-06-18 15:19:57 CDT --- Should be fixed by 130f232d2049cab5fcdf2c773a7255ff94cc6d33.
http://bugs.winehq.org/show_bug.cgi?id=28201
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |130f232d2049cab5fcdf2c773a7 | |255ff94cc6d33 Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #21 from Jerome Leclanche adys.wh@gmail.com 2012-06-18 22:43:41 CDT --- Confirming fixed
http://bugs.winehq.org/show_bug.cgi?id=28201
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sworddragon2@aol.com
--- Comment #22 from Austin English austinenglish@gmail.com 2012-06-20 17:10:05 CDT --- *** Bug 30968 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=28201
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #23 from Alexandre Julliard julliard@winehq.org 2012-06-22 13:29:38 CDT --- Closing bugs fixed in 1.5.7.
-
wine-bugs＠winehq.org