50 choke in CSS

[Kerri]

I've recently bought a new pc, i have it all set up and everything will play Skyrim smoothly with everything at high and CSS at about 250 fps with high settings. My only problem is that I'm getting about 50 choke ingame. I've tried messing with my rate, cl_cmdrate, cl_updaterate and cl_interp. When I lower cmdrate and updaterate both to 10 and rate to 30000 all the choke goes and my ping falls from 170 to around 140 but actions such as nades and such are laggy and so are hitboxes. When they're around 15 I still get the 50 choke. I've played around with them enough to know it's not them. Internet hasn't changed from old PC and neither has the router or the connection method ( USB adapter, Edimax ew-7711eTn I think ).

Specs : Intel Pentium CPU G860 3.00Ghz
Windows 7 64 Bit
Nvidia GeForce GT 640
4GB RAM
430 watt PSU
500GB Seagate HDD


Rates : ( Before change and after, only difference is PC spec and 50 choke )
cl_cmdrate "101"
cl_interp "0.04"
cl_updaterate "101"
rate "25000"

EDIT : I'm only getting the choke on highly populated servers like our Dust 2 or UKCS ( Can have around 40-50 people on ) but around 20 and it seems fine. Any reason for this?

 

[Kerri]

I also get no choke at all in cs:go, so it's just CSS.

 

[Kerri]

Bump

 

[Slam Fanderbergler]

Did you get a new hdd as well or is it the same one?

 

[Kerri]

Did you get a new hdd as well or is it the same one?

Yea, downloaded CSS again.

 

[Slam Fanderbergler]

Oh. I was asking because when I upgraded my machine I didn't get a new hdd and had the same problem. Don't know what to tell you

 

[Cloakedsphere]

Is this solved or are you still looking for help?

 

[Kerri]

Is this solved or are you still looking for help?

Still looking for help, Steam haven't replied in about a week.

 

[kYuKi]

There are some Registry things you can try. Like this here. It helped me previously before, but as seeing it might be a Hard Drive issue, I would think about doing a reformat to see if that's the case, or buy a cheap new hard drive and try it out. Though, only do these options out of extreme case, as you may want to still want to wait from a reply from Steam.

Both of these are just a suggestion, not a true work around as I've never had this issue before regarding choke.

 

[Cloakedsphere]

This is a handy article I found that could help you.

Part 1 - Cmdrate and Updaterate
Enter a server and change your rates. cl_cmdrate 80 and cl_updaterate 60

Play the game for a few minutes. You will need to make sure that area 5 on the net_graph is not being limited by the server. If it stays at 33.3 or 66.6 all the time, it means you should tweak this on a different server that allows for higher rates (100 tick servers mean max of 100 updates and commands per second!)
Once you find a server that is not limited, you want to make sure your rates are cmd 80, and update 60. Play on the server for a few rounds, and keep an eye on your CHOKE and LOSS.

If you are experiencing choke, you will need to change your rates lower. The correct ratio for update to command means cl_updaterate should be 3/4 of cmdrate (75% is good)-- *This means CMDRATE is higher than UPDATERATE by a pinch*. So, lower your rates, keeping ROUGHLY the same ratio. If your choke is 30, lower your rates about 30 (but make sure you still use the ratio of 75%). This would mean cl_updaterate 35 and cl_cmdrate 50 (thats 70% ratio, close enough)

Try the new settings, and adjust your rates as needed. You want to lower your rates until you get less than 2 choke in the middle of a round, and less than 10 at the beginning, and end of a round. (choke is higher at beginning and end of rounds while server does stats, and resets objects)

Once you get to 0 choke, and 0 loss (loss may not change if it is a network problem) you have your proper rates.




Part 2 - The rate setting in CSS
The rate setting is used to set the MAX amount of data coming to you from the server in bytes per second. Rarely does your computer receive more than the max, and the more players on the server you are on, the more data you will recieve. On a 32 player server, you receive player positions, voice, chat, and nades weapons etc move. That will obviously use a lot of bandwidth to receive all that info.
In short, heres what you set your rate to, its not very important to tweak.
Connection Speed Set your rate to:
56k or slower 1800comcast
Slow DSL/Cable 20000
Fast DSL/Cable 25000



Part 3 - Interp setting in CSS
In Counter Strike Source, once your lag ping choke and loss are all fixed, you can improve your connection even more. The interp setting in CSS is used to tell your computer how fast to interpret the player and object positions sent to you by the server. The proper interp depends on your updaterate. Your cl_interp should be 1/updaterate. This means that if your updaterate is 50, your interp should be .02 - In the console type "cl_interp .02" or whatever yours should be. MAKE SURE YOU GET THE .02 and not just .2
There is also an interp setting that sets your interp automatically, adjusting dynamically. I do not use it, and cant give any advice, but the command is cl_interp 0.