Bat Enthusiast | bur·ner | ⚙️ [settings.gg]
Twitter
HLTV [www.hltv.org]

CSGO-MZE9x-ODyBw-Ekmzh-2mVB3-K8OEL
CSGO-Knc5E-sjsie-t79Nc-BzS4r-uoKjC

Now playing with these settings (in autoexec)

sv_clockcorrection_msecs 0 - its a tradeoff, great for awpers, worse for riflers, default is 30ms, my observation: the game shows opponents a little earlier, but for a price of very unpolished movement of opponents (its harder to predict their next position - 0ms doesnt allow client to smooth out the movement based on previous 2 ticks). Thats why its great for snipers, not so great for riflers. Versus high ping opponent its even worse as they tend to move even more erratically than normally. The parameter is possible to set in client also at server (set to 0 at BOTH sides at LAN to reduce peekers advantage at LAN game!).

cl_cq_min_queue -1 - this parameter is again a trade off, you trade hitreg for reactivity of client. With 2 the hitreg is better, but there is obvious queue delay in netgraph (the netgraph will permanently show 2 green boxes line = 20ms which are obviously buffered (read: delayed) somewhere). I didnt make any deeper investigation yet, whether the delay is or is not compensated any way (i think its not, as its client sided).

cq_min_queue_size 0

cq_buffer_bloat_msecs 0

cq_buffer_bloat_msecs_max 0 (people use usually their ping for not perfect connection so 15 or 30 may be optimal)