Css cmd rates

Sniper123

Sniper123

Sniper123

Associate
Joined
29 Nov 2006
Posts
470
Location
The Mo0n
Had to delete my CFG file so I could get the radar back but now my rates are messed up :(

Atm half my shots don't seem to regester, So I'm blaming the rates :p Just had a quick look in the CFG file and its set to...
cl_updaterate "60"
cl_cmdrate "60"

So what rates are you guys using?
 
Just set them to 100 tbh. :)

I'm using 100/100/25000 I think.

Why set them to 101 btw Redbull? I've seen lots of people do this, despite playing on 100 tick servers.

I thought it was 33/33 for 33 ticks, 66/66 for 66 ticks, and 100/100 for 100 ticks?
 
Fraggr said:
Just set them to 100 tbh. :)

I'm using 100/100/25000 I think.

Why set them to 101 btw Redbull? I've seen lots of people do this, despite playing on 100 tick servers.

I thought it was 33/33 for 33 ticks, 66/66 for 66 ticks, and 100/100 for 100 ticks?
Click to expand...

Completely correct.

Valve now had server side commands to restrict peoples rates. Which is what the community has been after for years. People uses rate 101 because it makes them harder to hit . . .
 
i've got a standard 2Meg ADSL connection and my rates are:


20,000
80
80
cl_smooth 0


think thats all i've changed other than a few adjustments with cl_inter....
 
Depends what the max rate on the server is always just set it to whatever
the server allows which is mostly rate 25000 cl_cmdrate 101 cl_updaterate 101
 
Depends what the max rate on the server is always just set it to whatever
the server allows which is mostly rate 25000 cl_cmdrate 100 cl_updaterate 100
 
If I use anything higher than 18000 80 80 I get connection errors, causing my game to 'hang' then lose connection and quit back to the front-end GUI. So annoying.
 
The rates are there for shot registration, like your blasting some with an m4 then you check the console and it says you never even hit them.

Man I hate it when it does that!!!!! makes me wana put the mouse through the monitor!!! ok ok calm down now :p

so has anybody come to a conclusion on rates then?

I see people on servers say 25000 60 60 (just an example btw) but which is which?
 
I thought a lot depends on your connection.

I have 30,000 - 101 - 101 - Seems to work very well.

Best bet is to bring up the netgraph (3 I think) and watch for choke and loss and adjust accordingly until they are both around 0.
 
thanks,

choke goes upto 50-70 :-/ which does my head in.

ill try those rates when i get home then.

btw internet connection is VM 20mb
 
kirbz said:
I see people on servers say 25000 60 60 (just an example btw) but which is which?
Click to expand...

rate: 12000 - 25000 (typically)
cl_cmdrate: 60 - 100 (typically)
cl_updaterate: 60 - 100 (typically)

As has been said, the "correct" rates, very much depend on the server settings and your internet connection. But those are the range of values that should work best for most people.
 
i've been having trouble shooting people, fire a full clip in bursts and not 1 hit, the only kills was nades and a few lucky random shots. i'm going to try the rate commands and if they don't work God help anybody within striking distance ;)
 
tbh rates should be set to whatever tick the server is..

so if you on a

33tick server cmd - 33 update - 33
66tick server cmd - 66 update - 66
100tick server cmd - 100 update - 100

some people dont agree with this and keep them at say 80 etc.

but imo its best just to adjust the rates to comply with the server.

rate however ive always just kept at rate 25000
 
Pinkeyes said:
I thought a lot depends on your connection.

I have 30,000 - 101 - 101 - Seems to work very well.

Best bet is to bring up the netgraph (3 I think) and watch for choke and loss and adjust accordingly until they are both around 0.
Click to expand...



30k is overkill lol.


and 101 was back in the old CS days. i'm pretty sure source is limited to 100.
 
You must log in or register to reply here.
Back
Top Bottom