Thread: +TCF+ vs [Dirty30] Scrim tonight at 9PM CST

Visa was a major pain in the ass.

Nice scrim even though we got it handed to us.

BTW, I didn't have F5 as my screen shot, so I didn't get the shot of all you guys and your human tower....sorry.

Yeah visa is always a pain in the ass. That's why we recruited his ass!!! Visa is the man.

Twas fun..... Although next time we'll have to avoid getting spanked so bad..lol

Cheers Bros..

PS - I blame the move on being rusty and not kicking some ass....lol

This hasn't been said, so I just wanted to thank Dirty30 for not rubbing their victory (whoopin) in too bad on us. We took our defeat as a learning experience, and Dirty30 took their winning like great sports. We look forward to another one.

We are the Dirty30, we don't hate... we appreciate. No need to rub it in, we are all friends here and play with eachother frequently. Unless you were some CAL team, then I would rub it in! \\/

ok the choke you get is crazy

Choke is simply the server wanting to send you data but can't

a pretty good explaination of it: Tickrate - Whisper's Wiki

the short form is it's caused by 1 of 2 things

1) an incorrectly set Internet speed (ie just go in to options and change it and it works)

2) Messing around with your tick rates: rate, cl_update rate

Fixing Clients Choke

Besides making sure clients follow BAD CHOKE SOLUTION and set their STEAM Internet Connection Settings correctly, the only 2 Variables that are going to really help the clients choke problems are RATE and CL_UPDATERATE.

1. If in doubt about your STEAM Internet Connection Setting, set it 1 higher than what you have.

2. If you are getting choke and the throughput on the net_graph 3 (see below) is lower than what you expect then raise your RATE.

3. If you still get choke, then make sure you set the CL_UPDATERATE to the servers tickrate and then in steps of 5, lower CL_UPDATERATE until choke disappears or is at least minimised. eg. Start at 100 and try 95, 90, 85, 80 etc. etc.

4. The blame may not always be with you, the client! Try another server, or another server on another Game Service Provider.

5. Finally, don't buggerise around trying to fix choke problems if you have loss problems. You are just wasting your time and everybody elses if you ask them to help fix your choke problems if you have LOSS!!! Loss is a network problem. (See point 6. of net_graph 3)

You shouldn't be getting any choke that means your net settings are messed up.

thanks for the reply Mytheral, i've changed the internet setting for steam its the one steam->file->settings->downloads; i've changed it to 10M the highest one, as mine is 5M, played around with the cl_updaterate from 5 all the way to 100 still doesnt work. How am i supposed to change the net settings?

You changed them correctly.

you haven't tried the rate command yet

for a starting point:
rate 20000
cl_updaterate 20

also try to get it down to around 10 (but 0 ideally) or less constantly, although some (crappy) servers I get as much as 30%

also wait a minute or so after joining a server to adjust it, it takes a bit to settle if your rates are off.

Well i've tried so set rate to 20000 and cl_updaterate 20 and still no fix. I think the spike in choke is a effect of something, it is not the choke that cause my game to die so as to speak. The shaking screen came in first and came the immense choke and there is a huge spike on the entities and otherplayer on the graph.