Optimal rates to play on this server.

[Missing Lynx]

Perhaps this is the place to let people know what the best settings are for the server,
and how to type them into console.

You know. Tick rate and stuff.

[Missing Lynx]

I found this piece of info written by a guy named Qaddafi Duck.
( I have to admit I changed stuff here and there to make it more clear or understandable)

Setting Rates

Setting your rates is very simple.
In the console, use the following commands for the corresponding rate, substituting the number you want for #:
Rate - rate #
Cmdrate - cl_cmdrate #
Updaterate - cl_updaterate #

use net_graph 3 to view your in, out, ping, and choke
use net_graph 0 to switch it off

Explanation of Rates
Most people do not know what their rates do for them, if they know that there is such a thing as rates.
Rates determine how often you sync with the server.
There are three rates, rate, cmdrate, and updaterate.

Rate is usually in the range of 10000 to 30000.
This is the maximum bytes per second you receive from the server.
Your rate should be determined by your connection.
For example, with a 128k connection, you would be able to receive a maximum of 12800,
256k should be able to receive 25600, and so on.
http://www.testmyspeed.com/ here is a link to test your connection speed.

Cmdrate is usually in the range of 20 to 100.
This is the number of times per second that your computer sends a packet, which is a bundle of information, to the server.
General rule of thumb is to take your rate, divide by 200, and round down for a maximum.
For example, 12800 for a rate would result in a maximum cmdrate of 64.
The most a server can handle varies, our server runs on 66 tick and will handle 66 cmdrate maximum.
Anything over 66 will be treated like 66.
The minimum cmdrate on the server is 20 to prevent players “glitching” and “warping” across the map.

Updaterate is exactly the same as cmdrate but involves the number of packets per second your computer receives from the server.
Again, the minimum is 20 and may go as high as 100.
Remember, however, that the maximum used by our CS:S server is 66 and any value above 66 will be treated as 66.

So setting these both to 100 should also give you smooth play when you are on other servers that may have a 100 tickrate.

To determine your optimum functional rates, use net_graph 3 to view your in, out, ping, and choke while changing rates.
Your in and out will be capped based on your cmd and update rates, your ping will change based on your rate, and choke will change based on the cmd and update rates.
You want to minimize your ping and choke at the same time.
Ping is basically your “lag” in communicating with the server and occurs when your rate is low and you receive less packets per second. Choke occurs when the server detects that you have not received the last packet it sent you and holds packets until the last one it sent reaches you.
Choke is caused by a cmd or update rate that is set too high for your connection, causing a digital traffic jam while the server tries to communicate faster than your computer is capable.

By experimenting with many combinations, you will find the optimal setting for your connection and computer. This optimal setting will greatly enhance your gameplay, from an increase in frames per second to a decrease in ping and choke.

Also, your optimum setting is what is best for the server.
Rates that are too high will cause you to “glitch” or “warp” on the screens of other players, something that is not beneficial to the server by any means.
Rates that are too low will cause the same but you will notice the same “glitching” and “warping” in other players as they notice in you.

This is the reason we must often ask players to change their rates, to make sure the game is fair and fun for everyone.

Last Edit: Feb 6, 2008, 12:23am by Qaddafi Duck