Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
и у меня ет проблема, проверял целостность кэша, все норм, и памяти хватает, я хз
Hi,
An update to the thread here
Several people have reported experiencing loss after this update, even in non-panorama mode for the short while it existed. The loss occurs when there was a lot going on - killing someone, getting killed, grenades going off (whenever more data had to be sent/received suddenly) would cause the loss to spike from 0% to anywhere between 5 and 15% or higher depending on rates, it only seems to happen on official servers.
CSGO (not sure if client or server, didn't analyse the traffic) seems to be sending larger datagrams than before this update, as a result some packets are getting dropped by some peer between the client and the server/relay, thus causing the loss.
I assume the update either changed the way CSGO calculates the max datagram it can send or has added extra data that isn't being accounted in the final payload size for some reason - maybe some auth data or something considering it only seems to occur on official servers? Or maybe I'm barking completely up the wrong tree.
Either way, if you force CSGO to fragment at a lower size (I started testing with 700 and only tested up to 1100) using net_maxroutable 1100 it should fix the issue. I imagine there will be a very slight CPU impact since the client will have to do more fragmentation for the same amount of data but I would guess it to be negligble.
I've tested this fix in 2 separate locations in the UK that did have the issue but it would be good to confirm if this fixes the issue for others elsewhere or if this particular issue is BT (UK ISP) route specific - I know some people in Australia and Germany were having the issue in the previous thread.
You could probably push the value slightly higher than 1100 (1150 might work?) that's just the highest I tested but I don't see much point.
It would be good to get a Valve response to work out if this is actually intended and they didn't anticipate the larger packets getting dropped or if it's a bug.
If anyone's interested I diagnosed this running CSGO over an openvpn connection with various configurations.
TLDR: Set net_maxroutable 1100 in console and the loss should be fixed.