Fatty October 10, 2004 Share Fatty GC Founder October 10, 2004 Ok, what is choke, what causes it, why's it go up and down, who's responsible for it, and um yea. Also, anyone find tweaks for source? I could use any info at all, especially video...but also the normal rate stuff, etc. I had an entire autoexec.cfg of tweaks for CS, but now I'm running stock. Any tips would be helpful. I really need to see if I can squeeze tolerable perfomance out of my video card, and I'm also interested in why I'm seeing so much choke. Link to comment Share on other sites More sharing options...
Fatty October 10, 2004 Author Share Fatty GC Founder October 10, 2004 Rates? Went to office, people were warping on me, my choke was up to 100! Has this anything to do with the GSP? Link to comment Share on other sites More sharing options...
Fatty October 10, 2004 Author Share Fatty GC Founder October 10, 2004 choke same in another server....gonna reset my router, etc... Link to comment Share on other sites More sharing options...
TheBugs October 10, 2004 Share TheBugs Member October 10, 2004 i keep both cl_cmdrate and cl_updaterate at 60 and rate at 25000. Link to comment Share on other sites More sharing options...
ConGregation October 10, 2004 Share ConGregation Member October 10, 2004 I adjusted my rate to 9999 and choke went away on office. It was only hovering around 4 though. Link to comment Share on other sites More sharing options...
auggybendoggy October 10, 2004 Share auggybendoggy Member October 10, 2004 what is choke? and all these other settings? Link to comment Share on other sites More sharing options...
bear^ October 10, 2004 Share bear^ Member October 10, 2004 Loss = percent of incoming packets of data seen as lost Choke = percent of outgoing packets of data seen as lost Both are a type of packet loss Rate = Amount of data per packet. This number needs to be the same or very close to the server's settings. Otherwise packet loss occurs. If you have choke type into your console cl_updaterate Look at the current value. If it was 60, lower it to 50 If you have latency, you want to increase your cl_updaterate values Hope this helps! Link to comment Share on other sites More sharing options...
spiralstairs October 10, 2004 Share spiralstairs Member October 10, 2004 Loss = percent of incoming packets of data seen as lost I get extreme loss spikes. Like, itll jump to 20, then chill at 3, go back to zero, and so forth. Makes the game very unplayable. How do I fix this? Link to comment Share on other sites More sharing options...
Fatty October 10, 2004 Author Share Fatty GC Founder October 10, 2004 Um...maybe this is the problem, because as I found them (stock) they were: cl_cmdrate "30" cl_updaterate "20" What is: cl_cmdbackup "2" And I see no plain old "rate" line? Link to comment Share on other sites More sharing options...
Guest zerodamage October 10, 2004 Share Guest zerodamage Guests October 10, 2004 Loss = percent of incoming packets of data seen as lostChoke = percent of outgoing packets of data seen as lost Both are a type of packet loss Rate = Amount of data per packet. This number needs to be the same or very close to the server's settings. Otherwise packet loss occurs. If you have choke type into your console cl_updaterate Look at the current value. If it was 60, lower it to 50 If you have latency, you want to increase your cl_updaterate values Hope this helps! <{POST_SNAPBACK}> Excellent explanation. I was going to type the same thing. You may gain some ping by downing your cl_updaterate but choke will go away. Default rate is 10000. I have mine at 15000 with excellent results. Link to comment Share on other sites More sharing options...
Fatty October 10, 2004 Author Share Fatty GC Founder October 10, 2004 Welp, that seems to have solved the choke problem...so defaults are lame. Thanks guys! Link to comment Share on other sites More sharing options...
TheBugs October 10, 2004 Share TheBugs Member October 10, 2004 time "rate" in the console and u will see what urs is at. Link to comment Share on other sites More sharing options...
spiralstairs October 10, 2004 Share spiralstairs Member October 10, 2004 (edited) thanks. that solved it. changed Cl_updaterate to 10 (default was 20) and changed my rate to 15,000. no more choke or loss. EDIT: still getting loss spikes. choke is okay still. Edited October 10, 2004 by spiralstairs Link to comment Share on other sites More sharing options...
Fatty October 10, 2004 Author Share Fatty GC Founder October 10, 2004 why you go 10 with updaterate? did someone suggest it that low Link to comment Share on other sites More sharing options...
spiralstairs October 11, 2004 Share spiralstairs Member October 11, 2004 You may gain some ping by downing your cl_updaterate but choke will go away. Link to comment Share on other sites More sharing options...
Fatty October 11, 2004 Author Share Fatty GC Founder October 11, 2004 Was just pointing out that the defaults were WELL below what these lee7 people were using/suggesting ( I saw 60/60, etc) Have you tried tossing it up there yet? Link to comment Share on other sites More sharing options...
spiralstairs October 11, 2004 Share spiralstairs Member October 11, 2004 Was just pointing out that the defaults were WELL below what these lee7 people were using/suggesting ( I saw 60/60, etc) Have you tried tossing it up there yet? <{POST_SNAPBACK}> Yeah, just tried making it higher. Choke started up again. Link to comment Share on other sites More sharing options...
Fatty October 12, 2004 Author Share Fatty GC Founder October 12, 2004 This is from Barry at xgaming: Please relize Choke does not come from the server itself. It is happening because these players think they know it all and are "Tweaking" there client side. Choke comes from when the client over sets there settings particuly with the cl_updatrate's. They did this with HL1 and they will try and do it again with HL2. I never understood why these people would alter there settings when they have no idea what it really does. If they set there updaterates and the server is not properly setup to accept tweaking then the client will be trying to pull to much information and the server will only allow so much which causes Choke. Now I dont suggest changing the servers updaterates because it has not been properly tested to do so. A while back CAl put out some false information about update rates and such and ever since then most of the CAL teams at least over tweak there settings without knowing what they are doing. Then they think evry server they play on that has choke is because the server sucks. Well yes if you have a small 5 vs 5 match server with the CAL configs running you can get away with this. When CAL put out the information about tweaking the configs they did this with the intention for 5vs5 match play with there config running. Typically you do not want to run these configs on a public server because most pc's can not handle that update rate on anything larger then 10 players. Its just to much information to process for that PC. Now HL2 is more demanding then the HL1 is therefore the tweaking should not be so harsh like it was with HL1 unless you have a top of the line PC. Im not sure if you notice but those that do not tweak there settings rarley complain about Choke. Good rule of thumb for any server is if every single person is not seeing the exact same problem then its not the server itself. Its either the ISP, Routing to and from the server or the client has over tweaked his or her settings. You can try changing the rates within the server but I do not suggest it. I've noticed that each time someone in our server complains of choke, another comments that he has none, which backs up his rule of thumb. So, Budweiser salutes you, Mr. "Tweak Everything until it Breaks" Man. Although, I think the defaults are a bit off...cause I tweaked to suggested and choke went away for me. So anyways, this addresses the fact that it's not the sever. Link to comment Share on other sites More sharing options...
dwEEziL October 12, 2004 Share dwEEziL Member October 12, 2004 /background singers "Tweak til it breaks!" Link to comment Share on other sites More sharing options...
DJ Premier October 12, 2004 Share DJ Premier Member October 12, 2004 Fatty configing. What has the world come to. Link to comment Share on other sites More sharing options...
Fatty October 13, 2004 Author Share Fatty GC Founder October 13, 2004 /background singers "Tweak til it breaks!" <{POST_SNAPBACK}> lmao dweez... The guy keeps talking: "When they said your card wasn't going to run that new game, you scoffed at them and made it work...." <background "you scoffed and laughed at them..." "FPS? You invented max_fps because smoke has no effect on you" <you don't see the smoke> Mr. Tweak Everything until it breeeaaaakkkksss....... Link to comment Share on other sites More sharing options...
dwEEziL October 13, 2004 Share dwEEziL Member October 13, 2004 LOL, nice! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now