When doing a long command that forces multi-packet responses in TF2, such as cvarlist, we're dropping packets. More importantly, we're getting packet responses that have larger-than-normal sizes (exceeding that of SRCDS's maximum of 4096.)
That said, srcds seems to be more than happy to send us packets upwards of 4100 bytes, which is strange. Unsure whether this is caused by node's buffering of the data (which it shouldn't since the socket doesn't drain) or if srcds is the fault here.
When doing a long command that forces multi-packet responses in TF2, such as
cvarlist, we're dropping packets. More importantly, we're getting packet responses that have larger-than-normal sizes (exceeding that of SRCDS's maximum of 4096.)That said, srcds seems to be more than happy to send us packets upwards of 4100 bytes, which is strange. Unsure whether this is caused by node's buffering of the data (which it shouldn't since the socket doesn't
drain) or if srcds is the fault here.