I'm sure that everyone knows these but I had nothing more to do so...
These are useful config commands if someone feels that keys are "sticky" etc.
As you can see, there are different sensitivity commands for mouse and keyboard..
-controlMap.setButtonRiseTime
-controlMap.SetButtonFallTime
-controlMap.SetDoubleTapTime
-controlMap.keyboardSensitivity [number]
-controlMap.mouseSensitivity [number]
Next two commands are very useful ! (..and almost necessary to operate in other fps games..)
-renderer.drawFps [0,1]
-game.lockFps [framerate]
First test your fps with console command "renderer.drawFps 1" for several maps (best test results when server full..).
Observe the numbers at upper left corner at your screen.
For each map try to find and remember THE LOWEST value.
Then set (lock) your fps in framerate-value for that LOWEST OF ALL value.
You can see and FEEL the result in game playing...
This WOULD help servers work better too (less data to bounce around...)
If you type only "game.lockFps" in console, you will see the value your fps is locked at that moment. As default it was something like 300 or more. That's INSANITY !
I tested 2-3 days for my lowest fps (97..98) at FULL servers and decided to cap it to 85. Works as in the movies
If someone needs more than 85 fps, I would like to hear why. Based on what ? More accuracy etc. are not any real arguments.
These are useful config commands if someone feels that keys are "sticky" etc.
As you can see, there are different sensitivity commands for mouse and keyboard..
-controlMap.setButtonRiseTime
-controlMap.SetButtonFallTime
-controlMap.SetDoubleTapTime
-controlMap.keyboardSensitivity [number]
-controlMap.mouseSensitivity [number]
Next two commands are very useful ! (..and almost necessary to operate in other fps games..)
-renderer.drawFps [0,1]
-game.lockFps [framerate]
First test your fps with console command "renderer.drawFps 1" for several maps (best test results when server full..).
Observe the numbers at upper left corner at your screen.
For each map try to find and remember THE LOWEST value.
Then set (lock) your fps in framerate-value for that LOWEST OF ALL value.
You can see and FEEL the result in game playing...
This WOULD help servers work better too (less data to bounce around...)
If you type only "game.lockFps" in console, you will see the value your fps is locked at that moment. As default it was something like 300 or more. That's INSANITY !
I tested 2-3 days for my lowest fps (97..98) at FULL servers and decided to cap it to 85. Works as in the movies
If someone needs more than 85 fps, I would like to hear why. Based on what ? More accuracy etc. are not any real arguments.