#Choke packets with 'safe' interp settings

1 messages · Page 1 of 1 (latest)

coral willow
#

Hello! I have a question regarding the interp settings that were applied using Comfig. Please note that everything described below is related only to Valve servers.

Mastercomfig was installed and snapshot_buffer was set to safe.
During the game I enabled net_graph 4 and noticed that choke packets appear randomly (something between 3 to 9, usually returns to 0 after a pair of seconds, but appears again after some time).

Since I was advised that there should not be any choked or lost packets at all I decided to experiment with interp settings in order to find the reason of that. I set snapshot_buffer to custom and started to change cl_interp_ratio, cl_interp, cl_cmdrate, cl_updaterate, rate (plus some graphics settings at some point just in case).

As the result it was noticed that for some reason the issue is always persist unless cl_cmdrate and cl_updaterate set to their default values (30 and 20 accordingly). Even 33 for both of them caused this issue. With default values choked packets happened only in cases like for example on koth_megaton, when entire server is destroyed by the bomb.

Could you please explain the reason of that? I expected that Valve servers should easily handle cl_cmdrate 66 and cl_updaterate 66, which is actually recommended by mastercomfig (any I understand why). Is there anything else that I should check?

Just in case some of my specs:
Wired ethernet ~80Mbits/s
ping 57 or 72 on the Valve servers (Stockholm and Frankfurt) that it usually connects me to
CPU: Ryzen 7 5800X, 32Gb Ram

Thank you in advance for the help.

image.png image.png image.png
ripe wedge
#

Interp has nothing to do with choke, and Valve servers can absolutely handle 66 in/out.

Choke is when the amount of data the server is sending you exceeds your bandwidth limit (controlled by the cvar: rate in bytes/sec).

Lowering cl_updaterate will reduce the incoming data, therefore lessening the likelihood of choke. But you might as well just increase your limit instead since your internet is fast enough.

bandwidth=6.0Mbps in modules.cfg

coral willow
#

Yes, tested with this as well. Ended up with 8.0Mbps (rate 1048576) in my autoexec. Basically no significant changes were noticed with default 1Mbps (rate 131072) or my custom value.

ripe wedge
#

Then that choke is probably unavoidable.

#

Sorry. Only just looked at your screenshots...
That's a connection issue, not settings, and unlikely to be server

strange spindle
#

from what i've seen, that amount of choke spontaneously occurring over public matches is normal and shouldn't impact gameplay in any meaningful way

coral willow
#

Ok. Just in case checked my connection and didn't find anything suspicious. Well, I'll leave it as it is with safe option assuming it's unavoidable or something on my provider side (basically, cannot be fixed by me as well).
Thank you.

coral willow
#

I am not sure if it is related but just in case I would like to mention it. During my tests launch option -dxlevel 100 was applied. Only yesterday I learnt that it actually should be deleted after it was applied once. So, the game started to feel more stable plus less choke packets appear now (usually 4 or less, at least I did not noticed more than that).

vast pulsarBOT
#

@coral willow has leveled up! (0 ➜ 1)

levelup.png
strange spindle