LAG LAG LAG

**...bigdog...** · 07-20-05, 09:29 AM

We're still getting choke, though. I'm into the double digits when the round starts, and especially during large fights. We weren't getting any choke for the last month or so.

AoW said they "made some changes" to the server last night. If you're playing to today, keep an eye on your net_graph 3 and post here your choke levels.

Though we can't expect it to always be 0.....it certainly was 0 even with 20 players on last week and the weeks prior.

**BiGG-D** · 07-21-05, 12:41 AM

dude i have a 400 ping!

C:\Documents and Settings\Owner>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 10 ms 7 ms 10.48.128.1
3 6 ms 21 ms 9 ms pos5-2.hstntxtid-rtr1.houston.rr.com [24.28.97.7
3]
4 8 ms 8 ms 9 ms srp8-0.hstntxtid-rtr3.texas.rr.com [24.93.33.147
]
5 7 ms 15 ms 8 ms son0-0-3.hstqtxl3-rtr1.texas.rr.com [24.93.33.16
1]
6 153 ms 9 ms 142 ms pop1-hou-P0-3.atdn.net [66.185.133.149]
7 8 ms 10 ms 12 ms bb1-hou-P2-0.atdn.net [66.185.150.148]
8 169 ms 150 ms 144 ms bb1-dls-P6-0.atdn.net [66.185.152.132]
9 16 ms 13 ms 26 ms pop1-dls-P0-0.atdn.net [66.185.133.81]
10 * * * Request timed out.
11 20 ms 18 ms 26 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
12 17 ms 19 ms 18 ms 216.39.64.27
13 18 ms 20 ms 17 ms 216.39.69.234
14 21 ms 18 ms 19 ms 10.1.4.2
15 377 ms 371 ms 383 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

C:\Documents and Settings\Owner>

**...bigdog...** · 07-21-05, 08:15 PM

perhaps due to the many issues our cable modem users are having. Their traces are so messed up and irregular, they are causing the server to get out of sync, sort of, with it's clients. Kind of like if half the users are broadband, and the other half are 56k'ers.

I don't know if it's trye, but we might have to deal with it till the comcast/roadrunner net gets it's ass back in gear.

**BiGG-D** · 07-21-05, 08:22 PM

i dont know what hte problem is all i know is sometime my lag gets so bad its unplayable

**geeseven** · 07-21-05, 10:23 PM

BiGG-D, does anyone on your net connection use limewire or bit torrent?

I have heard in some cases with cable that the connections gets really screwy even after you close those bandwidth hogging apps. The connections is screwy till the DHCP gives you a fresh IP.

I also know that today our road runner went down although the digital phone did not, very strange. I think there is something going on with Time Warner, i.e. server updates, hackers, or maybe they need more servers.

**...bigdog...** · 07-22-05, 12:03 AM

I think it's an upgrade/loss of service issue....but it's not just roadrunner, since JAN and Ian both got it earlier in the week on comcast.

**SAMBO** · 08-02-05, 12:12 PM

I've never had a problem with lag on here. That is one of the main reasons i like this server so much.

**...bigdog...** · 08-02-05, 12:50 PM

that's good to here. check out your choke/loss levels in game by typing net_graph 3 in console.

**Ãƒâ€¦Ã‚Â®Ãƒâ€¡TÃƒÅ’Ã‚Â¢_V** · 08-02-05, 02:40 PM

The choke I usually get I'm thinking stems @ round start..
I've gotten some during firefighte but not much..
Here is my tracrt:

Code:

Tracing route to 88.157.36.72.reverse.layeredtech.com &#91;72.36.157.88&#93;
over a maximum of 30 hops&#58;

  1     8 ms     8 ms     9 ms  10.248.144.1
  2     8 ms     9 ms    10 ms  68.1.200.245
  3    20 ms    21 ms    37 ms  dllsdsrc02-pos0701.rd.dl.cox.net &#91;68.1.206.21&#93;
  4    20 ms    19 ms    19 ms  so-3-3-0-0.gar2.Dallas1.Level3.net &#91;4.78.234.5&#93;

  5    21 ms    19 ms    23 ms  ae-1-54.bbr2.Dallas1.Level3.net &#91;4.68.122.97&#93;
  6    54 ms    51 ms    59 ms  ae-0-0.bbr1.LosAngeles1.Level3.net &#91;64.159.1.125
&#93;
  7    51 ms    51 ms    51 ms  ge-5-0-0-52.gar2.LosAngeles1.Level3.net &#91;4.68.10
2.49&#93;
  8    51 ms    51 ms    51 ms  4.68.127.190
  9    52 ms    53 ms    52 ms  bcs2-so-6-0-0.Dallas.savvis.net &#91;204.70.192.50&#93;

 10    53 ms    53 ms    53 ms  ohr1-pos-1-0.FortWorthda1.savvis.net &#91;208.172.12
9.230&#93;
 11    54 ms    53 ms    54 ms  216.39.64.2
 12    54 ms    55 ms    55 ms  216.39.69.134
 13     *        *        *     Request timed out.
 14    54 ms    53 ms    53 ms  88.157.36.72.reverse.layeredtech.com &#91;72.36.157.
88&#93;

edit: btw i'm on Cox Cable

**...bigdog...** · 08-02-05, 03:06 PM

50 ms aint perfect...in fact, it's a littlw slow.

why in the hell you're starting in dallas, then going to LA, and then back to dallas is also a little odd. I'll send this into them.