| Rates |
|---|
|
Rate Settings FAQ (English)
// rate... //------------------------------ You don't need [CL_RATE] so let it be default -9999-. The command [RATE] tells CS how much bytes per second can be sent and received. This command is only important for someone, who has a bandwidth of less than 80000 bits (10000 bytes) per second. On LAN set this value to -25000- or higher. Online most servers have a limitation of 10000 bytes per second (sometimes only -6000-8000- !!). So you can take -10000- or higher as a good value for [RATE]. (to change the server-side maximum rate use [RCON SV_MAXRATE], 0 = no limitation) If your bandwidth is less than 80000 bits per second put this value to [YOUR BANDWIDTH IN BYTES] -1000-. For example: if you've 64000 bits per second (that's max. 8000 bytes per second) take -7000- as the value for [RATE]. LAN: RATE -25000- or higher I-Net (80+ kbit): RATE -10000- or higher I-Net (80- kbit): RATE [BANDWITH IN BYTES] -1000- // cl_updaterate... //------------------------------ You receive updatepackets from the server, they include player positions, actual scores etc. The command [CL_UPDATERATE] sets the maximum number of packets, which can be received per second. More packets will make the game "smoother". You can say it reduces the delay. [CL_UPDATERATE] is also important to reduce CHOKE. CHOKE is, if packets are lost on their way to the client. If you wanna see how much CHOKE you have, put your [NET_GRAPH] on. On LAN try -101- as value. Online most servers limitate this value to -30-. This really sux, but if you are server admin you can try [RCON SV_MAXUPDATERATE] to remove this limitation. Again the bandwidth and rate value are important to see which value is the best for this command. Try -101- with every connection. Then connect to a good(!) server of your choice and put your [NET_GRAPH] on. If you've high CHOKE while playing (I think CHOKE 0-5 is normal) try to reduce the [CL_UPDATERATE] value until you've "normal" CHOKE. High CHOKE at the beginning of a round is normal. Some servers really suck, so it's not always your connection which causes CHOKE. Good values are -101-, -51-, -34-, -26- etc. This is in cause of your FPS. [YOUR FPS] / X + [1] = CL_UPDATERATE I think most players have 100 FPS. If you take 1 for the X you get 100/1+1=101. If you take 2: 100/2+1=51, 3: 100/3+1=34 etc. So the player positions etc. will be updated every frame (CL_UPDATERATE 101), every second frame (CL_UPDATERATE 51), every third frame (CL_UPDATERATE 34) and so on. LAN: CL_UPDATERATE -101- I-Net: CL_UPDATERATE -101-, -51-, -34-, -26- or other values until you've got "normal" CHOKE (0-5). // cl_cmdrate... //------------------------------ It's like [CL_UPDATERATE], but in the other direction. The command [CL_CMDRATE] sets the maximum number of packets, which can be sent per second. A high value will reduce the delay for example the time between your mouseclick (+attack) and the arrival of this command at the server. So you can react faster with a high value. But a low value also has it's advantanges. The delay grows a little bit, BUT your recoil will decrease. REALLY! This is caused by the higher delay, so it's not like spraying - there's more time between the shots in cause of the delay. ;) But in my opinion a good reaction is better than a lower recoil (it's only reduced in the beginning of your spraying, the first five shots or so). So use a high value. On LAN and I-net ALWAYS take -101- as value. But if your normal scoreboard ping grows too much (especially if you use BattleCom or another communication tool) take -51- or -34-. LAN: CL_CMDRATE -101- I-Net: CL_CMDRATE -101-, if the scoreboard ping grows too much try CL_CMDRATE -51- or -34- |
