Originally posted by: ShawnD1
First of all, tick is not the same as cmd rate. Tick is how often the server is updating itself and doing calculations. cmd rate is how often it tells you about those updates.
http://game.kingj.net/pages/extra-tickrate
I would like to point out that you are mixing up cmd rate and update rate. Cmd rate is the frequency what which you
SEND packets to the server. It is directly tied to your frame rate.
Also, I never said a 100 tick server and cmd rate were the same thing. I included 100 tick for more description, I could have easily left it out and said "The server I play on goes from 5-15 choke to 0 choke if it is reset every couple of days".
He doesn't get choke on the servers that have admins smart enough to put limits on the update frequency. The ones with no limits will let you run at the full 100hz update rate and choke like crazy. I took 2 screenshots to show how this works.
Right now your sentence states that server admins are stupid because they run 100 tick servers. There are always limits but I'm assuming you are meaning high tick rate servers.
Update rate is packets sent from the server to you. Last time I checked, most broadband players don't have any problems receiving the amount of data required. This assumes they are trying to play on a server that can handle the load and there are no connection issues between the player and the server.
Here is a picture of me playing TF2 with a 100 cl_cmdrate and cl_updaterate
Notice how the incoming bandwidth is 15kb/s and my choke is 24. The little numbers between my settings indicate that the server is forcing a rate of 33hz incoming and 26hz outgoing (odd numbers are probably given because I'm choking so bad).
Now look at what happens when I set cl_cmdrate and cl_updaterate down to 10
Incoming bandwidth has reduced to 5.4kb/s, my choke is now 2. Although my ping has increased, the problem of the server not receiving my packets is gone. You'll also notice how the server is forcing a 30hz outgoing but allows me to run at 10hz incoming.
I looked at your screenshots and this is what I see.
The server you are playing on in these screen shots has cmd rate set at ~26 and update rate at ~33. You on the other hand have 20fps in that screen shot. You have choke because you're trying to send out more packets then you are generating.
In your case, which I believe is the minority now, you don't have a computer powerful enough to handle the settings you are playing at. You need to limit your max fps to something lower. If you keep dipping below the statically set cmd rate you WILL get choke. Plus you must have some pretty noticeable slows downs going from 40 to 20 etc?
You solved this in the second screen shot because you limited everything to 10 and your fps went up to 40. Set your max_fps to 3 and then set your cmd and update rates to 10 again and see what happens after awhile.
Some servers don't put a limit on the cmd and update rates, so you can really screw yourself if you don't know what you're doing.
The tick rate is the limit. Whatever the tick rate is would be the maximum that server is updating. Obviously, they can set up/down async but there is always a limit.
Personally, I would never play on a server like the one you have in your screen shots. If those settings were set by them then you have clients updating the server LESS than the server is updating the client...self imposed by the server. Considering the clients are the objects doing stuff in the game world...that seems slightly silly. Wouldn't be nearly as bad in a case like yours because your computer can't produce the frames. On top of that both cs:s and tf have weapons that shoot faster then a server like that can update...meaning potential missed hits.
Facebook
Twitter