http://bugs.winehq.org/show_bug.cgi?id=11674 --- Comment #143 from Aigars Mahinovs <aigarius(a)gmail.com> 2011-11-04 16:23:30 CDT --- I would have grave suspicions about timing and synchronization errors as the draw functions return much sooner that programs expect them to and also return before anything is actually drawn. This could also lead to games falsely claiming higher FPS that is actually shown in cases where you can accept 100 frames per second worth of draw requests, but you can't actually manage to show all of them in that time, so the queue just grows until you start getting huge latency between an action happening in the game and actually showing up on the screen. The games measure FPS exactly for the purpose of preventing that - frames are dropped so that the time between an action happening in the game engine and showing it on screen is never delayed by a queue of frames to be rendered. I'd rather see the multi-core identification issue fully solved. If WoW does not manage to figure out that there is more than one core, then they actually turn off all the multi-core optimizations that they already have in there. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.