Server running at 66tick?

[ZeroX]

Well after the new update I have noticed that almost all CS:S servers have been running at 66tick mine is running at 66tick and I am using the same command line as before.

I have also noticed that some scrim servers run at 100tick and all of ESEA servers run at 100tick.

[Beaverbeliever]

Put these in your server.cfg:

Code:

sv_maxupdaterate 101
sv_maxcmdrate 101

[BehaartesEtwas]

valve locked the tickrate ad 66. there are hacks to change the tickrate anyway, but I wouldn't recommend that... they also fixed several problems in the lag compensation and interpolation which make higher tickrates unnecessary.

[ZeroX]

(06-26-2010, 07:12 PM)BehaartesEtwas Wrote:  valve locked the tickrate ad 66. there are hacks to change the tickrate anyway, but I wouldn't recommend that... they also fixed several problems in the lag compensation and interpolation which make higher tickrates unnecessary.

Leagues may force you to use a mod to set it to 100tick maybe the new zblock will have it .

[BehaartesEtwas]

(06-27-2010, 06:01 AM)ZeroX Wrote:  Leagues may force you to use a mod to set it to 100tick maybe the new zblock will have it .

on the contrary. leagues will (hopefully) not rely on some ugly hack. in fact a tickrate of 66 is fine, no need to change it. valve change some things in the netcode so higher tickrates will not do anything better...

in case you feel the hitboxes are not in place, make sure your cl_interp value is not too small and the server is running stable... the registration is now better than on a tick 100 server before the update...

[lhffan]

What walue is optimal for cl_interp... close to your ping on the server or what?

I have seen many threads about that. Some want to have it at 0.00 and others a value under the standard value.