What Tickrate is this server supposed to be? Is it 100 or 66?
Whenever I play a map, it's around 66 Tick, but when I die and go Spectator. I can go out of the map to that pitch black area, and it goes up to 100.
What Tickrate is this server supposed to be? Is it 100 or 66?
Whenever I play a map, it's around 66 Tick, but when I die and go Spectator. I can go out of the map to that pitch black area, and it goes up to 100.
With no power, comes no responsibility.










what tickrate you read will be limited by your framerate.
It's 100, it usually takes a few moments to get there for me, but it is 100 tick.
So it's my FPS? I usually like to cap my fps off at 54. It can stay there steadily, and I don't get bad fps when people are complaining about their fps being at 16.
Should I use fps_max 101 instead? Would that increase my tick?
P.S. Another thing, would my rates have anything to do with it?
Last edited by Lucid; 9 Nov 2009 at 03:41am.
With no power, comes no responsibility.
wouldnt hurt to make sure there right
cl_cmdrate 100
cl_updaterate 100
rate 40000
Thanked by 1 user: Lucid (9 Nov 2009)










I think it got fixed in newer source engine versions (orange box and above) but i'm not sure, on CSS though and everything using the older settings the answer is YES ABSOLUTELY.
ALL your rates are capped by your framerate for some retarded reason. You can use "net_graph 3" and look at them all jump around while capping your framerate at various settings. Ideally if you can stand the tearing effect you want everything uncapped and vsync off, otherwise you want to try for at least a framerate higher than the server's ticrate.