FIX FOUND: Packet loss/choke since last update

[FlooD◦]

UPDATE: POTENTIAL FIX FOUND

Thanks to another user who has been having similar problems, a potential fix has been found that may help you!

net_maxroutable

the command net_maxroutable alters the max byte size of a single packet. The default is 1200. By lowering the value to 1100 all of my packet loss disappeared! This should have a negligble affect on your CPU usage. If 1100 does not work for you, try lowering this amount in increments of 100 until you find the value that works for you. Don't go too low however as this can massively increase the amount of packets sent.



---------------------------------------------------------------------------------------------------------------------

I have noticed significant packet loss on all servers offical Valve servers since the last update.

This packet loss is noticable because various sounds go missing as well as a split-second freeze of the game.

This loss occurs during several scenarios:

• When the bomb goes off - I never hear the explosion
  
• When an enemy player appears on my screen - I get a split-second freeze
  
• When an enemy player shoots - I never hear the shots an enemy hits me with
  
• When I die - I get a freeze

This packet loss also happens when I am observing a team mate and these scenarios occur.

There are several other occurances of this packet loss but they are too irregular. I know it is packet loss because when these instances occur my loss spikes to between 1%-5% before going away.

Steps I have taken to resolve this error:

• Verified game cache
  
• Reinstalled cs:go
  
• Factory reset router
  
• Tried using a different router

I do not suffer from any network problems outside of CS:GO and this issue only arose after the latest update. I am convinced this is a CS:GO bug that I cannot fix on my own.

Has anyone been having the same problems as me?
Does anyone have any advice?

EDIT: This issue only happens on offical valve servers (MM,DM, Casual etc.)

[Vault Hunter 101]

lower your rates in console

[Charlotte✭]

It's a CS:GO bug since Panorama is a buggy mess.

[FlooD◦]

Originally posted by Vault Hunter 101:

lower your rates in console

My internet speeds are 55≈Mbps DL and 15≈Mbps UL so I can't see why rates would be an issue? I will try it nonetheless. I currently use 786432 and have done well before the update and this issue. What rate value do you suggest I use?

[FlooD◦]

Originally posted by flwr:

It's a CS:GO bug since Panorama is a buggy mess.

That's what I was thinking :/ I tried panorama but it looks terrible on my res so i'm sticking with the old UI for now. I was hoping that other people would say its a bug because then I know its not my end that's causing it

[FlooD◦]

Originally posted by Kläöüß ¯\_(ツ)_/¯:

Increase snd_mixahead
mat_queuemode 0

From UK?
sdr ClientForceRelayCluster "LHR"

My current mixahead is 0.02 so i'll increase it to 0.05.

What do the other two commands do?

[FlooD◦]

Originally posted by Kläöüß ¯\_(ツ)_/¯:

"mat_queue_mode" = "0" ( def. "-1" )
//The queue/thread mode the material system should use: -1=default, 0=synchronous
With -1 my CPU tops out at 100% usage at csgo.exe (Intel i5-4690), with 0 it's at the usual 35%. Tests yours.

sdr is steamdatagram, relay cluster is a entry point to Valve's network, without specifying (force) a cluster you will get connected to any cluster that answers first. This can be China, Usa, Taiwan, Mars, Jupiter, another Solar System, who knows :D
LHR is London. So you force the game to only use London as the entry point.

Thanks for answering!

I'll try your suggestions and I will lower my rates (just in case). What is the benefit of using mat_queue_mode -1 or -2? I've seen on reddit that it gives you more fps or something?

[TehSpoopyKitteh]

Clear all custom and default configuration files and any autoexec cinfigs you created. Those sometimes do not get transfered very easily when an update occurs because Vale sometimes change the CVAR's or integers that cotrol those functions.

After you clear those file. run a game file integrity check, exit Steam after it is done, then restart your PC. This will reorganbize the registry to the current version of CSGO to the latest version.

[Flanger]

The symptoms you observe, should not be caused by packet loss. Sound playback is fully controlled by client, not downloaded on the fly from the server. But to be sure, try joining any casual server or deathmatch for example, while having console opened. You will see some SDR debug information, when client gets into queue. It tries out VALVE's different routing clusters and tries to connect you either directly to the servers or via their SDR proxy, if it has least latency. It looks something like this:

https://i.imgur.com/KjtAGXu.png

Once the game connection commences, you can see which routing cluster you are being connected to (including IP address). Copy that address and try to ping from your system with -t flag for continuous ping and gage whether you have packet loss and jitter. You can also influence which SDR routing cluster your client chooses, by forcing it with console command "sdr ClientForceRelayCluster [routing cluster name]". For example "sdr ClientForceRelayCluster vie".

[FlooD◦]

Originally posted by Flanger:

The symptoms you observe, should not be caused by packet loss. Sound playback is fully controlled by client, not downloaded on the fly from the server. But to be sure, try joining any casual server or deathmatch for example, while having console opened. You will see some SDR debug information, when client gets into queue. It tries out VALVE's different routing clusters and tries to connect you either directly to the servers or via their SDR proxy, if it has least latency. It looks something like this:

https://i.imgur.com/KjtAGXu.png

Once the game connection commences, you can see which routing cluster you are being connected to (including IP address). Copy that address and try to ping from your system with -t flag for continuous ping and gage whether you have packet loss and jitter. You can also influence which SDR routing cluster your client chooses, by forcing it with console command "sdr ClientForceRelayCluster [routing cluster name]". For example "sdr ClientForceRelayCluster vie".

Selecting lhr#56 (162.254.196.82:27032) as primary for connection 3624808759. [Ping = 10+23=33 (front+back=total).]
Selecting sto2#235 (155.133.252.66:27033) as backup #1 for connection 3624808759. Ping = 32+0=32 (front+back=total).

These were the routing clusters that were chosen. I pinged both of them in terminal and they reported the same ping values and I observed no loss of packets whatsoever. As I am in the UK I will use ' sdr ClientForceRelayCluster "LHR" ' however it seems steam is already choosing that relay as the primary connection for my client.

Do you have any idea what else could be causing this sound/loss problem?


EDIT: FYI here is a pastebin of the SDR debug info https://pastebin.com/7CZbwkD2

[FlooD◦]

Originally posted by The Spoopy Kitteh:

Clear all custom and default configuration files and any autoexec cinfigs you created. Those sometimes do not get transfered very easily when an update occurs because Vale sometimes change the CVAR's or integers that cotrol those functions.

After you clear those file. run a game file integrity check, exit Steam after it is done, then restart your PC. This will reorganbize the registry to the current version of CSGO to the latest version.

Already tried that. Didn't work :(

[坑坑更健康#CSGO真箱]

I'm also suffering the packet loss. It often has 1%~3% when playing, and 50%(!) loss when death-replay. Some sound effect are missing when packet loss happens. really annoying.

[FlooD◦]

Originally posted by 坑坑更健康:

I'm also suffering the packet loss. It often has 1%~3% when playing, and 50%(!) loss when death-replay. Some sound effect are missing when packet loss happens. really annoying.

I have tried pretty much every cs:go/network related fix and none of them have worked. I am suffering from exactly the same symptoms as you. I am 99% sure this is a bug related to the latest update :/

Does this happen to you on all servers or just Valve ones?

[Jo_Mei]

could be your rate should be in relation to your fps , no need for max rate if u stutter around with average 30 fps, or min rate with u playing above 200 fps on average , me just guessing

[AzKat 🐔]

Lower your rates, don't just brag about your internet, just lower them.

[FlooD◦]

Originally posted by Jo_Mei:

could be your rate should be in relation to your fps , no need for max rate if u stutter around with average 30 fps, or min rate with u playing above 200 fps on average , me just guessing

I've got a high-end PC and I get 400+fps on cs:go currently