[cod] Network server settings

[Ian mu]

Tickrate is the "equivalent" (using that term very loosely) of sv_fps, but
as mentioned may affect gameplay and other issues when changed.
 I think you have to be a bit careful about what you "really" mean by lower
pings. I.e in Q3 engine games (and again haven't tested if this still holds
true in cod2) there's things like cl_maxpackets (client setting), where the
higher it is the lower the "actual" latency is, however the higher the pings
are reported (so you used to see loads of people on a ping of 48). What you
see isn't necessarily what is happening. Just I used to know a few people
who used to lower their maxpackets to 30 and brag about their ping when in
reality the total turnaround latency would be higher. What you see isn't
necessarily what you get.
 Personally I would say keep sv_fps at 20, maxrate at something like 25000
and encourage people to use higher maxpackets. Without pb you can't really
even force people to have snaps of 40 (even if it didn't screw other stuff
up) to make sure they have their network settings correctly aligned with the
server.
 In truth I would prefer a game to have a standard set of server rates, and
I think has helped a lot of Q3 engine games (yes I know this isn't, but has
a lot of essences the same) because of a fairly uniform state of gameplay,
whereas css in truth is all over the shop with their network settings.


 On 11/11/05, Stephane <armageddon21 at sympatico.ca> wrote:
>
>  Ok,
>
>  Is there a setting similar to "tickrate" like CSS to increase the quality
> fo play and "lower pings"
>
>  thanks
>
>   ------------------------------
>
> *From:* Jim Mayes [mailto:jim.mayes at onemean.net]
> *Sent:* Friday, November 11, 2005 8:38 AM
> *To:* cod at icculus.org
> *Subject:* RE: [cod] Network server settings
>
>  Also an issue with sv_fps throwing the bomb timers off. Bombs would
> explode before the clock had fully counted down. Bombs would set & defuse
> before the progress bar reached the full time. So if you run S&D, keep an
> eye out for those issues too.
>
>  ~jim
>
>   ------------------------------
>
> *From:* Ian mu [mailto:mu.llamas at gmail.com]
> *Sent:* Friday, November 11, 2005 3:51 AM
> *To:* cod at icculus.org
> *Subject:* Re: [cod] Network server settings
>
>  My initial guess would be clients that have their snaps set at 20 for
> those that it increases by as they'd be received less packets, those who
> have it set to 40+ would be fine. If it works the same as the Q3 engine
> vars, it only works in discrete steps, and anyone under that value may
> suddenly only be receiving 15 packets/second or a different amount actually
> less than the default 20. There was also the issue in some games of upping
> sv_fps changing the wep physics so need to be a bit wary (it did in rtcw for
> example). Not sure if that latter part applies to cod2 in any way at all,
> just need to be cautious in case.
>
>  Ian
>
>  On 11/11/05, *Stephane* <armageddon21 at sympatico.ca> wrote:
>
> Hello,
>
>  I was trying to tweak my "tickrate" or I think in COD its sv_fps, maybe
> something else I am not sure.
>
>  If I put sv_fps to 40 instead of 20 , half the people will decrease in
> ping from 40 to 25 ish . but half others will increase from 40 to 80 !!!
>
> Why is it decreasing ping for some and increasing for others ?
>
>  Am I tweaking the wrong var ?
>
>   Thanks guys!
>
>   ------------------------------
>
> *From:* Click Bouyow [mailto: click at deadboneplatoon.com]
> *Sent:* Tuesday, November 08, 2005 4:52 PM
> *To:* cod at icculus.org
> *Subject: *[cod] Hacks
>
>  I ran across this today.
>
>  By entering these commands into console, a player can turn off background
> noise:
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/cod/attachments/20051111/64d9edc9/attachment.htm>