[cod] networks cvar

[Luis Lorenzo]

This is my actual config:

set sv_maxPing                 "0"
set sv_minPing                 "0"
set sv_maxrate                 "20000"
set sv_fps                     "20"


I will try this.

----- Original Message ----- 
From: "Luis Lorenzo" <suil at newlightsystems.com>
To: <cod at icculus.org>
Sent: Tuesday, May 17, 2005 1:17 AM
Subject: Re: [cod] networks cvar


> Thanks!
> 
> I wi'll try this changes :)
> 
> ----- Original Message ----- 
> From: "BludGeonT[EUG]" <bludgeont at gmail.com>
> To: <cod at icculus.org>
> Sent: Sunday, May 15, 2005 8:52 PM
> Subject: Re: [cod] networks cvar
> 
> 
> Some of the cvars you have listed I believe are not even server cvars,
> but rather client cvars:
> 
> com_maxfps is client
> cl_maxpackets and cl_packetdup are believe are client side also
> 
> In my opinion, you are going to get (depending on the amount of
> clients you allow to your server) crappy performance with having a low
> sv_maxrate, combined with a high sv_fps value.
> 
> Here are my suggestions:
> 
> leave maxping and minping 0, they are unstable at least have been
> throughout Quake 3 engined games.
> 
> sv_cinematic, I've never had to change this variable
> 
> com_maxfps is the frame rate you wish to try to get from your client,
> this variable is not set on the server itself.
> 
> Id leave maxsnaps, cl_maxpackets, and cl_packetdup at their default
> values without changing them, punkbuster might not like it if you
> change these variables and could quite possibly complain about it if
> you break either the low or high threshold of these cvars if PB is
> monitoring them.
> 
> I think your sv_fps is way too high, for a server with over 30 people,
> I generally tend to reduce this value from it's default of 20 to 17. 
> For larger servers, I have noticed that reducing this a little helps
> with gameplay all around.
> 
> For an average sized server, I would recommend leaving this at 20,
> changing it to 24 will only kill performance on the server, in my
> opinion.  You can change this variable on the fly with rcon access,
> its not latched.
> 
> Id get rid of sv_minrate, this is controlled by punkbuster if someone
> tries something funny with going to low on rate, just leave it at 0.
> 
> com_hunkmegs, you might, if your machine allows, to increase this to
> 256  - 128 isnt horrible if you are going to run a smaller server, it
> should be fine.
> 
> I hope this helps, and please if I have provided incorrect
> information, please comment back.  Good luck :)
> 
> BludGeonT[EUG]
> Earthlink Ultimate Gaming
> www.EarthlinkUltimateGaming.com
> Developer
> 
> On 5/15/05, Luis Lorenzo <suil at newlightsystems.com> wrote:
> > Hi!
> >  
> > I have a cod server with this config:
> > set sv_maxPing                 "0"
> > set sv_minPing                 "0"
> > set sv_cinematic               "0"
> > set com_maxfps                 "75"
> > set maxsnaps                   "40"
> > set cl_maxpackets              "250"
> > set cl_packetdup               "2"
> > set sv_fps                     "24"
> > set sv_minrate                 "7500"
> > set sv_maxrate                 "12000"
> > set com_hunkmegs               "128"
> >  
> > What do you think about this config? there is some way to improve them?
> >  
> > Thanks in advance
> >  
> >