http://bugs.winehq.org/show_bug.cgi?id=16636
Summary: Black & White 2 Graphics Glitches and Crash Product: Wine Version: CVS/GIT Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: ryanshow@gmail.com
Created an attachment (id=18212) --> (http://bugs.winehq.org/attachment.cgi?id=18212) a zipped logfile, made from the command "wine white.exe > bw2err.log 2>&1"
I have the latest wine git as of December 26th 2008. I installed Black and White 2, with both the version 1.1 and 1.2 patches. I also installed the No-CD patch for SecuROM reasons.
The game opens just fine. The menus work great. The intro video works great as well. After the video the game loads and that's where the graphical glitches begin.
It looks as if there are two seperate rendering schemes going on at the same time. One of the schemes only renders the game's water, and the other renders the game's land. I have the game in a 800x600 virtual wine desktop, and the water rendering portion seems to occupy a 640x480 square in the bottom left corner of the game. The rest is occupied by the land rendering. Interactive objects such as the game's "creature" the player hand, and scrolls seem to be unaffected by this issue. I've also attached a screenshot so that what I'm saying might be better understood.
The second issue is that the game crashes not long after selecting a creature. If you skip the tutorial island and go straight to the mainland (by pressing ESC). The game will progress into an in-game video where you're flying over a reddish sea to an island. Half-way to that island the game crashes.
The attached log files seem to indicate that I'm running out of memory, but my computer's memory shouldn't be an issue. I'm running Ubuntu Intrepid 64 bit with 4 gigs of ram and an nVidia 8600 GTS with 512MB of vram.
Also, for some reason when I attempted to direct the output of stdout and stderr to the log file, the debug output wasn't fully captured. I've included the history of my bash prompt so that it shows the debug output of the previous run as well, which had identical results to the one I captured in the log file.