Fixing server tickrates

So looking at a lot of the servers, most of them (including PB,TTT, and Scrim...didn't check ZE) have wonky rate settings that are super outdated. Back in 2016 steam/CSGO changed network settings to allow for 'higher game traffic to client' :

[ATTACH=CONFIG]18947[/ATTACH]

Ignore what it says about 'high surge rate', its literally irrelevant unless you have the shittiest of internet, plus you can just leave it at the default 196608 and never have a problem.

PB and TTT are both still at 128000 as max rate allowed (based on pre-2016 '128k') and scrim is at 80k? The Deathmatch server has the proper settings for anyone who wants to look, allows you to have the preset default (196608 ) all the way up to the max (786432).

[ATTACH=CONFIG]18948[/ATTACH]

Source : https://www.vsgaming.co.za/discover/how-set-your-new-csgo-rates

MM servers use the same rate settings, and it gives a noticeable difference compare to the SG servers. I don't know nor can I find anything saying this would cause any sort of significant extra load on the servers, and I believe it is almost all based around how much information the individual 'client' is receiving. I also joined multiple 1v1 servers and a few other misc ones and they all had the same settings, so at least for like the scrim server this should be fixed.

Forgive me if I'm missing something, been a while since I looked at this side of server stuff.

I might've forgotten to change those rates when I fixed the tickrates on scrim a while back @tides hf

This is just saying something, but would this fix ghost knifing on mg? If possible I'd like a small upgrade on our tick rates.

Also this is a thing in MG and TTT :

[ATTACH=CONFIG]18949[/ATTACH]

(Cl_cmdrate 102 and Cl_updaterate 102)

Rates did change as I mentioned above, but the cmdrate and updaterate remained the same, and they were what determine if a server is '128 tick'. The 102 settings are from CSS and were maybe copy pasted from old files? 102 was to determine 100 tick servers back the if anyone remembers, but having 102 tick now just makes for some weird lag and hits not connecting when you think they should. Could also be the thing causing the knifing issue that was mentioned on MG (I did look though and MG has the proper rate settings allowing you to cap at 786432)

PB has 64 tick settings, which I assume is correct since it isn't listed as a 128 tick server or whatever, but if that is the intention then someone should look at that too.

@Wawa @Gator @Im Sad @Karma

@Grateful @WavY @Karma @papa @Gator @Im Sad

I went ahead and updated the server.cfg files on MG, TTT, PB, and Surf to these network settings:

//64 Tick

sv_maxrate 786432

sv_minrate 64000

sv_maxcmdrate 64

sv_maxupdaterate 64

sv_mincmdrate 64

sv_minupdaterate 64

//102.4 Tick

sv_maxrate 786432

sv_minrate 102400

sv_maxcmdrate 102.4

sv_maxupdaterate 102.4

sv_mincmdrate 102.4

sv_minupdaterate 102.4

//128 Tick

sv_maxrate 786432

sv_minrate 128000

sv_maxcmdrate 128

sv_maxupdaterate 128

sv_mincmdrate 128

sv_minupdaterate 128

The only server I didn't look at was ZE, and the other servers looked fine.

Thank you @BoM for your help.

@Grateful @WavY @Karma @papa @Gator @Im Sad

 

I went ahead and updated the server.cfg files on MG, TTT, PB, and Surf to these network settings:

 

//64 Tick

sv_maxrate 786432

sv_minrate 64000

sv_maxcmdrate 64

sv_maxupdaterate 64

sv_mincmdrate 64

sv_minupdaterate 64

 

//102.4 Tick

sv_maxrate 786432

sv_minrate 102400

sv_maxcmdrate 102.4

sv_maxupdaterate 102.4

sv_mincmdrate 102.4

sv_minupdaterate 102.4

 

//128 Tick

sv_maxrate 786432

sv_minrate 128000

sv_maxcmdrate 128

sv_maxupdaterate 128

sv_mincmdrate 128

sv_minupdaterate 128

 

The only server I didn't look at was ZE, and the other servers looked fine.

 

Thank you @BoM for your help.

Glad to see the new manager making an effort.

@Wawa @tides the scrim server still has min/max of 80000 rate. Maybe people won't hack on there if we fix that?

Nah jk, people will still be dumb xd

I'm looking at the server.cfg right now and it has a min of 128000, max of 786432. Don't have access to my PC right now but it should be fixed.

Fixed the issue, the rates were declared in another cfg and it was overriding the desired rates.