Problem...

[Max The Bunny]

When I join to our server, I start to lag. MY ping is 'round 150 as normally, but I lag and lag and lag. It have never happen on our server. When I go to other server with same ping it isn't lagging. What's my problem?

 

[Sharp67]

This has been happening a lot lately to me too....i figured it was the ISP that runs the server crapping out

 

[Ice hearted killer]

ditto

 

[Max The Bunny]

So, what to do?

 

[Tanooki]

Call up your ISP and see if there are any problems. Currently my ISP is having issues due to the large amounts of rain my area has gotten over the past couple months. (Missouri is soon either going to be a swamp, or a marshland ) This has caused issues with my connection speed due to water getting in the lines... It's strange though because I don't have issues with like my Valve games, but I have problems with WoW, and vent.

 

[Primesghost]

while in the game, open up your console and type rate. Check what it's set to and try turning it up to 10k, 20k, or 30k. I had this exact same problem and that was it for me.

 

[!Woodstock!]

I have heard a few discussions about rates. I really do not know what they are all about. If someone could explain them and values to use to try to decrease lag, that would be g r e a t...y e a h...

 

[Tanooki]

Hmm I thought the eGO servers set the rates to what they should be automatically and you couldn't change it? I could be wrong, just what I thought (also I don't feel like creating a new thread to ask this question, but does anyone know the command to bring up net_graph 3, but without the map it shows of your ping jumps or whatever it is.)

 

[Drew The Pirate]

net_graph 2

also, as far as rates are concerned, you need to change them based on your personal internet connection speed. I set mine at 30k, I think the ego servers automatically cap it at 20k. in general if you have a quick speed, go ahead and set it higher.

 

[!Woodstock!]

On rates, what is a red-line minimum if there is one?

 

[Lafinass]

A brief explanation...

rate is a measure of the overall bandwidth your client will attempt to utilize. It defaults to 10000, but this will cause choke on most servers. eGO servers cap the rate at 25000, so regardless of your setting it won't go higher.

cl_updaterate is the rate at which you receive packet updates from the server or more precisely the rate your client will expect to receive. If this is set higher than the server is providing, you will generate choke. This is capped at 66 on eGO servers.

cl_cmdrate is the rate at which the client attempts to send packets to the server. If you attempt to set this higher than the server can handle, you will generate loss. This is also capped at 66 on eGO servers.

Your best bet is to set all of these to max and then join your favorite server. Run net_graph 4 and observe the four numbers on the right. From top to bottom they are cl_updaterate, the actual update rate, the actual command rate, and cl_cmdrate. The top two numbers should be as close to identical as possible and the bottom two numbers should be as close to identical as possible. If they are not, you may notice your choke is high. Any choke over 10 will be noticeable and ideally we want zero. So decrease the values until you have zero choke and the numbers all match up. For myself that is 30/60 update/cmd, but your mileage will vary. And just because your current rates work today doesn't mean they will next week.

 

[!Woodstock!]

Thanks Lafinass, I play around with it next time I play.

 

[Drew The Pirate]

if you are getting crazy choke, check your rates. After one of the recent updates I was trying to play and I was lagging like crazy. I checked my rates and found that for some reason or another, they had reset to 3000... that's wayyy low. Kicked it back up to 30k and was fine.