Rate help
jacksmoke234
Join Date: 2007-07-07 Member: 61518Members
in Tech Support
This isn't for me, but it's for a friend of mine that is really starting to make trouble in a server I play on.
He's playing using a 56k connection, and everyone knows thats bad to begin with, but I'm wondering are there any good rates to even help reduce the lag a little bit?
Thanks if anyone knows.
He's playing using a 56k connection, and everyone knows thats bad to begin with, but I'm wondering are there any good rates to even help reduce the lag a little bit?
Thanks if anyone knows.
Comments
rate 7000
cl_cmdrate 40
cl_updaterate 40
ex_interp 0.1 // default
if he gets choke lower cmdrate
For a 56 k connection, it should be something like:
rate 5000 (or maybe lower)
cl_cmdrate 30 (or 20)
cl_updaterate 30 (or 20)
ex_interp 0 (= auto set depending of cl_updaterate)
That will affect what you should set your rate at. <a href="http://ucguides.savagehelp.com/ConnectionFAQ/Halflife.htm" target="_blank">This</a> is the link you're looking for.
rate 4500
cl_cmdrate 40
cl_updaterate 40
cl_cmdbackup 1
cl_resend 1.5
<!--QuoteEnd--></div><!--QuoteEEnd-->
cl_cmdbackup 1 ? 2 (default) would be better on a 56 k connection i think.
cl_resend 1.5 ? why ? it should be higher on a 56 k connection. Ah you probably think it's "the number of times a packet can be resent to the server if a packet delivery fails." like said on ensl site, that totally wrong. cl_resend is "Delay in seconds before the client will resend the 'connect' attempt. This is when you have problem connecting to server and when you see : "Retrying connection to server #1". And this hasn't anything to do with netcode like people originally though."