https://bugs.winehq.org/show_bug.cgi?id=37206
Bug ID: 37206 Summary: Starcraft broodwar stops at the startup screen Product: Wine Version: 1.7.14 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: glenn.schrader@verizon.net Regression SHA1: 7366709d60f42ae09a37548e41c030c5e82fef6a
Created attachment 49458 --> https://bugs.winehq.org/attachment.cgi?id=49458 Log file captured using "WINEDEBUG=all+d3d,ddraw,wgl,x11drv"
The checkin log for the regression SHA1 says "wined3d: Restore the pixel format of the window whose pixel format was actually changed".
The symptom is that when Broodwar starts up it stops at the loading screen. It is not hung since the "Loading" text continues to flash. Left alone, it will stay at this screen forever. The only way I found to get past the startup screen is to manually trigger the screensaver. After the screensaver has started and been terminated, Broodwar gets past the loading screen into the top level game screen. The game will run at this point but there is no GPU acceleration so everything is quite slow.
Note that SHA1 b8569d2f3006bbb14b973eca15a608f9575a0ebd works properly at full speed with no problems (aside from the normal Battlenet issues, etc).
One thing that may or may not have a bearing on this is that I'm running on a dell laptop with a NVIDIA GPU. This laptop only supports a single screen resolution (1440x900). Before NVIDIA dropped re-scaling a while back Broodwar would run full screen with no problem. Afterwards, it would start up in a corner of the screen but I could scale it before starting Broodwar using "xrandr --output LVDS-0 --scale-from 640x480".
I used "export WINEDEBUG=all+d3d,ddraw,wgl,x11drv" to capture diagnostic data while the system was at the startup screen. The log file is attached. Note that the place where the log starts being repetitive is around line 8043.