|
|
|
#1 (permalink) | |||||||||||
|
PC Gamer
|
Since some of you guys are having problems with laggin in the CS:S server i decided this might be the reason. People also have been askin me what the rates stand for i researched some of the topics and found this out, hope this helps the server get less laggier
(this should help prevent rubber knifes) ![]() rate sets the data transfer speed between the client and the server. 20,000 is the maximum rate, and should be used for all connections 256k and above. rate 30000 ( Or 20000 I forget but Ithink 30000 should work better) cl_cmdrate controls the number of packets sent to the server per second. This should be set to 100 (maximum) for LAN and broadband connections. cl_cmdrate 100 cl_updaterate controls the number of packets requested from the server per second. This should be set to 100 (maximum) for LAN and broadband connections. cl_updaterate 100 cl_interp_ratio is the new system for interpolating player positions on the server timescale. It is now based on a calculation with cl_updaterate and has brought the time gap between fast and laggy players closer together. On a 100 tickrate server, and a good client connection, this should be set to 1. cl_interp_ratio 1 Personally, i like to keep everything even, and use fps_max 100 as well. If you send and receive 1 packet for every frame, i believe it feels smooth and has good bullet registration. fps_max 100 Net_graph 3 This shows your fps, ping, bps, etc. Or maybe this that i found on another site: Btw dunno if this helps or not, tell me if this is right or wrong, found it in a fpsbanana tutorial Here it is: Rate This is your download speed in bytes / second. If you know your advertised speed in kbIps (like a 56k is actually 56kbIps), then all you have to do is divide your speed by 8 and multiply it by 1024. Like this: 56 / 8 = 7 kbYtes/sec (1 byte = 8 bits) 7 * 1024 = 7168 bYtes/sec (1 kbyte = 1024 bytes) Your rate would be: rate 7168 You should know you will never download @7168, because thats the maximum theoretical limit. Instead, you should be realistic and take 90% of the theoretical limit to get the download speed you would get on most servers. 90% of 7168 = 7168 * 0.9 = 6451 rate 6451 That's about right, and should work best if you have a 56k dialup modem. cl_updaterate This is the amount of times you receive updates from the server per second. In a heavy firefight the largest packets can be up to 180 bytes. (A packet is a bit of information that you receive). If we divide our rate by the largest packet size, we'll get our cl_updaterate. 6451 / 180 = 36 cl_updaterate 36 We dont need to take 90% of the updaterate, because we've already done that in the rate calculation. cl_cmdrate This is like cl_updaterate only that it's the amount of times you send updates to the server. The largest packet size that you (the client) send to the server is something like 30 bytes. So we should divide cl_rate by the largest packet size we send through: 14746 / 30 = ~491 Now, you can't send 491 updates per second to the server . It's almost impossible for the server to handle all those packets. What CSS has done, is limit cl_cmdrate to 100 So if you calculate cl_cmdrate and its bigger than 100, change it to 100 cl_cmdrate 100 That's more than fast enough for most ppl. ============================================= ============================================= That was the first part, I think all I said there has been said before, and perhaps better than I explained it. But now comes the bit everyone forgot to mention! The server you connect to has maximum and minimum rates. It means that your specially calculated rates wont work properly and youll get choke and loss. How should you fix this? Well, currently you can only do this by looking up the max rates of the server, and recalculating rates after youve got the servers max rates. Ill explain how: 1/ First connect to a server 2/ Open console with "~" 3/ Type: sv_maxrate 4/ Press enter 5/ You should see a message in console displaying sv_maxrate xxxx Now that you've got the servers max rate, you know your own max rate aswell, the server limits your rate to his own max rate. So now we have to adjust our own rates. Lets say sv_maxrate was 10000 sv_maxrate 10000 Our rate should then also be 10000 (if your rate is less than sv_maxrate, you dont need to do any more calculations, you have the best rates for your connection). What we need to change is our cl_updaterate to avoid choke. So we need to calculate cl_updaterate based on a rate of 10000 10000 / 180 = 56 cl_updaterate 56 That will be our new cl_updaterate. After you've done that, you have calculated the best possible rates for the server you are on. All you have to do is type "cl_updaterate 56" in console. If you still experience choke or loss, lower your cl_update and cl_cmdrate, not your rate. Or DPs website http://www.fishtankclan.com/e107_plu...php?content.44
__________________
I'm a gamer. PERIOD. These days everyone plays some kind of game...But I'm a true Gamer, 'TIL I Die. LUCK = Preparation + Opportunity CSS Name: [OCN] Lucky Killz|╗ Knifing Maniacs Club
Last edited by luckykillz : 05-11-08 at 08:55 PM. |
|||||||||||
|
|
|
|
|
#2 (permalink) | ||||||
|
Audiophile
Join Date: May 2007
Location: 51°23'56.77"N x 1° 4'11
Posts: 948
Rep: 44
![]() Unique Rep: 38
Trader Rating: 0
|
rate 30000
cl_cmdrate 101 cl_updaterate 101 ^ sorts all your troubles (:
__________________
Failure.
|
||||||
|
|
|
|
|
#3 (permalink) | |||||||||||
|
PC Gamer
|
close enough
![]() Cl_cmdrate 100 seems like a more even number that 101, makes it look prettier lol
__________________
I'm a gamer. PERIOD. These days everyone plays some kind of game...But I'm a true Gamer, 'TIL I Die. LUCK = Preparation + Opportunity CSS Name: [OCN] Lucky Killz|╗ Knifing Maniacs Club
|
|||||||||||
|
|
|
|
|
#5 (permalink) | |||||||||||||
|
Overclocker
|
cl_cmdrate should be 85% of your max fps.
therefore cl_cmdrate 85. my source comes from google... i searched it 1 and a half years ago... so i cant really provide a link but i know forsure that its 85%.
Last edited by LaoFX : 05-03-08 at 05:54 PM. |
|||||||||||||
|
|
|
|
|
#6 (permalink) | |||||||||||||
|
Audiophile
|
if you play in a server that has a cal config. it will change the rates once you enter the server to the appropriate settings. or really close.
After playing in lots of season of CAL for css. it seem that the rates are nto set but depends on your ping/fps/location to the server. So there is no set. example: once i had to have my rates set to cl_cmdrate 66, and once cl_cmdrate 44. because of different locations
__________________
Silverstone Fanboy Instruments: Viola: Hans Keller 300. Year: 2004 Approx Value: $4,000 Guitar: 6 string Fender Squire All white
|
|||||||||||||
|
|
|
|
|
#7 (permalink) | |||||||||||
|
PC Gamer
|
1. Do people in the gungame server ever play CAL?
(i do, but we really are just a bunch of gungame whores )
__________________
I'm a gamer. PERIOD. These days everyone plays some kind of game...But I'm a true Gamer, 'TIL I Die. LUCK = Preparation + Opportunity CSS Name: [OCN] Lucky Killz|╗ Knifing Maniacs Club
|
|||||||||||
|
|
|
|
|
#8 (permalink) | |||||||||||
|
PC Gamer
|
For more info go to fpsbanana.com
or gamefaqs.com I got my info from fpsbanana
__________________
I'm a gamer. PERIOD. These days everyone plays some kind of game...But I'm a true Gamer, 'TIL I Die. LUCK = Preparation + Opportunity CSS Name: [OCN] Lucky Killz|╗ Knifing Maniacs Club
|
|||||||||||
|
|
|
|
|
#9 (permalink) | |||||||||||||
|
Overclocker
|
thats what you needed. a source incase you violate a rule. thx for the source... even though i already knew it lol xP im a cs1.6 guy
Last edited by LaoFX : 05-03-08 at 07:36 PM. |
|||||||||||||
|
|
|
|
|
#10 (permalink) | |||||||||||
|
PC Gamer
|
Yea i forgot to add it Stupid me =p
__________________
I'm a gamer. PERIOD. These days everyone plays some kind of game...But I'm a true Gamer, 'TIL I Die. LUCK = Preparation + Opportunity CSS Name: [OCN] Lucky Killz|╗ Knifing Maniacs Club
|
|||||||||||
|
|
|
![]() |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
|
|