The default settings for cs:s are
rate 30000,
cl_updaterate 20,
& 32 players.
The de_dust2 server uses sv_minrate 15000, sv_maxrate 75000, sv_minupdaterate 33, sv_maxupdaterate 66.
Many people change their updaterate to 66, but leave their rate 30000.
You may recognize my spray. The servers max rate is sometimes too low for 33 tick (not shown in spray). I know because I played with 33-tick and still had choke. (My fps was always 33+ [100+ always actually], important for testing choke)
The server has 2x the players and 3.3x the updaterate equaling 6.6x bandwidth required. 30000*6.6=198000.
A simplified equation for rate settings 46.875(tick)(maxplayers)*
I asked hell's gamers to increase their maxrate, and it fixed everybody's hitreg problems (the ones that actually increased their rate, because unfortunately they left sv_minrate to 15000, and I have not asked them to change it yet) They set their sv_maxrate to 0 (unlimited). That is not a good idea, because not only does rate limit network bandwidth limit, but also downloading files from the server. The max source allows is 1megabyte/s. If there are 20 open slots on their server a hacker could potentially be downloading 20 different instances using 20mb/s upload from the server's bandwidth (theoretically possible, never heard of this happening). 198000byte*64 players would equal 12.67mbyte/s.
To learn about source networking rate, & choke:
This applies to all of your 64 player 66 tick source servers*
Change CVARS to:
sv_minrate 198000
sv_maxrate 198000
rate 30000,
cl_updaterate 20,
& 32 players.
The de_dust2 server uses sv_minrate 15000, sv_maxrate 75000, sv_minupdaterate 33, sv_maxupdaterate 66.
Many people change their updaterate to 66, but leave their rate 30000.
You may recognize my spray. The servers max rate is sometimes too low for 33 tick (not shown in spray). I know because I played with 33-tick and still had choke. (My fps was always 33+ [100+ always actually], important for testing choke)
The server has 2x the players and 3.3x the updaterate equaling 6.6x bandwidth required. 30000*6.6=198000.
A simplified equation for rate settings 46.875(tick)(maxplayers)*
I asked hell's gamers to increase their maxrate, and it fixed everybody's hitreg problems (the ones that actually increased their rate, because unfortunately they left sv_minrate to 15000, and I have not asked them to change it yet) They set their sv_maxrate to 0 (unlimited). That is not a good idea, because not only does rate limit network bandwidth limit, but also downloading files from the server. The max source allows is 1megabyte/s. If there are 20 open slots on their server a hacker could potentially be downloading 20 different instances using 20mb/s upload from the server's bandwidth (theoretically possible, never heard of this happening). 198000byte*64 players would equal 12.67mbyte/s.
To learn about source networking rate, & choke:
HTML:
https://developer.valvesoftware.com/wiki/Source_Multiplayer_NetworkingChange CVARS to:
sv_minrate 198000
sv_maxrate 198000
. Which is about half that's how I know double the rate of 75000 would fix the bandwidth choking. I guess cs:s default is 80000. Maybe it used to be 30000, or that's cs 1.6's setting, or maybe that's what alot of people recommend online for servers / user net settings. 30k is horrible for user settings you want as high as the server allows haha. Whoever recommend this for net settings obviously doesn't understand valve's networking page hahahaha. luckily there is a sv_MINrate (server forced minimum rate value). for people who don't know. Wouldn't make them laggy to anybody with good rate because uploading at 30000 is fine (maybe they gave out this rate so they'd own everybody else) HAHAHA
