Changeset 8505

Timestamp:

May 19, 2011, 3:18:44 AM (14 years ago)

Author:

rgrieder

Message:

Do not limit the main thread to the first Core/CPU on Windows. It might slow down the game by a percent or two because Ogre forces the program to reside in the first core when it queries the time, hence potentially rescheduling the application.
On the other hand, limiting the application's main thread to one core has drawbacks when starting Orxonox multiple times without taking care of it by specifying —limitToCPU #.

File:

• code/trunk/src/libraries/core/Core.cc (modified) (1 diff)

code/trunk/src/libraries/core/Core.cc

@@ -86 +86 @@
 
 #ifdef ORXONOX_PLATFORM_WINDOWS
-    SetCommandLineArgument(limitToCPU, 1).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is the first core (faster than off)");
+    SetCommandLineArgument(limitToCPU, 0).information("Limits the program to one CPU/core (1, 2, 3, etc.). Default is off = 0.");
 #endif