Bug 4476 - Threaded Optimizations on NVIDIA settings produces massive FPS reduction. Can it be at least workarounded if not properly fixed?
Status: RESOLVED INVALID
Alias: None
Product: ioquake3
Classification: Unclassified
Component: Misc
Version: GIT MASTER
Hardware: PC Windows Vista
: P3 major
Assignee: Zachary J. Slater
QA Contact: ioquake3 bugzilla mailing list
URL:
Depends on:
Blocks:
 
Reported: 2010-01-07 19:02 EST by tinkah
Modified: 2010-10-31 05:32:55 EDT
0 users

See Also:


Description tinkah 2010-01-07 19:02:31 EST 
.
Comment 1 tinkah 2010-01-07 19:03:36 EST 
The critical issue with this is that this is a _default_ setting on NVIDIA, hence a major issue for the common user that is pre-informed.
Comment 2 tinkah 2010-01-07 19:04:02 EST 
*isn't.
Comment 3 Zachary J. Slater 2010-10-19 02:19:00 EDT 
Sounds like an NVIDIA bug to me, and my latest check from them hasn't cleared yet.
Comment 4 tinkah 2010-10-31 05:32:55 EDT 
Some insight from

http://gamedev.stackexchange.com/questions/3254/what-is-the-right-process-to-get-compatibility-or-at-least-a-workaround-for-the

"My understanding is that most programs won't have a problem with the feature, which essentially just allows the graphics driver to use an additional thread on multi-cpu systems. It doesn't do anything particularly special, it's just a normal windows thread. This will generally bring a flat increase in FPS.

It can be a problem if something gets in the way of the driver thread by disrupting the windows task scheduler. From looking around it seems like two cases are the primary cause of problems with threaded optimization:

   1. Dealing with the windows message system on multiple threads at once or in a particularly weird way. This can disrupt windows's thread scheduling.
   2. Manually adjusting thread priorities. If you're trying to micromanage thread priorities this can cause a higher priority thread to pop up at a bad time for the driver thread, causing some expensive context switching."