http://bugs.winehq.org/show_bug.cgi?id=10081
Summary: City of Heroes does not run if asked to use a dual core processor Product: Wine Version: 0.9.47. Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P3 Component: test AssignedTo: wine-bugs@winehq.org ReportedBy: matthew.b.gerber@gmail.com
If I run CohUpdater.exe with the -renderthread 1 flag to inform it of the presence of a dual-core processor, the game appears to:
* Enter an endless loop (continually spamming SetLayeredWindowAttributes calls to the terminal Wine was run from) rather than finishing loading, and
* Mess up at least part of the Wine registry while doing it (graphics settings are lost after the game and Wine are killed, whereas they're properly saved after a normal session.
CoH is optimized for dual-core processors; top confirms that it isn't detecting the dual-core processor on its own under Wine.
OS: Ubuntu 7.0.4 CPU: Intel Core 2 Duo GPU: nVidia GeForce 6800 Ultra
http://bugs.winehq.org/show_bug.cgi?id=10081
Emmett Hendrick Gonesolo@imagine.ie changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Gonesolo@imagine.ie
--- Comment #1 from Emmett Hendrick Gonesolo@imagine.ie 2008-02-27 15:24:03 --- I can confirm this bug on Fedora 8 (i386) with WINE 0.9.55. With the switch added the game will not even start.
OS: Fedora 8 CPU: Intel Core 2 Duo GPU: nVidia GeForce 8800GTX
http://bugs.winehq.org/show_bug.cgi?id=10081
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|testcases |-unknown
http://bugs.winehq.org/show_bug.cgi?id=10081
Dan grinnz@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #2 from Dan grinnz@gmail.com 2008-05-12 16:34:26 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #3 from Austin English austinenglish@gmail.com 2008-11-12 13:45:04 --- Is this still an issue in current (1.1.8 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #4 from handsomepete jeff.mitchell+WINE@gmail.com 2008-11-12 22:28:38 --- Created an attachment (id=17245) --> (http://bugs.winehq.org/attachment.cgi?id=17245) output of -renderthread 1
Confirmed still present in 1.1.8.
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #5 from handsomepete jeff.mitchell+WINE@gmail.com 2008-11-12 22:43:44 --- Created an attachment (id=17246) --> (http://bugs.winehq.org/attachment.cgi?id=17246) running without -renderthread 1
I did some quick checking around and apparently sometime last year they made -renderthread 1 the default. It appears that it's being disabled automatically though when running via Wine because of: Disabling multi-threaded rendering because ATI drivers are older than 6.6?
running Ubuntu 8.10, Wine 1.1.8, nvidia video, core 2 duo processor. Happy to provide any additional info. Thanks.
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #6 from Austin English austinenglish@gmail.com 2009-05-18 10:45:49 --- Is this still an issue in current (1.1.21 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10081
handsomepete jeff.mitchell+WINE@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeff.mitchell+WINE@gmail.co | |m
--- Comment #7 from handsomepete jeff.mitchell+WINE@gmail.com 2009-05-18 10:53:33 --- I can confirm that this still exists as of 1.1.21 / current git. Still haven't figured out how to send it arbitrary driver info to see if that's the issue or something else is causing it. I'll try to get some fresh logs posted. Any hints on good debug flags for this?
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #8 from Austin English austinenglish@gmail.com 2009-11-19 12:52:18 --- This is your friendly reminder that there has been no bug activity for 6 months. Is this still an issue in current (1.1.33 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #9 from handsomepete jeff.mitchell+WINE@gmail.com 2009-11-21 06:43:03 --- Still present in 1.1.33. Any hints as to debug an app that just goes out to lunch and doesn't come back would be appreciated.
http://bugs.winehq.org/show_bug.cgi?id=10081
Ove Kaaven ovek@arcticnet.no changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ovek@arcticnet.no
--- Comment #10 from Ove Kaaven ovek@arcticnet.no 2010-05-16 11:17:25 --- In the latest CoH/CoV update, renderthread 1 has apparently been made default (probably the reason for #22561).
I see the hang is because the renderthread tries to do SetPixelFormat, but Wine's implementation of SetPixelFormat sends a Wine-specific message to the game window, which is owned by the main thread (not the render thread). In the meantime, the main thread is running a tight loop doing Sleep() calls until the render thread is done initializing, and does not process window messages.
http://bugs.winehq.org/show_bug.cgi?id=10081
dlzerocool dl.zerocool@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dl.zerocool@gmail.com
--- Comment #11 from dlzerocool dl.zerocool@gmail.com 2012-02-12 10:07:52 CST --- I really wish to help, I have tried to display relay and tip to see what's going on, but I am unable to find where the call is made.
I took a look at the SetPixelFormat on painting.c but I don't see how it's possible that the render thread don't receive it, but the main window does.
If you have more information I'll be glad to help.
http://bugs.winehq.org/show_bug.cgi?id=10081
--- Comment #12 from Ove Kaaven ovek@arcticnet.no 2012-02-12 11:27:03 CST --- (In reply to comment #11)
While I appreciate the sentiment, this problem is closely linked to Wine's design, and takes some fairly deep understanding. If you aren't a good enough programmer to understand this problem when it has already been diagnosed, then you're certainly not qualified to fix it. Even a qualified programmer would probably not try to fix it without proposing and discussing possible solutions with Alexandre himself. If this bug is important to you, the best you can do is probably to remind the core developers of the problem.
http://bugs.winehq.org/show_bug.cgi?id=10081
Mark Wagner mark+winebugs@carnildo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mark+winebugs@carnildo.com
--- Comment #13 from Mark Wagner mark+winebugs@carnildo.com 2013-05-25 17:24:15 CDT --- This appears to be fixed as of Wine 1.5.30. I can now run City of Heroes and the standalone Icon costume creator without needing to specify the "-renderthread 0" command-line option.
https://bugs.winehq.org/show_bug.cgi?id=10081
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #14 from Austin English austinenglish@gmail.com --- (In reply to Mark Wagner from comment #13)
This appears to be fixed as of Wine 1.5.30. I can now run City of Heroes and the standalone Icon costume creator without needing to specify the "-renderthread 0" command-line option.
Fixed.
https://bugs.winehq.org/show_bug.cgi?id=10081
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #15 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 1.7.32.
-
wine-bugs＠winehq.org