![shaftwhores only by [EXE]dann](/files/avatars/2007/51852-shaftwhore.gif "shaftwhores only by [EXE]dann"){kind=small}
Technical & FPS Stuff
cg_lagometer
The lagometer in the right bottom corner of the screen. Please turn this off (Value: "0"). Ok, it shows you your lag, but you can do nothing against it anyways, and it will divert you from playing. Additionally, it takes away some serious rendering power.
cg_drawFPS
The FPS display in the right upper corner of the screen. The same as the lagometer: Disturbs you & eats FPS. Set it to "0".
cg_scorePlums
This command allows you to enable/disable the little score plums that ascend above the dead body if you kill someone. Not of any use in a serious game. Set to "0" to disable.
com_maxFPS
One of the most important console commands of the game. Caps FPS at the desired value. Most PC's nowadays will be able to display a constant 125 FPS, so the best value should be "125". That's also where you jump highest (when connected to a dedicated server). "125" is better than "120" in this case because "120" caps at 125 FPS anyways.
r_displayRefresh
The refresh rate of your monitor. A 17" should usually be able to do 120 Hz at 640x480 just fine. Set your refresh rate at least to "120" (that's the highest Windows refresh rate for most monitors). Higher values are no mistake though, but as usual, the author is not responsible if you blow your town up through trying to set your monitor refresh rate to 500 :)
pmove_fixed
Changes your movement to a constant 125 FPS movement. DO ONLY use with slower PC's (150 FPS or less in timedemo four) to do some certain jumps (T2 tele jump for example), because it's pretty much a jerky mess. On a fast system with 200 FPS or more in demo four you will notice how jerky your movement will become when setting pmove_fixed to "1". So most users will prefer to let this feature disabled.
m_Filter
If enabled, filters mouse movement. You'll notice the movement of you crosshair will become smoother, which is a nice effect. But, as with every filtering process, the results are inaccurate AND add some lag. So, your aim will not be as precise anymore and additionally the crosshair will lag a bit when first moved. Recommended setting: "0".
cg_lagometer
The lagometer in the right bottom corner of the screen. Please turn this off (Value: "0"). Ok, it shows you your lag, but you can do nothing against it anyways, and it will divert you from playing. Additionally, it takes away some serious rendering power.
cg_drawFPS
The FPS display in the right upper corner of the screen. The same as the lagometer: Disturbs you & eats FPS. Set it to "0".
cg_scorePlums
This command allows you to enable/disable the little score plums that ascend above the dead body if you kill someone. Not of any use in a serious game. Set to "0" to disable.
com_maxFPS
One of the most important console commands of the game. Caps FPS at the desired value. Most PC's nowadays will be able to display a constant 125 FPS, so the best value should be "125". That's also where you jump highest (when connected to a dedicated server). "125" is better than "120" in this case because "120" caps at 125 FPS anyways.
r_displayRefresh
The refresh rate of your monitor. A 17" should usually be able to do 120 Hz at 640x480 just fine. Set your refresh rate at least to "120" (that's the highest Windows refresh rate for most monitors). Higher values are no mistake though, but as usual, the author is not responsible if you blow your town up through trying to set your monitor refresh rate to 500 :)
pmove_fixed
Changes your movement to a constant 125 FPS movement. DO ONLY use with slower PC's (150 FPS or less in timedemo four) to do some certain jumps (T2 tele jump for example), because it's pretty much a jerky mess. On a fast system with 200 FPS or more in demo four you will notice how jerky your movement will become when setting pmove_fixed to "1". So most users will prefer to let this feature disabled.
m_Filter
If enabled, filters mouse movement. You'll notice the movement of you crosshair will become smoother, which is a nice effect. But, as with every filtering process, the results are inaccurate AND add some lag. So, your aim will not be as precise anymore and additionally the crosshair will lag a bit when first moved. Recommended setting: "0".