Post by Filthy_Few ♂ on Jun 6, 2006 7:37:06 GMT -8
If you join The_Few's 66 tickrate server and your own game's client settings aren't set correctly, then you wont get the benefit of the additional tickrate.
The clients rate should = the servers sv_maxrate
The clients cl_updaterate should = the servers sv_maxupdaterate which equals the servers tickrate.
Thus a server with sv_maxrate 10000 tickrate 66 sv_maxupdaterate 66 the clients should run the following settings:
rate 10000
cl_updaterate 66
cl_cmdrate 66
cl_interpolate 1
cl_interp 0.1
cl_smooth 0
****************************************************
If you join The_Few's 100 tickrate server and your own game's client settings aren't set correctly, then you wont get the benefit of the additional tickrate.
The clients rate should = the servers sv_maxrate
The clients cl_updaterate should = the servers sv_maxupdaterate which equals the servers tickrate.
Thus a server with sv_maxrate 30000 tickrate 100 sv_maxupdaterate 100 the clients should run the following settings:
rate 30000
cl_updaterate 100
cl_cmdrate 100
cl_interpolate 1
cl_interp 0.1
cl_smooth 0
****************************************************
1st Open your config.cfg found here >>> C:\Valve\Steam\SteamApps\user_name\counter-strike source\cstrike\cfg and edit with notepad.
IF YOU HAVE LAG ISSUES YOU CAN CHANGE THESE SETTINGS, IF YOU KNOW WHAT YOU ARE DOING!
=== The_Few 66 CSS server rates===
// SET RATES
// Max bandwidth rate allowed on server...
sv_maxrate 10000
// Min bandwidth rate allowed on server...
sv_minrate 0
// Maximum updates per second that the server will allow, increasing this will take more cpu power, 100 is max
sv_maxupdaterate 66
sv_minupdaterate 13
CL_UPDATERATE IS REALLY IMPORTANT. what it does is that in sets how many times per second you the CSS client requests update (you current location, location of your enemy, were shots fired. and etc) information from the server.
cl_updaterate value should be different for every player. Basicly your cl_updaterate value should be same as the lowest fps value that you are getting on the map.
Explanation: for example you cl_updaterate is set at 100, when you get into a battle your fps drop to 45. What is happening now is that the server expects you to send 100 packets per second and you the client are only able to send 45 packets per second. So we have 55 packets at that particular point of time that the server is trying to send to you. This causes your choke to go up and you might experience choppyness and so called skip/back lag.
Also make sure that you cl_cmdrate is set around 20-30 and and cl_cmdbackup is set at 2. Never go with cl_cmdrate lower than 20, otherwise you might get into point blank spray and pray battle with someone and after you die wonder how come you never hit that guy.
Have fun.
PS the higher cl_updaterate you can run at without any choke, the more accurate shot registration you will experience.
The clients rate should = the servers sv_maxrate
The clients cl_updaterate should = the servers sv_maxupdaterate which equals the servers tickrate.
Thus a server with sv_maxrate 10000 tickrate 66 sv_maxupdaterate 66 the clients should run the following settings:
rate 10000
cl_updaterate 66
cl_cmdrate 66
cl_interpolate 1
cl_interp 0.1
cl_smooth 0
****************************************************
If you join The_Few's 100 tickrate server and your own game's client settings aren't set correctly, then you wont get the benefit of the additional tickrate.
The clients rate should = the servers sv_maxrate
The clients cl_updaterate should = the servers sv_maxupdaterate which equals the servers tickrate.
Thus a server with sv_maxrate 30000 tickrate 100 sv_maxupdaterate 100 the clients should run the following settings:
rate 30000
cl_updaterate 100
cl_cmdrate 100
cl_interpolate 1
cl_interp 0.1
cl_smooth 0
****************************************************
1st Open your config.cfg found here >>> C:\Valve\Steam\SteamApps\user_name\counter-strike source\cstrike\cfg and edit with notepad.
IF YOU HAVE LAG ISSUES YOU CAN CHANGE THESE SETTINGS, IF YOU KNOW WHAT YOU ARE DOING!
=== The_Few 66 CSS server rates===
// SET RATES
// Max bandwidth rate allowed on server...
sv_maxrate 10000
// Min bandwidth rate allowed on server...
sv_minrate 0
// Maximum updates per second that the server will allow, increasing this will take more cpu power, 100 is max
sv_maxupdaterate 66
sv_minupdaterate 13
CL_UPDATERATE IS REALLY IMPORTANT. what it does is that in sets how many times per second you the CSS client requests update (you current location, location of your enemy, were shots fired. and etc) information from the server.
cl_updaterate value should be different for every player. Basicly your cl_updaterate value should be same as the lowest fps value that you are getting on the map.
Explanation: for example you cl_updaterate is set at 100, when you get into a battle your fps drop to 45. What is happening now is that the server expects you to send 100 packets per second and you the client are only able to send 45 packets per second. So we have 55 packets at that particular point of time that the server is trying to send to you. This causes your choke to go up and you might experience choppyness and so called skip/back lag.
Also make sure that you cl_cmdrate is set around 20-30 and and cl_cmdbackup is set at 2. Never go with cl_cmdrate lower than 20, otherwise you might get into point blank spray and pray battle with someone and after you die wonder how come you never hit that guy.
Have fun.
PS the higher cl_updaterate you can run at without any choke, the more accurate shot registration you will experience.