http://bugs.winehq.org/show_bug.cgi?id=24405
Summary: Midnight Club 2 runs too fast Product: Wine Version: 1.3.2 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: jrstone88@gmail.com
Midnight Club 2 has what feels like a clockspeed issue causing the game to run very fast making the menus hard to navigate and the game difficult to play. Setting the nvidia graphics driver to sync to vBlank does not help.
http://bugs.winehq.org/show_bug.cgi?id=24405
--- Comment #1 from James Stone jrstone88@gmail.com 2010-09-14 21:47:01 CDT --- Created an attachment (id=30761) --> (http://bugs.winehq.org/attachment.cgi?id=30761) Debug Output from Midnight Club 2
http://bugs.winehq.org/show_bug.cgi?id=24405
--- Comment #2 from Andrew Nguyen arethusa26@gmail.com 2010-09-14 21:52:37 CDT --- Presumably you have CPU frequency scaling enabled; does pegging the CPU to a single clock speed help? If so, it's not a defect in Wine but rather an issue with older games that try to time the CPU but don't account for CPU scaling.
http://bugs.winehq.org/show_bug.cgi?id=24405
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #3 from Wylda wylda@volny.cz 2010-09-15 00:49:16 CDT ---
I have similar problem in bug 24368. Any chance you could test wine-1.1.7?
http://bugs.winehq.org/show_bug.cgi?id=24405
--- Comment #4 from James Stone jrstone88@gmail.com 2010-09-15 11:19:11 CDT --- (In reply to comment #2)
Presumably you have CPU frequency scaling enabled; does pegging the CPU to a single clock speed help? If so, it's not a defect in Wine but rather an issue with older games that try to time the CPU but don't account for CPU scaling.
Yes I do, retested pegging all CPU's at max frequecy and the menus still run at warp speed but the gameplay was now at normal speed. Pegging the CPU's at auything less than max frequency caused the gameplay to run slow (menus unaffected). The game doesn't run consistently under the same conditions though, I was able to get one lucky time with the menus and everything ran at the right speed. I closed down the game and restarted under the same condition and everything was running too fast, and this is at the constant max CPU frequency! I'll test this game in a native windows to try and isolate the issues of running the game in wine under linux.
http://bugs.winehq.org/show_bug.cgi?id=24405
James Stone jrstone88@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from James Stone jrstone88@gmail.com 2010-09-15 13:29:07 CDT --- (In reply to comment #4)
(In reply to comment #2)
Presumably you have CPU frequency scaling enabled; does pegging the CPU to a single clock speed help? If so, it's not a defect in Wine but rather an issue with older games that try to time the CPU but don't account for CPU scaling.
Yes I do, retested pegging all CPU's at max frequecy and the menus still run at warp speed but the gameplay was now at normal speed. Pegging the CPU's at auything less than max frequency caused the gameplay to run slow (menus unaffected). The game doesn't run consistently under the same conditions though, I was able to get one lucky time with the menus and everything ran at the right speed. I closed down the game and restarted under the same condition and everything was running too fast, and this is at the constant max CPU frequency! I'll test this game in a native windows to try and isolate the issues of running the game in wine under linux.
Tested on Windows Vista, same speed inconsistency showed up, not a wine bug, closing.
http://bugs.winehq.org/show_bug.cgi?id=24405
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Dmitry Timoshkov dmitry@codeweavers.com 2010-09-15 22:52:48 CDT --- Closing invalid.