View Single Post
.raM
Junior Member
Join Date: Dec 2017
Location: Dust2
Old 11-09-2018 , 10:15   Re: 200 tick with 66 tick player rate IDEAS
Reply With Quote #6

Hey,

yes you need tickrate_enabler to run -tickrate command, i just presumed you have it already so i said to change - tickrate in startup only.

Again, avoid going over 100 tick, there is no real benefit and you will just overload your cpu, more over if you add store or vip and other stuff...100 tick is ideal for source. If client-side rates for css are locked on 100 max, running 200 tick means clients cant even benefit from it cause they can update on every second tick, the rest is waste...

Most of the servers in source now run what they call "100 tick" but they let clients in with cl_updaterate 20 and cl_cmdrate 20, so it is not full 100 tick unless clients specify rates themselfs, so these servers feel like 20 tick for most players that dont specify rates in autoexec.cfg, which is bad and gives game bad reg#rep

What you need to run smooth css server is rent with nfo and lock server at 100 tick meaning:

sv_minrate 100000
sv_minupdaterate 100
sv_mincmdrate 100
and lock cmdrate difference on 1

server will perform great and you will still have cpu space to play with.
If you run dm or gg, lower it to 66 tick cause there is too much action going on, your server cpu will skyrocket with 24+ ppl. If you run zm or 64 slot pub u can go to 33 tick but as you noticed, 33 is crap...specially if you bhop! ;)

Last edited by .raM; 11-09-2018 at 10:17.
.raM is offline