Renderthread (Command Line Parameter): Difference between revisions
BlackSpectre (talk | contribs) (Created page with "== Command Line Parameter== : {{launchparam|renderthread|options=[0-1]}} Tell the client to use a separate thread for rendering graphics. * 1 = Turn ON thread for rendering. (default) * 0 = Turn OFF thread for rendering. * Unneeded as of Issue 11. '''Note:''' This command enables a thread for all draw calls and anything that touches the OpenGL driver. A thread is dedicated to one CPU core. At the time City of Heroes was live (2004-2012), mos...") |
BlackSpectre (talk | contribs) No edit summary |
||
Line 1: | Line 1: | ||
__NOTOC__ | |||
== Command Line Parameter== | == Command Line Parameter== | ||
: {{launchparam|renderthread|options=[0-1]}} | : {{launchparam|renderthread|options=[0-1]}} |
Latest revision as of 07:39, 22 July 2023
Command Line Parameter
Tell the client to use a separate thread for rendering graphics.
- 1 = Turn ON thread for rendering. (default)
- 0 = Turn OFF thread for rendering.
- Unneeded as of Issue 11.
Note: This command enables a thread for all draw calls and anything that touches the OpenGL driver. A thread is dedicated to one CPU core. At the time City of Heroes was live (2004-2012), most CPUs had either 1 or 2 cores. The command line parameter -renderthread was used to split the single thread for 1 core CPUs into 2 threads for use with 2-core CPUs. One thread was used for rendering graphics, and the other thread for all game logic, input, processing, etc. and Nvidia PhysX objects. The game was updated in Issue 11 to automatically detect systems with 2 CPU cores and in turn automatically enable 2 threads when appropriate. Today, PhysX has been completely split out and now there are 3 main threads that do the vast majority of game processing: one for graphics, one for game logic, etc, and one for PhysX. There are also a few other threads such as the background texture loading thread, geo loading thread, and some created by OS libraries for things like asynchronous networking, but those are relatively low-load and only serve to reduce latency. Using -renderthread 1 to enable multiple threads is unneeded today, however using -renderthread 0 to turn off the graphics rendering thread has some minor use under very specific circumstances, but that is rare.
Example
-renderthread 1
Also
- -renderthread
- -norenderthread
- -userenderscale
- -renderscale
- -renderscalefilter
- -renderscalex
- -renderscaley
- -rendersize