Input lag - buffering smooth over packet loss

[VIZIONÁRES.]

Does the input lag increase if I switch 'buffering smooth over packet loss' to 1 or 2? Do you have any sources?

[WombRaider [No Monitor/Sound]]

Yes it increases your interpolation, type 'cl_interp' in console while connected to a server to see interp and interp_ratio

[VIZIONÁRES.]

Thanks for your fast reply.

None packets:
cl_interp = 0.000000 (cl_interp_ratio=0 / cl_updaterate=64)

1 packet:
cl_interp = 0.015625 (cl_interp_ratio=1 / cl_updaterate=64)

what does this exactly mean?

[kabanod1m #NotoToxicity]

no, it does not increase input lag

instead, in simple terms, it increases ping

[WombRaider [No Monitor/Sound]]

cl_interp is calculated by interp_ratio divided by update rate to the server.
Interp is the pre-set delay amount to what you see rendered on the screen.
Less or no interp is better IF you can still hit stuff and things aren't rubber banding/jumpy.

[VIZIONÁRES.]

I have currently some internet issues, especially in the evening. There are some high ping peeks and I have also packet loss. The packet loss on "1 packet" is much better than on "none", but I have the feeling, that my hit registration/movement is trash.
The feeling with "cl_interp = 0.000000" is way better than on 0.015625.

Can i change the value also with '1 packet" to 0?

[WombRaider [No Monitor/Sound]]

No right now you can't change the value outside off the 'None' '1 Packet' '2Packet' options like in older CS versions. '1 packet' will equal to 0.015625

Recently a lot of people have seen packet loss with Buffer Packets set to default 'None'.
I think Valve has changed something to cause this issue rather than your internet connection being the source of the packet loss.
My guess would be Valve is overloading the Server computers for matchmaking to save on overhead costs.
Likely the same reason they switched to Sub-tick in CS2 and only had 64 tick servers in CSGO.

[VIZIONÁRES.]

Thank you for your help. I hope that they will fix this issue soon...

[aldrack]

Having the same problem. Started after the last update (or the one before that)