Jump to content
Posted 11 May 2006 - 04:17 PM
Posted 11 May 2006 - 08:26 PM
Posted 12 May 2006 - 01:37 AM
Posted 12 May 2006 - 10:31 AM
Posted 13 May 2006 - 03:04 PM
Posted 13 May 2006 - 04:14 PM
Posted 19 May 2006 - 04:54 PM
Posted 20 May 2006 - 12:45 AM
Posted 21 May 2006 - 10:09 PM
Posted 22 May 2006 - 02:17 AM
It is important to check your rates for both Steam and for ingame. There have been many players with DSL running with 14.4 modem rates which certainly won't help and this also makes connecting and map downloads very slow.
To check your rate in Steam: Steam > Settings > Internet
To adjust your rate in the game: console (~) then:
to see what it is set to.
Here are all the different pre-set rates (all bytes/second):
Modem - 14.4k - 1500
Modem - 28.8k - 2500
Modem - 33.6k - 3000
Modem - 56k - 3500
ISDN - 112k - 5000
DSL > 256k - 7500
DSL > 768k - 9999
LAN/T1 > 1M - 20000
You may also want to try customizing the rates to your exact setup. Type each of the following commands in your game console and write down your default settings before making any changes:
For example, your default cl_cmdrate rate might show as "cl_cmdrate 30" in your game console.
Type "net_graph 2" in your game console. You will see a line with different colors. You want that line to be as steady as possible.
Next, please try altering the rates of the following: (Note: "X" is variable rate you will be assigning/altering.)
"cl_cmdrate X" - This refers to the maximum number of command packets sent to server per second. This should be equal to your FPS. If this is set too high or too low, you will experience a choke. There is no cap for GoldSrc games (Half-Life, Counter-Strike), however, Source games are capped at 100.
"cl_updaterate X" - This refers to the number of packets per second of updates you are requesting from the server. There is no cap for GoldSrc games - the Source game cap is 100.
"rate X" - This refers to the maximum bytes per second the host can receive data. GoldSrc games are capped at 20000 and Source games are capped at 30000. If this is set too high or too low, you will experience a choke.
“cl_interp X” - This interpolates object positions starting "X" many seconds in past. Higher cl_interp rates make the game appear smoother, but true player positions will be displayed less accurately.
In the event altering, also known as 'tweaking', the rates in your game console does not help, please revert to your default rate settings.
Edited by Mr Alpha, 22 May 2006 - 02:25 AM.
Posted 03 June 2006 - 02:34 AM
Posted 07 June 2006 - 02:39 AM
Posted 15 July 2006 - 08:27 PM
0 members, 0 guests, 0 anonymous users