WineHQ
Bug Tracking Database – Bug 34547

 Bugzilla

 

Last modified: 2014-12-31 12:25:47 UTC  

Very slow performance. StarCraft: Brood War.

Bug 34547 - Very slow performance. StarCraft: Brood War.
Very slow performance. StarCraft: Brood War.
Status: CLOSED FIXED
AppDB: Show Apps affected by this bug
Product: Wine
Classification: Unclassified
Component: d3d
1.7.2
x86-64 Linux
: P2 normal
: ---
Assigned To: Mr. Bugs
: regression
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2013-09-18 15:31 UTC by AleXoundOS
Modified: 2014-12-31 12:25 UTC (History)
6 users (show)

See Also:
Regression SHA1: 3c023a5db5538a7622d4518e8ce24d36e1c459b1
Fixed by SHA1: 7052c87358ee3d54fc07cd4ae26f9cc21c530323
Distribution: ---
Staged patchset:


Attachments
patch (754 bytes, patch)
2013-11-29 13:20 UTC, Henri Verbeet
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description AleXoundOS 2013-09-18 15:31:34 UTC
"StarCraft: Brood War" game runs very slow (about 5 fps) including game menu and the game interface itself. Cursor lags too. It's completely unplayable.

When running with "WINEDEBUG=warn+all" console is filled with the same message:
"warn:d3d_perf:wined3d_surface_blt Converted surface, using CPU blit."

Tested hardware:
Intel(R) Pentium(R) D CPU 3.20GHz
NVIDIA Corporation G92 [GeForce 9800 GT] (proprietary driver 325.15, direct rendering enabled)

Important to note that the game works flawlessly with wine-1.5.28 on the same hardware. So it looks as a major regression.
Comment 1 Austin English 2013-09-18 16:49:08 UTC
Please perform a regression test.
Comment 2 Austin English 2013-09-18 16:49:16 UTC
Forgot the link:
http://wiki.winehq.org/RegressionTesting
Comment 3 Goblinstomper 2013-10-13 16:31:42 UTC
Still a problem? I'm unable to reproduce with wine 1.7.4 (although using frglx).
Comment 4 neochronox 2013-10-21 01:03:16 UTC
I also experienced this bug and performed a regression test as suggested:

3c023a5db5538a7622d4518e8ce24d36e1c459b1 is the first bad commit
commit 3c023a5db5538a7622d4518e8ce24d36e1c459b1
Author: Henri Verbeet <hverbeet@codeweavers.com>
Date:   Fri Sep 13 10:18:10 2013 +0200

wined3d: Just set the first render target to NULL in wined3d_device_reset().
Comment 5 Henri Verbeet 2013-11-29 13:20:56 UTC
Created attachment 46674 [details]
patch

Does the attached patch help? I don't think I can quite reproduce the issue, probably because I have a faster CPU, but I can reproduce the +d3d_perf warning, and the patch makes it go away for me.
Comment 6 AleXoundOS 2013-12-02 15:18:23 UTC
Yes, I confirm that the patch takes away the warning messages and the game becomes playable.
Comment 7 Alexandre Julliard 2013-12-06 13:44:26 UTC
Closing bugs fixed in 1.7.8.
Comment 8 Bob Johnson 2014-02-02 01:53:52 UTC
I don't know if this is the appropriate place to post my issue, but I too am having a performance issue with SC: Brood War

For me, with WINEDEBUG=WARN+ALL, I get a screen flooded with

warn:d3d_perf:wined3d_surface_map Mapping a dynamic surface without WINED3D_MAP_DISCARD.
warn:d3d_surface:wined3d_surface_blt D3D not initialized, using fallback

Regression test incoming.
Comment 9 Bob Johnson 2014-02-02 01:55:31 UTC
Forgot I am running 1.7.11-1.
Comment 10 Bruno Jesus 2014-02-02 15:40:01 UTC
(In reply to comment #8)
> I don't know if this is the appropriate place to post my issue, but I too am
> having a performance issue with SC: Brood War> 
> ...
> Regression test incoming.

Please open a new bug report about that, this one is already closed.
Comment 11 Bob Johnson 2014-02-10 07:23:38 UTC
I think that version of Mesa is required, because I just tried to build 10.0.3 with the --disable-shared-dricore option, and it was unrecognized.
Comment 12 Bob Johnson 2014-02-10 07:24:30 UTC
^ Wrong bug, sorry.


Privacy Policy
If you have a privacy inquiry regarding this site, please write to [email protected]

Hosted By CodeWeavers