http://bugs.winehq.org/show_bug.cgi?id=18657
Summary: Motocross Madness 2 Demo: picture quality in menus changes as mouse moves Product: Wine Version: 1.1.22 Platform: PC URL: http://www.microsoft.com/games/motocross2/default.htm OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: hoehle@users.sourceforge.net CC: aric@codeweavers.com
I know that Aric Stewart's commit prior to wine-1.1.3: eb4ee4f4ada6d02aeb26b0e12964b208ecc68b52 is first bad commit commit eb4ee4f4ada6d02aeb26b0e12964b208ecc68b52 Author: Aric Stewart aric@codeweavers.com Date: Wed Jul 30 10:01:08 2008 -0500 wined3d: Rework surface Blt a bit to only lock the part of the destination surface being drawn to. was already associated with several regressions, e.g. bug #15056, some of which have been fixed since, e.g. bug #12766. Here's a new one, with a possibility that this commit just puts the nail on something that was broken long before[*].
Since Aric's commit, Motocross Madness Demo 2 shows: a) the scene pictures as if downsampled to 8 bits instead of 16/32 in both the terrain selection view as well as the motorcycle selection view in the garage. b) and an extra horizontal garbage line near the bottom of the screen.
What's been fixed again since Aric's commit, as of wine-1.1.22: c) the mini-TV pop up animation to select stunt/motocross etc. mode in the initial menu.
Please compare the AppDB screenshot http://appdb.winehq.org/appimage.php?iId=14073 with my own in bug #17234, comment 6 at http://bugs.winehq.org/attachment.cgi?id=21343 to see a) and b)
These defaults are visible in wine-1.1.21 both with an Intel Xorg driver in Ubuntu as well as with an NVidia 9400 chip in MacOS X.
[*] The color artifacts may be explained as follows, considering the earlier build d4d133f032389f54a45e6c8397a932f0ac47b432
Go to the "single player race event" menu. The scene seems well drawn in 16 or 32 bit depth. However, as the mouse moves to the top 3 tabs, the scene view darkens and looses colours. It looks very much like it was turned into an 8bit picture. and exactly like after Aric's patch. Moving the mouse over it restores the original variety of colours underneath, a "mouse lighting" effect I described in bug #17234.
So an 8/16 bit depth mismatch could explain the observed change of colours.
Hence it is not the case that the later commit from Aric broke everything. It just made the situation degrade, by displaying an 8bit-lookalike picture right from the beginning.
Let's focus on a) and b) here and on the (supposedly) distinct mouse lag issue in bug #17234. Both the trial and the retail version of MCM2 are affected, but the demo is downloadable (40MB).