q3config>>ADSL

[rider]

This is the recommended Q3config for an ADSL connection on q3central:

seta cl_packetdup "1"
seta cl_maxpackets "60"
seta snaps "60"
seta rate "25000

Excuse me?
Well I tried it for a laugh, and experienced a connection similarly matched to ISDN @ 64Kbps, even just sitting on a WP server with no one on it, I got 60-90. Nice one q3c.

So here are my recommended settings:

seta cl_packetdup "1"
seta cl_maxpackets "40"
seta snaps "40"
seta rate "10000"

30-50 ping with a server compliment of 8 [instagib in this case] and it's smooth and indistinguisable from a LAN.

If q3central encourage ADSL users to do this, the bloody exchange[s] is/are going to be crawling with lagging ADSL players.

Not very clever recommendation IMHO.

[WiiijA]

Right these are settings I use for Q3 with broadband...cable but makes no odds.

packetdup 1
maxpackets 30
snaps 100
rate 25000

I ping wireplay 25-35 at all times with them settings,and thats with a slight network problem at a certain hop,when NTL routed a different way so as to avoid this hop I pinged 14-20 max at anytime :/.

Anyway try them see how how u get on m8.

Also a tip for any1 dont put maxpackets below 25 as this causes you to stutter in other peoples view,although it feels fine to you.........it is actually classed as cheating in league games now to have maxpackets that low :o

regards


WiiijA

[rider]

experimentation is a good idea; however, I would never have tried those settings
I'll try them out anyway just to see if I get a better return from the server

my point though, is that from an ADSL contention aspect, if you have players accessing a server and sending data back and forth in a stream to that level of update, it's going to cause a backlash to all those concerned - non players and web users alike

well, ****'em

;)

I noticed a helluva lot of wanky modemers and above using that trick with the maxpackets [I know I didn't] - and it's a frikkin nightmare hitting the *******s, especially in instagib, when a RL will do the job just nicely

I don't know if anyone hops to and from uk.uunet and .alter.[teleglobe], but they're the culprits screwing up the pings from their routers - it's not your ADSL or CM connection, that I can tell you

the IP's that are causing the damage are:
uk.uunet @ 158.43.164.1 and 158.43.254.218
teleglobe @ 158.43.193.245 and 158.43.254.214
and if anyone hops through them, you're going to be sorry - I tracert'd them from Winnersh>>Wokingham and the ms average was 600-900ms and even hit 1200ms at one point during testing
just so you know

lucky I'm just outside that range
unlucky for those that aren't

this will go on until uunet sort they're sodding problem with a spammed to hell email server that's taken a week to notice and this week to sort out [I hope]

maybe I should have started another thread
sorry but I can't be arsed
:D