CSS Lag/ Choke?!
- Thread starter Angeal
- Start date
- Joined
- Jan 5, 2010
- Messages
- 117
also. Choke is always high when you're in thirdperson/free look on the jail servs
depending what your rates are set to, since they are running real low there, it could have just been that the server was full or something. i know when i play on dust2 (or did anyway) i couldn't get above 30 tick or less than like 25 choke just because of the intense amount of traffic through the server with 38+ people. its just how it is, you won't find a server that big that doesn't do the same thing.
its like in events with smaller maps, you'll never have less than 50 choke...its almost impossible!
set rates to cl_cmdrate 101 cl_updaterate 101 and let the server govern what the cap is (eGO is 60/66) and you'll be fine. choke otherwise is just a part of the game dependent on your connection with the server, and if that server is full or overloaded then theres really nothing that can be done about it, unless people disconnect.
its like in events with smaller maps, you'll never have less than 50 choke...its almost impossible!
set rates to cl_cmdrate 101 cl_updaterate 101 and let the server govern what the cap is (eGO is 60/66) and you'll be fine. choke otherwise is just a part of the game dependent on your connection with the server, and if that server is full or overloaded then theres really nothing that can be done about it, unless people disconnect.
- Joined
- Mar 7, 2009
- Messages
- 4,081
eGO servers arent the "best" so your always going to get some choke since they are 66 tick, always expected with large player count servers because CSS isn't really made for that. I prefer 24 at the max, with 100 tick servers.
funny thing is bout rates and choke is they are directly connected. so if your rates are set too high for your connection with the server you'll get choke. so then you're told to lower your rates by the amount of choke and that way you won't get choke anymore, except you're limited the traffic from your computer to the server with setting your rates lower.
essentially you're doing the same thing as choke is, and it isn't changing anything, except by manually setting your rates lower you are guaranteed not to get higher. for instance you set your rates too 100/100 and get 50 choke. you're supposed to set them to 50/100 and now you get 0 choke. good job except now you'll never get higher than 50 tick even if you would have 0 choke or not. same scenario you set your rates to 100/100 with 50 choke, it just means that only 50 bits of info per second are zooming around instead of your set 100, so its the same outcome except this time if the connection clears up with lesser ppl etc it can raise to 60 (by having 40 choke) or more...improving things like player positions (registry) and whatnot
essentially you're doing the same thing as choke is, and it isn't changing anything, except by manually setting your rates lower you are guaranteed not to get higher. for instance you set your rates too 100/100 and get 50 choke. you're supposed to set them to 50/100 and now you get 0 choke. good job except now you'll never get higher than 50 tick even if you would have 0 choke or not. same scenario you set your rates to 100/100 with 50 choke, it just means that only 50 bits of info per second are zooming around instead of your set 100, so its the same outcome except this time if the connection clears up with lesser ppl etc it can raise to 60 (by having 40 choke) or more...improving things like player positions (registry) and whatnot
