How to fix choke?

[RTFMy]

Lately i've had some choke, but I still had a good ping (average 50)

my rates :
rate 20,000
cl_rate 20,000
cl_cmdrate 101
cl_updaterate 70
cl_interp 0.05
cl_smooth 0

 

[bliink]

choke occurs when your computer is too busy to accept the packets coming to it, try closing unneeded programs

 

[RTFMy]

choke occurs when your computer is too busy to accept the packets coming to it, try closing unneeded programs

Besides Xfire thats all I run in the background.

I have a wireless connection (yes it blows ) though, but it's not to bad, right now I ping 110 to google.

 

[bliink]

What speed is the wireless?

 

[RTFMy]

768 I think?

It shouldn't be the wireless, cause I never had this problem with CS 1.6, but I don't remember the rates I used.
Isn't there a rate you adjust to fix choke?

 

[smsKONG]

cl_updaterate is usually the culprit try lowering this, also I think your rate itself should be a little lower (but I could easily be wrong:E ). You just have to remember that the upspeed AND downspeed of your connection have to be considered when setting your rates. Also in your case, you'll have to consider that tho your connection may be 768 on paper, in reality it depends on the quality of the wireless signal you can attain.

My advice would be to set them all lower then experiment with raising them bit by bit till you start to get tiny amounts of choke, then a small amount of tweaking should get you to the optimal rates for your connection.

(Also the old CS rates aren't right for everyone - since the rates have changed for different connections. The faster your connection- the more likely your CS:S rates will have remained close to the 1.6 rates. For instance my 256k rates have dropped quite a bit, but many people with faster connections are still practically using the old cs max rates ).

 

[smsKONG]

[Sorry tried to edit this in but it took me too long..damn my single finger style ] - I'm not being arsey by the way Bliink (cos I could easily be wrong about this:E ), but I always thought choke was caused when you are receiving too many packets for your connection to receive, meaning you get a backlog of packets that the server is trying to send you. By reducing cl_updaterate, you reduce the number of update packets that the server sends to your computer every second. Thus reducing or ceasing the choke as you limit what the server can send you based on the downspeed of your connection.

And for the thread starter-

Ping is the time for a packet to get to you from the server, this has nothing to do with your choke. Loss is something else alltogether and if you are getting this then it is indicative of a problem with your connection, ie your are losing packets in transit, this could either be caused by faulty equipment at your end (if always getting loss) or a bad line path to the server/poor ISP reliability (if intermitent loss).

Also,if I remember correctly(bit of a lottery then:E ) cl_updaterate is linked to rate as cl_cmdrate is linked to cl_rate

 

[RTFMy]

I was messing around with my rates today like you suggested, 20 minutes, and didn't fix much

http://www.rtfmish.com/images/de_dust20013.jpg

 

[[12K]Uber-Police]

whats cl_interp 0.05

what benefit does that have and what is it?

 

[smsKONG]

cl_interp is the command for how much server side interpolation occurs the value states how far ahead it will predict movement for you in seconds I believe (used to battle the inevitable delay between user and server)

RTFMy, what did you change and how much did you change it?

As I said the command which usually affects choke is cl_updaterate, but if all your rates are too high then you will still have problems.

Try dropping your rates down to something like:

rate 12000-15000
cl_rate 14000-17000
cl_cmdrate 60-75
cl_updaterate 40-50

then do the increases from there

If you are still getting choke after you drop the rates down to the values above, then I'm afraid your choke is being caused by something else (or your connection is really bad and you need to drop them further). It could be something with your internet settings (maybe packet compression is enabled or something), but beyond this I don't think I can offer too much help.

Btw using cl_smooth 0 is possibly not the best thing either(it's supposed to help you if other people are choking or losing packets- it smooths over their jerky movement)

 

[RTFMy]

What I did was I took everything down rates to about 10,000 and cl_cmdrate to about 40 cl_updaterate to about 40, and tryed increasing from there, found nothing consistent, just the same problem - choke.

What I find funny is I played some CS 1.6 today, used the exact same rates and I got 0 choke.

 

[RTFMy]

I just a took a speed test at dslreports, and I got

- 1028 down
- 783 up


http://www.rtfmish.com/images/dslreports.jpg