[Bug 17503] Diablo 2 refuses to detect D3D device
wine-bugs at winehq.org
wine-bugs at winehq.org
Thu Feb 26 07:31:40 CST 2009
http://bugs.winehq.org/show_bug.cgi?id=17503
haarp <liquitsnake at gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |stefan at codeweavers.com
--- Comment #5 from haarp <liquitsnake at gmx.net> 2009-02-26 07:31:39 ---
Heh. I was going to bisect them all, but forgot about it :P
Ok, there are 2 regressions:
It breaks between 1.1.0 and 1.1.1: freezes at 100% CPU load
Then again, starting with 1.1.3 up to current Wine: The D3d test simply fails,
like described at the beginning of this bug. Second regression between 1.1.2
and 1.1.3 reveals:
c1bbab7c54618935d74b7d2b70421253018f5594 is first bad commit
commit c1bbab7c54618935d74b7d2b70421253018f5594
Author: Stefan D��singer <stefan at codeweavers.com>
Date: Thu Aug 7 14:09:19 2008 -0500
ddraw: Send the ddraw output to the clipper window, if any.
:040000 040000 4a60a1c2a59103c9cad3185898bbc59553289b35
f18be73670fd3c5b13d36a1b959fde64c8808fe7 M dlls
cc'ing author aswell
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
More information about the wine-bugs
mailing list