[Arad119]

Originally Posted by Bacardi Could you try one thing ? When that lag happen and you see update rate held on 24, go to spectator team, type in your own game console cl_updaterate 130, then go back in team T or CT. Does update rate increase 24 -> 128 ? *Seems using JUMP button in spect team fix bug as well. *Seems using JUMP button in ct or t team while spectating other player fix bug as well. *edit What purpose is with this plugin ? Source Scramble Manager *edit When map change or player connect to server, does server move player in team automatically ? So player have no time to choose team ?

I did some more testing, the update rate problem seems to happen during the server hibernation when no one is playing on the server. Upon disabling the server hibernation with sv_hibernate_when_empty 0, the update rate stays at 128 even after a couple of hours.

I'll enable the hibernate feature and test cl_updaterate 130 like you mentioned, will update you in a couple of hours.

Regarding Source Scramble Manager, I believe it was there from the beginning as I don't recall downloading it. Seems to allow plugins to allocate memory and such, more info about it here.

No, the server doesn't automatically move a player into a team upon joining. The players have roughly 15 seconds to choose whatever team they want to join.

[pedrotski]

Originally Posted by Arad119 UPDATE: The same problem still happens even with sv_minupdaterate and sv_maxupdaterate removed from the server configs.

Why did you remove these? Setting them to 128 should force clients to be 128 tick.

Furthermore cl_ are client side only. If other people have the problem, that's not the issue.

Delete your entire server CFG and just add this

sv_maxrate 0 sv_minrate 75000 sv_maxupdaterate 128 sv_minupdaterate 128 sv_maxcmdrate 128 sv_mincmdrate 128 sv_parallel_sendsnapshot 1

Setting min rates will force things not to go below that threshold.

Values like that shouldn't change for no reason.

[Bacardi]

Read whole topic @pedrotski

[pedrotski]

Originally Posted by Bacardi Read whole topic @pedrotski

I did. And it sounds like a server side config issue to me. Hence he should start with his server.cfg file and go from there. Start eliminating variables.

[Arad119]

Sorry for the late reply, haven't been on the computer thus not being able to test commands and such.

Originally Posted by Bacardi Read whole topic @pedrotski

I tried cl_updaterate 130 but the problem still occured.

Originally Posted by pedrotski I did. And it sounds like a server side config issue to me. Hence he should start with his server.cfg file and go from there. Start eliminating variables.

Also tried your commands, seems to have fixed the problem. Don't know which one of the commands actually made the difference but anyways. Thanks for the help, much appreciated

[pedrotski]

Originally Posted by Arad119 Sorry for the late reply, haven't been on the computer thus not being able to test commands and such. I tried cl_updaterate 130 but the problem still occured. Also tried your commands, seems to have fixed the problem. Don't know which one of the commands actually made the difference but anyways. Thanks for the help, much appreciated

Awesome glad its fixed !