The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
RE: Game window is not displayed
by Hew McLachlan on Saturday May 16th 2009, 4:11
I'm having the same problem (no game window and 100% CPU), but I downgraded to wine-1.0.1 and the problem still exists, so I suspect it's something other than Wine. Note that there are test results that indicate wine-1.1.21 works fine for others. I'm running Ubuntu Jaunty; I hope to investigate this further when I switch to Karmic shortly.
RE: Game window is not displayed
by Chris on Saturday May 16th 2009, 8:30
Pixel shaders for GW are broken for me in 1.1.21. Disable them in winecfg and see if the game will start--if that doesn't work roll back to 1.1.20, where pixel shaders are working good. This is on a gentoo system with a 9800GT.
RE: Game window is not displayed
by Øyvind on Saturday May 16th 2009, 11:06
Same thing happens to me. Game crashes with:
err:d3d:getColorBits Unsupported format: WINED3DFMT_R32_FLOAT
err:seh:raise_exception Exception frame is not in stack limits => unable to dispatch exception.
if pixel shaders are enabled.
You can also try to start the game with the -dx8 switch (though the graphics won't look as good.)
RE: Game window is not displayed
by Damian Pound on Friday April 8th 2011, 16:20
To fix this as mentioned by killpotts at (bugs.winehq.org/show_bug.cgi?id=16783#c4), just replace the Gw.dat or delete it and run GW to create a new one. My addition is to use this command to reduce wear on the drive:
rsync -v --progress --partial --inplace [path to Gw.dat on cd] [path to installed Gw.dat]
Don't expect the time to copy to decrease by much though because the fastest a CD can be read is about 10MiB, while the R/W speeds of a hard drive are around 60MiB (although mine tends to be 30R/20W).
