<a href='http://ucguides.savagehelp.com/ConnectionFAQ/Halflife.htm' target='_blank'>Try this page</a> its old, but most commands still work, It would be futile for anyone here to say, your rate cl_updaterate and cl_cmd rate should be X, X and X, as it varied between two exact same connections as much as it does a 128k connection to a 2mb connection. good luck <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile-fix.gif' border='0' style='vertical-align:middle' alt='smile-fix.gif' /><!--endemo-->
those are the rates I use. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> If I am not mistaken Jink Jink said the most cmd a server can get is 30 so any higher you are oversending.
<!--QuoteBegin-slipknotkthx+Feb 24 2005, 12:47 AM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (slipknotkthx @ Feb 24 2005, 12:47 AM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin-->If I am not mistaken Jink Jink said the most cmd a server can get is 30 so any higher you are oversending.<!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> That's incorect afaik. *Most people set that value higher than 30. I have mine set @ 65. Besides, cl_cmdrate is a <b>client side command.</b> I don't understand why the server would max out at 30...
Server admins can decide what your max rates are with the help of a plugin.What type of connection are you using,wireless tends to have bad latency so that might be it.
P.S.. use morephus instead.. it doesn't use sys resources like kazaa does..
(shifty eyes) I didn't say that. <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html/emoticons/wink-fix.gif' border='0' style='vertical-align:middle' alt='wink-fix.gif' /><!--endemo--> <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd--> Or use BT as then it isn't the sys resources that makes yah choke it is the DLing at 200K/s <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif' /><!--endemo-->
you can also very easily set many P2P progies to cap the up/down speeds <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile-fix.gif' border='0' style='vertical-align:middle' alt='smile-fix.gif' /><!--endemo-->
<!--QuoteBegin-CoCa+Feb 26 2005, 11:49 PM--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><b>QUOTE</b> (CoCa @ Feb 26 2005, 11:49 PM)</td></tr><tr><td id='QUOTE'><!--QuoteEBegin--> I have 3 mb connection and a good pcw. updaterate ?? cmd rate ?? rate ?? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd--> In half-life, as most FPS games, there is a key you can press to bring down what is known as the console.
In half-lifes console there are commands to control the network speed, and packets sent and recieved.
Rate - is the speed in bytes that you can set, what is your max upstream in bytes, not in bits. I find setting this to between 1 and 5 kilo bytes per second less than my maximum upstream works on my connection. (the upstream is only 15kbps) I set this to between 10000 and 14000.
cl_updaterate - is the downstream packet controller. It works on alot of values, But I'd say anywhere from 30 - 101 is fine.
cl_cmdrate - this is the one that if set incorrectly will make people see you "skip" accross the screen infront of them when set to low, and cause choke when set to high, for instance, I cannot set this to higher than 75, or i begin to get choke. but again its dependent on connection,
so just play with the command in the half-life console (the key left of 1 and above tab), as you dont know what these are I assume its set to Rate 7500 cl_updaterate 20 cl_cmdrate 30, which to be honest, should be fine on most connections, but with 3mb, I dunno, probably just too fast for those settings.
Comments
seriously, just stop.
/me points at tech help forum, post there.
and tell us ping, choke, and loss.
and your net connection, and sys specs and other things.
and stop downloading porn via p2p prgorams.
P.S.. use morephus instead.. it doesn't use sys resources like kazaa does..
(shifty eyes) I didn't say that. <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html/emoticons/wink-fix.gif' border='0' style='vertical-align:middle' alt='wink-fix.gif' /><!--endemo-->
rate 9999
cl_cmdrate 80
cl_updaterate 15-20
cl_rate 9999
those are the rates I use.
P.S.. use morephus instead.. it doesn't use sys resources like kazaa does..
(shifty eyes) I didn't say that. <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html/emoticons/wink-fix.gif' border='0' style='vertical-align:middle' alt='wink-fix.gif' /><!--endemo--> <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
*Cough**Cough*Shareaza**Cough*
rate 9999
cl_cmdrate 80
cl_updaterate 15-20
cl_rate 9999
those are the rates I use. <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
If I am not mistaken Jink Jink said the most cmd a server can get is 30 so any higher you are oversending.
That's incorect afaik. *Most people set that value higher than 30. I have mine set @ 65. Besides, cl_cmdrate is a <b>client side command.</b> I don't understand why the server would max out at 30...
updaterate determines recieve from server.
cmdrate determines send to server.
updaterate ?? cmd rate ?? rate ??
P.S.. use morephus instead.. it doesn't use sys resources like kazaa does..
(shifty eyes) I didn't say that. <!--emo&;)--><img src='http://www.unknownworlds.com/forums/html/emoticons/wink-fix.gif' border='0' style='vertical-align:middle' alt='wink-fix.gif' /><!--endemo--> <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
Or use BT as then it isn't the sys resources that makes yah choke it is the DLing at 200K/s <!--emo&:p--><img src='http://www.unknownworlds.com/forums/html/emoticons/tounge.gif' border='0' style='vertical-align:middle' alt='tounge.gif' /><!--endemo-->
you can also very easily set many P2P progies to cap the up/down speeds <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html/emoticons/smile-fix.gif' border='0' style='vertical-align:middle' alt='smile-fix.gif' /><!--endemo-->
updaterate ?? cmd rate ?? rate ?? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
In half-life, as most FPS games, there is a key you can press to bring down what is known as the console.
In half-lifes console there are commands to control the network speed, and packets sent and recieved.
Rate - is the speed in bytes that you can set, what is your max upstream in bytes, not in bits. I find setting this to between 1 and 5 kilo bytes per second less than my maximum upstream works on my connection. (the upstream is only 15kbps) I set this to between 10000 and 14000.
cl_updaterate - is the downstream packet controller. It works on alot of values, But I'd say anywhere from 30 - 101 is fine.
cl_cmdrate - this is the one that if set incorrectly will make people see you "skip" accross the screen infront of them when set to low, and cause choke when set to high, for instance, I cannot set this to higher than 75, or i begin to get choke. but again its dependent on connection,
so just play with the command in the half-life console (the key left of 1 and above tab), as you dont know what these are I assume its set to Rate 7500 cl_updaterate 20 cl_cmdrate 30, which to be honest, should be fine on most connections, but with 3mb, I dunno, probably just too fast for those settings.