http://img184.imageshack.us/img184/139/95683313js3.png
2009/2/18 ServerAlex <[email protected]> > Ok thats easy.. for tickrate 1000 servers you should not use a maxrate > less than 50000 (on source, no idea whats it on goldsrc). > Choke means not enough bandwidth to transmit all packets. And maxrate > (server) / rate (client) limits this bandwidth virtually. > So you just test it by connecting to the server, watching your choke > in the net_graph and then raising the maxrate/rate step by step till > the choke is gone (choke <= 5 is fine). > > anyway you should raise your minrate a bit. > > alex > > 2009/2/18 Pierre Egerland <[email protected]>: > > Thats only at pingboost 3.. the ingame clock go stupidly at pingboost 3 > with > > over tickrate 2500.. We´ve tested it. If you use pingboost 2 and tickrate > > 10000 then the ingame clock normal. > > And the Gameserver run smoother with pingboost 3 tic 2500 or pingboost 2 > and > > tic 10000. > > > > 2009/2/18 Steffen Tronstad <[email protected]> > > > >> That would make the ingame clock go stupidly fast. Mp_c4timer 35 will > >> actually be 24 or something. And roundtime 3 min = 2,5 min. > >> > >> sys_ticrate 2000 seems to be the limit before the ingame clock goes > wild. > >> > >> > > _______________________________________________ > > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
