So if I was using 22 tickrate I would use:
sv_minrate 2000
sv_maxrate 100000
sv_maxupdaterate 22
sv_minupdaterate 22
sv_maxcmdrate 32
sv_mincmdrate 32
As the CMD rates were not 33 I assume they either stay as they are or do i change them to be 22?
[QUOTE=adamski0811;46849716]So if I was using 22 tickrate I would use:
sv_minrate 2000
sv_maxrate 100000
sv_maxupdaterate 22
sv_minupdaterate 22
sv_maxcmdrate 32
sv_mincmdrate 32
As the CMD rates were not 33 I assume they either stay as they are or do i change them to be 22?[/QUOTE]
min/max cmdrate should be one below tickrate, so 21. That being said - I really wouldn't recommend running at 22 tickrate.
[editline]3rd January 2015[/editline]
Also raise your minrate, nobody is limited to a 2kbps connection anymore. 30000 is the lowest sensible value
[QUOTE=swingflip;46849235]Have you tried running the server without ANY plugins, take a net_graph 4 reading. Then reintroducing each addon one by one whilst also taking net_graph 4 readings. Robot is 100% right.
The input spikes are quite large. I would assume it would be a memory leak or a bad bit of scripting.
If the resource is too large it will cause blackouts and crashes within the server.
Have you also checked the server console for any errors?
Also to test your server just use ulx bots. They should run around causing the server enough load to get a accurate answer during server down times.[/QUOTE]
Instead of one by one ( time consuming ) use Divide and Conquer. Remove half, if ping fixed re-add half of the half you removed ( 25% ) back. If ping not fixed, then swap the ones you removed with the ones that are still on. Continue adding / removing 50% until it is solved. For known problem mods you could remove those first to try.
Will do so in morning and report back with the issues I most likely will incur
Sorry, you need to Log In to post a reply to this thread.
