NEED HELP W/ Q3!

[old.GaMeR]

I need help with Q3! this is my prob! Lately i have been getting back into Q3 since i just upgraded! Well now when i join a server i have netgraph on and when I join a server The bottom layer is all yellow and the top is all spikey, from here it will either be the same and i get Connection Interupted or it will flatten out and be fine for 2 minutes and either go the same as i connected or do it every once in a while! I used the Netconfigtool.cfg file that was on the Guides to Q3 page and i pressed the either Network Information or Missed (incorrect) client-side Predictions buttons that are in it after loaded and i got Packet_Backup i think from it and thats about it! I will list my system specs, and ect.!

Pentium Celeron 500
3dfx Voodoo Banshee
96 Meg of Ram
Win 98
one way cable, and when connected send at 24600 kbps or 26400 kpbs! sorry huh!
i use mediaone one as my isp and this stuff has just happend lately, i think it could be related to mediaone being bought out by AT&T! hope it isn't, and can be something that can be fixed! Can someone PLZ help me!

 

[old.venturer01]

u using gamespy
i get this i think
when i connect using gamespy it goes to
33.6 k modem so i have to change it to back to 56k on network setting in q3.
if it still happens put it up to isdn
may help, may not help.
but it sound more complex, the prob u have.

 

[old.SimbobX]

24600 kbps or 26400

umm .. if you're right about those, I suspect that's your problem .. 26K upstream is very low (even current 56K modems manage 33K upstream)

not knowing enough (erm .. or, indeed, anything) about cable modems, I can't really help, I'm afraid You could try hassling your ISP/Provider.

One possibility is that Cable Modems are shared bandwidth, and the service is so over subscribed that every user is getting a very small slice of the ol' bandwidth pie .. if so, it sucks, but I doubt there's much you can do aout it, unless your service levels are guarenteed to a certain level and are falling below that.

Any cable-gurus know what can be done to test/fix this?

You could try having a look here:
Upset Chaps Connection Guide but I'm not sure how much it deals with CMs.

 

[old.venturer01]

if it's a node prod
and loads of ppl in your area
are taking up bandwidth
hit them with a big stick
or cut their phone lines
or tell them aol is better
lol

 

[old.GaMeR]

Thx, yeah, my ISP is mediaone and they were just taken over by AT&T and have heard of ppl with problems lately, Screw AT&T, i might wait for DSL, quite a bit better, its that or somethings like aDSL by bellsouth or something

 

[old.Pumpkin]

Yeah, one way cable modems are a bit of a nightmare. I don't know a lot about the standards of various ISP's in the US.

Suggestions.

1.) Pick a local server that you ping well to. Find out it's IP address from gamespy or whatever server browser you use. Bring up a command prompt (dos prompt), and tracert to it. eg :-

c:\> tracert 194.88.93.4

Using the dotted box and the copy button in the toolbar, copy and paste the results here for someone to look at. Repeat this for a few other servers, and include at least one barrysworld one if you could.

Now visit a website that allows you to do a remote traceroute TO your computer. www.tracert.com has a list of these. Pick a couple of USA sites to do this from, and pick a UK one as well (the Shellnet one was the only one working when I looked).

This will give us a rough idea of what performance we are looking at, and where the problem is likely to be.


2.) Fiddle with the rate, cl_maxpackets and snaps settings. Because Q3 wasn't really built to support async connections, you are going to be at a serious disadvantage in terms of exploiting the bandwidth of your downstream connection to increase the rate. You should still get a better connect that a normal modemer would because the downstream latency should still be lower.

 

[old.GaMeR]

yeah, thx, going to try that , not sure what is wrong I have used the cl_ commands and rate, ect, sometimes i can play, sometimes i can't! will try this

 

[old.GaMeR]

well i did it and here are the resultsC:\>tracert 24.129.8.89

Tracing route to quakelab.se.mediaone.net [24.129.8.89]
over a maximum of 30 hops:

1 134 ms 139 ms 129 ms jas105.jacksonville.net [24.129.56.225]
2 89 ms 80 ms 92 ms 24.129.56.252
3 81 ms 84 ms 83 ms rtr-bus-fe50.jacksonville.net [24.129.10.42]
4 85 ms 79 ms 92 ms gsr-jaxb-fe64.jacksonville.net [24.129.10.33]
5 2089 ms 2091 ms 78 ms rtr-sshe-pos510.jacksonville.net [24.129.20.218]

6 83 ms 81 ms 74 ms rtr-lab-pos400.jacksonville.net [24.129.10.134]

7 78 ms 89 ms 96 ms quakelab.se.mediaone.net [24.129.8.89]

Trace complete.

C:\>tracert 24.129.77.178

Tracing route to bc77-178.jacksonville.net [24.129.77.178]
over a maximum of 30 hops:

1 128 ms 124 ms 129 ms jas105.jacksonville.net [24.129.56.225]
2 2077 ms 86 ms 69 ms 24.129.56.252
3 81 ms 76 ms 81 ms gsr-jaxb-pos10.jacksonville.net [24.129.10.54]
4 82 ms 86 ms 79 ms rtr-bcl-pos800.jacksonville.net [24.129.10.122]

5 73 ms 80 ms 84 ms bc77-178.jacksonville.net [24.129.77.178]

Trace complete.

1 128 ms 122 ms 124 ms jas105.jacksonville.net [24.129.56.225]
2 75 ms 78 ms 78 ms 24.129.56.252
3 81 ms 78 ms 81 ms rtr-jaxa-pos200.jacksonville.net [24.129.10.45]

4 90 ms 83 ms 82 ms 12.127.145.21
5 81 ms 78 ms 193 ms gbr1-a31s1.ormfl.ip.att.net [12.127.3.6]
6 72 ms 82 ms 75 ms gbr4-p70.ormfl.ip.att.net [12.122.5.125]
7 101 ms 82 ms 96 ms gbr3-p10.attga.ip.att.net [12.122.2.129]
8 90 ms 99 ms 98 ms ggr1-p360.attga.ip.att.net [12.123.20.249]
9 91 ms 89 ms 93 ms ibr01-p0-0.atln01.exodus.net [209.1.169.41]
10 97 ms 89 ms 97 ms bbr01-g2-0.atln01.exodus.net [216.35.162.3]
11 105 ms 114 ms 115 ms bbr02-p5-0.stng01.exodus.net [209.185.9.42]
12 2113 ms 113 ms 108 ms bbr01-g4-0.stng01.exodus.net [216.33.96.163]
13 115 ms 115 ms 128 ms bbr02-p5-0.jrcy01.exodus.net [209.185.9.97]
14 122 ms 135 ms 115 ms dcr03-g3-0.jrcy01.exodus.net [209.67.45.97]
15 111 ms 111 ms 119 ms rsm04-vlan991.jrcy02.exodus.net [216.32.222.123

16 132 ms 122 ms 141 ms main.nyc.megapath.net [216.35.48.254]
17 2235 ms 133 ms 133 ms sdsl-64-7-6-86.dsl.nyc.megapath.net [64.7.6.86]

18 123 ms 135 ms 134 ms teamfort.com [64.7.24.67]

Barrysworld Server(i'm in FL)
C:\>tracert 194.88.93.40

Tracing route to 194.88.93.40 over a maximum of 30 hops

1 238 ms 128 ms 143 ms jas105.jacksonville.net [24.129.56.225]
2 73 ms 83 ms 73 ms 24.129.56.252
3 72 ms 82 ms 82 ms rtr-jaxa-pos200.jacksonville.net [24.129.10.45]

4 81 ms 81 ms 83 ms rtr-jaxc-fe500.jacksonville.net [24.129.10.6]
5 87 ms 78 ms 79 ms 7507a-srl510.tampabay.rr.com [24.94.158.230]
6 136 ms 102 ms 133 ms tmbrt01-FastEthernet4-0-0.rr.com [24.128.6.18]
7 111 ms 108 ms 106 ms 24.218.190.5
8 116 ms 109 ms 120 ms ccbgsr01-stbrt02.rr.com [24.218.188.149]
9 130 ms 106 ms 108 ms 24.218.189.101
10 116 ms 118 ms 116 ms ccbrt01-ccbgsr01.rr.com [24.128.191.13]
11 122 ms 118 ms 124 ms edge1.aads.level3.net [206.220.243.105]
12 111 ms 124 ms 2115 ms so-6-0-0.mp1.Chicago1.level3.net [209.247.10.165
]
13 213 ms 215 ms 232 ms 209.247.10.46
14 271 ms 261 ms 303 ms 209.246.119.97
15 308 ms 286 ms 295 ms loopback0.dwaccess1.London1.Level3.net [212.113.
2.69]
16 292 ms 298 ms 265 ms 212.113.3.11
17 270 ms 290 ms * 194.88.93.40
18 272 ms 301 ms 290 ms 194.88.93.40

Trace complete.

Shellnet TRACEROUTE service

traceroute to 24.129.38.52 (24.129.38.52), 30 hops max, 40 byte packets
1 pipex-gw (194.129.209.1) 2.947 ms 2.338 ms 2.730 ms
2 man-gw3.pipex.net (158.43.183.3) 4.184 ms 3.656 ms 3.699 ms
3 fddi0-0-0.cr1.man1.gbb.uk.uu.net (158.43.180.1) 3.735 ms 3.538 ms 3.414 ms
4 pos6-0-0.cr1.bhx1.gbb.uk.uu.net (158.43.254.158) 6.647 ms 5.938 ms 6.263 ms
5 pos4-0-0.cr1.rea1.gbb.uk.uu.net (158.43.254.37) 8.781 ms 8.596 ms 8.538 ms
6 fe1-1-0.cr2.rea1.gbb.uk.uu.net (158.43.254.94) 9.233 ms 8.658 ms 8.841 ms
7 pos1-2.cr1.lnd4.gbb.uk.uu.net (158.43.254.29) 10.038 ms 9.384 ms 10.597 ms
8 ge2-0.cr2.lnd4.gbb.uk.uu.net (158.43.254.138) 10.076 ms 9.569 ms 9.495 ms
9 pos1-0.cr2.lnd5.gbb.uk.uu.net (158.43.254.249) 11.564 ms 10.889 ms 10.298 ms
10 so-7-0-0.XR2.LND2.alter.net (158.43.233.246) 12.039 ms 11.453 ms 12.417 ms
11 SO-1-0-0.TR1.LND2.Alter.Net (146.188.7.230) 12.436 ms 11.712 ms 11.546 ms
12 SO-6-0-0.IR1.DCA4.Alter.Net (146.188.8.169) 88.943 ms 89.666 ms 88.700 ms
13 SO-0-0-0.IR1.DCA6.Alter.Net (146.188.13.33) 89.194 ms 88.723 ms 89.705 ms
14 118.at-6-1-0.TR1.DCA6.ALTER.NET (152.63.10.221) 89.064 ms 88.852 ms 88.919 ms
15 187.ATM6-0.XR1.DCA8.ALTER.NET (152.63.33.237) 91.687 ms 91.775 ms 92.064 ms
16 189.ATM5-0.BR2.DCA8.ALTER.NET (152.63.35.189) 91.756 ms 91.028 ms 91.934 ms
17 uu-gw.wswdc.ip.att.net (192.205.32.133) 91.935 ms 91.763 ms 91.610 ms
18 gbr4-p50.wswdc.ip.att.net (12.123.9.54) 92.169 ms 91.564 ms 91.589 ms
19 gbr4-p90.attga.ip.att.net (12.122.2.177) 107.696 ms 106.840 ms 106.316 ms
20 gbr3-p60.attga.ip.att.net (12.122.1.141) 106.887 ms 106.053 ms 106.571 ms
21 gbr4-p50.ormfl.ip.att.net (12.122.2.130) 115.705 ms 115.655 ms 116.724 ms
22 gbr1-p50.ormfl.ip.att.net (12.122.5.126) 116.230 ms 115.546 ms 115.350 ms
23 ar1-a3120s3.ormfl.ip.att.net (12.123.32.13) 117.441 ms 134.122 ms 116.139 ms
24 12.127.145.22 (12.127.145.22) 133.597 ms 131.268 ms 127.559 ms
25 rtr-jaxc-fe500.jacksonville.net (24.129.10.6) 130.663 ms 159.860 ms 143.105 ms
26 gsr-jaxb-pos02.jacksonville.net (24.129.10.50) 126.531 ms 128.990 ms 144.590 ms
27 gsr-wsb-pos20.jacksonville.net (24.129.10.66) 127.941 ms 128.012 ms 138.112 ms
28 gsr-wsa-pos10.jacksonville.net (24.129.10.69) 147.932 ms 133.546 ms 129.315 ms
29 rtr-opb-pos800.jacksonville.net (24.129.10.78) 129.738 ms 148.377 ms 132.366 ms
30 surfop38-52.jacksonville.net (24.129.38.52) 208.805 ms 211.242 ms 223.742 ms


Traceroute from Dialtone Internet




traceroute to 24.129.38.52 (24.129.38.52), 30 hops max, 38 byte packets
1 216.87.208.1 (216.87.208.1) 1.238 ms 0.516 ms 0.420 ms
2 12.126.159.93 (12.126.159.93) 17.851 ms 8.744 ms 5.299 ms
3 gbr2-a30s5.ormfl.ip.att.net (12.127.3.38) 5.285 ms 5.332 ms 5.247 ms
4 ar1-a300s3.ormfl.ip.att.net (12.123.32.17) 5.860 ms 5.771 ms 5.810 ms
5 12.127.145.22 (12.127.145.22) 10.398 ms 18.157 ms 14.896 ms
6 rtr-jaxc-fe500.jacksonville.net (24.129.10.6) 10.994 ms 9.715 ms 9.892 ms
7 gsr-jaxb-pos02.jacksonville.net (24.129.10.50) 10.900 ms 11.573 ms 16.782 ms
8 gsr-jaxa-pos10.jacksonville.net (24.129.10.53) 14.843 ms 10.062 ms 11.696 ms
9 gsr-wsa-pos20.jacksonville.net (24.129.10.62) 10.192 ms 10.575 ms 10.219 ms
10 rtr-opb-pos800.jacksonville.net (24.129.10.78) 12.814 ms 10.564 ms 11.531 ms
11 surfop38-52.jacksonville.net (24.129.38.52) 105.898 ms 93.210 ms 223.461 ms


Traceroute Output

FROM zeus.lyceum.com TO 24.129.38.52.

traceroute to 24.129.38.52 (24.129.38.52), 30 hops max, 40 byte packets
1 Ethernet0-0.BR1.ATL1.lyceum.net (205.142.28.4) 5.215 ms 3.008 ms 3.288 ms
2 Serial1-1.BR1.ATL2.lyceum.net (206.71.7.22) 6.754 ms 7.55 ms 6.843 ms
3 631.Hssi4-0-0.GW2.ATL1.ALTER.NET (157.130.72.41) 28.33 ms 630.Hssi5-0-0.GW2.ATL1.ALTER.NET (157.130.72.37) 14.465 ms 631.Hssi4-0-0.GW2.ATL1.ALTER.NET (157.130.72.41) 10.828 ms
4 105.ATM2-0.XR1.ATL1.ALTER.NET (146.188.232.74) 10.823 ms 10.348 ms 10.388 ms
5 195.ATM2-0.TR1.ATL1.ALTER.NET (146.188.232.82) 10.324 ms 10.64 ms 10.377 ms
6 109.ATM6-0.TR1.DCA8.ALTER.NET (146.188.138.138) 24.522 ms 25.005 ms 28.353 ms
7 297.ATM6-0.XR1.DCA8.ALTER.NET (146.188.163.73) 24.535 ms 24.735 ms 28.163 ms
8 189.ATM5-0.BR2.DCA8.ALTER.NET (152.63.35.189) 27.969 ms 234.802 ms 220.207 ms
9 uu-gw.wswdc.ip.att.net (192.205.32.133) 225.345 ms 448.892 ms 462.354 ms
10 gbr4-p50.wswdc.ip.att.net (12.123.9.54) 222.713 ms 458.556 ms 221.209 ms
11 gbr4-p90.attga.ip.att.net (12.122.2.177) 45.886 ms 45.233 ms 77.135 ms
12 gbr3-p60.attga.ip.att.net (12.122.1.141) 45.529 ms 45.546 ms 41.471 ms
13 gbr4-p50.ormfl.ip.att.net (12.122.2.130) 54.414 ms 53.042 ms 51.161 ms
14 gbr1-p50.ormfl.ip.att.net (12.122.5.126) 50.91 ms 52.587 ms 52.336 ms
15 ar1-a3120s3.ormfl.ip.att.net (12.123.32.13) 54.094 ms 51.981 ms 53.225 ms
16 12.127.145.22 (12.127.145.22) 71.031 ms 79.36 ms 284.983 ms
17 rtr-jaxc-fe500.jacksonville.net (24.129.10.6) 77.829 ms * 84.758 ms
18 gsr-jaxb-pos02.jacksonville.net (24.129.10.50) 71.663 ms 93.887 ms 63.773 ms
19 gsr-wsb-pos20.jacksonville.net (24.129.10.66) 70.774 ms 85.388 ms 82.32 ms
20 gsr-wsa-pos10.jacksonville.net (24.129.10.69) 70.146 ms 60.848 ms 88.661 ms
21 rtr-opb-pos800.jacksonville.net (24.129.10.78) 85.298 ms 62.98 ms 77.989 ms
22 surfop38-52.jacksonville.net (24.129.38.52) 148.883 ms 153.294 ms 142.62 ms

 

[old.Pumpkin]

Yer, looks quite congested / oversubscribed to me. Those last hops incoming are very rough for a cable connect.

DSL prolly will be your saviour, but until then, your looking at playing like a modemer.

If anyone knows anything about playing on async connections, let this guy know.

Its a shame id don't have seperated up and down rates, and seperate cl_packetdup settings for up and down.

 

[old.GaMeR]

yeah, well stupid AT&T took over my ISP, so this lag crap just happend lately, and you probably know how at&t treats there costumors, like crap, well, it will probably this fall till DSL, or i could go like BellSouth aDSL or something like that! oh well, and have to wait till lan party time comes