"sv_minrate" = "30000" ( def. "3500" )
replicated
- Min bandwidth rate allowed on server, 0 == unlimited
Im pretty sure it ups them, I set min cmd to 66 and it put everyone up to 66
instead of default 30.
On Wed, Mar 4, 2009 at 5:29 PM, Nephyrin Zey <[email protected]> wrote:
> That's a good point, though I'm not sure if minrate is 'minimum cvar
> rate setting for client' or actually enforces the minimum rate that must
> occur before they're kicked. If its the latter, finding a good rate to
> enforce (i'd think nearer to 48000 would be appropriate) might help.
>
> - Neph
>
> On 03/04/2009 05:22 PM, DontWannaName! wrote:
> > What if we as server ops changed sv_minrate to 60000, wouldnt that fix
> it.
> > Of course the people who dont have good connection wont do well with it
> but
> > I dont know how many people that would affect.
> >
> > On Wed, Mar 4, 2009 at 5:13 PM, Nephyrin Zey<[email protected]>
> wrote:
> >
> >
> >> <this post is about rate settings, not any bugs relating to rate or lag
> >> that are going around, please keep those to their own threads>
> >>
> >> So last night in my TF2 server, one of my regulars was complaining about
> >> 'the lag', and i asked him to open his console and type rate. '3500' he
> >> reads to me. Well, no wonder.
> >>
> >> This is not the only time i've helped someone up their rate from 3500. I
> >> also have a scrolling message in my 32x servers advising that you up
> >> your rate from the normal max of 30000 to even higher. Right now, both
> >> server and client rate settings have horrible defaults, and it is
> >> causing lag for everyone.
> >>
> >> - rate seems to like to default to 3500 for some people, for some
> >> reason. I've experienced this myself, no idea what causes it.
> >> - 32x servers use way more than 30000 rate in heavy action, net_graph 4
> >> + spectate makes this very clear
> >> - Servers have net_splitpacket_maxrate set to 15000 by default, and
> >> there's little documentation on this. This causes 'skips' when you first
> >> happen upon a lot of action, as Tony documented.
> >> - Since the l4d-networking-merge patch, either TF2 is using way more
> >> bandwidth, or the way it's calculating rate is more aggressive. 30000
> >> used to be enough for 32x (though it wasn't perfectly smooth), but now
> >> its just plain laggy.
> >>
> >> So please, everyone make sure your rate/maxrate settings are proper, and
> >> valve, please take a look at client rate defaults. I'm sure 90% of my
> >> players are using rate 30000, and this is just a much laggier experience
> >> than what you could be getting. The other 10% probably have either 10000
> >> (and probably have long since learned never to join 32x servers due to
> >> lag) or 3500. Neither of these is even for even a good 24x server, so
> >> that sucks.
> >>
> >> - Neph
> >>
> >> _______________________________________________
> >> To unsubscribe, edit your list preferences, or view the list archives,
> >> please visit:
> >> http://list.valvesoftware.com/mailman/listinfo/hlds
> >>
> >>
> > _______________________________________________
> > To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> > http://list.valvesoftware.com/mailman/listinfo/hlds
> >
>
> _______________________________________________
> To unsubscribe, edit your list preferences, or view the list archives,
> please visit:
> http://list.valvesoftware.com/mailman/listinfo/hlds
>
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
