Author Topic: New main arena location. (Read 1355 times)

Flayed1 · « **Reply #15 on:** March 06, 2006, 06:08:54 PM »

I have to say this location works much better for me. On the old one every night about 8 or 9pm her, about peak time as far as # of players go's my net status was terrible and I would hear every other word on vox. With this location my ping is down, Vox is fantastic and even on really packed MA nights my net status only has minor intermitent spikes compared to the ^^^^^^^^^^^^^^^^^ I always got on the old one.

I would personally love it if you stayed with this new one but if you do go back I guess I'll just deal with it

wojo71 · « **Reply #16 on:** March 06, 2006, 07:02:47 PM »

I have a low end machine and always been on the edge for playing AH2 but lately i've been getting a lot of freezes,miniwarps ,key the vox and it locks up, and disco's gone month's no discos now i get one every night never had a problem before. Low 30 frame rate's but steady and playable ,overall very unsteady lately for me.

Jackal1 · « **Reply #17 on:** March 06, 2006, 07:22:31 PM »

Whoo doggies. Don`t know what happened this afternoon, but I`m shootin blanks. In on spit, see the sprites, but no damage. In on 84, numerous sprites, but no damage. Just did a test in a D-9. Layed back 350 off of a Stang and lit it up wingtip to wingtip, no damage. This ain`t good.

AutoPilot · « **Reply #18 on:** March 06, 2006, 07:30:22 PM »

In the past whenever i logged on it would take 2-3 minutes before everything in the MA was fully loaded.It was usually fully loaded after my name was the last too appear on the range mic list in the start tower.When i say fully loaded i mean it will show 650 people in the MA but it takes 2-3 mins. for all of them too load in.

Now when i log into the MA it is lightning fast to load up.

i think we are all very happy with this move,at least on the bish side of things.

The one thing that darkens MA play is the constant loss of Vox(and not from being muted) while flying and having to re-log to get it back,fix that and you will have made evrybody body happy too no end.

TequilaChaser · « **Reply #19 on:** March 06, 2006, 07:34:20 PM »

sorry hitech, I know I posted it was worse on this server than the old one was....

issues last night was map not updating radar bars, dot dar, and multiple mini warps.......

our squad uses the vox ( enlarged dot) to see where each other are, well at different times it would show any one of use still sitting at the field /over the field when we were 2 or 3 sectors away......

then again, alot of mini warps to be had last night, even after the population died out and the map switched after the reset.....

after reading AutoPilot's post, it is the exact opposite with me, loaded much faster on old server, is snail crawling slow on this server to load up fully when logging in......

Ramon · « **Reply #20 on:** March 06, 2006, 07:42:49 PM »

My playability is about the same, Vox seems to be about the same. The difference I can see on my platform is Ping rate has dropped from about 67-72 to about 47-51. I did notice last night the player dots on the map were mislocated. My squady was flying right along side me and his dot was 3 sectors south and stationary. Also have noticed ghost dots appear. Had an enemy dot pop up right behind me, when I checked 6 nothing was there above me (no clouds) and nothing below even after turning to put the dot in front, but that could be a stealthy pilot. I believe it was another mislocated dot. Nothing I would really call a problem, just issues noticed.

Docc · « **Reply #21 on:** March 06, 2006, 07:46:58 PM »

I'm in Malaysia on DSL........slightly better pings but more slight warps, switching to TCP, loss of VOX. Seems the data stream isn't as steady as the old location.

Widewing · « **Reply #22 on:** March 06, 2006, 08:46:25 PM »

Quote

Originally posted by Jackal1
Whoo doggies. Don`t know what happened this afternoon, but I`m shootin blanks. In on spit, see the sprites, but no damage. In on 84, numerous sprites, but no damage. Just did a test in a D-9. Layed back 350 off of a Stang and lit it up wingtip to wingtip, no damage. This ain`t good.

Same problem my son-in-law Keith had last night....lots of hit sprites, no damage.

My regards,

Widewing

ThunderEGG · « **Reply #23 on:** March 06, 2006, 09:41:09 PM »

Speaking for FlaydONE and myself here in Eastern Oregon, this is the best dial-up connection we've ever had. On the MA's old ISP, we kept getting bad vox skips every night at peak hours, causing a lot of difficulty on squad nights.

Scherf · « **Reply #24 on:** March 07, 2006, 12:40:58 AM »

Let me add some detail to my post in Skuzzy's thread.

*ahem*

The close-in warps are appalling. Any time I get under 400 I have to bide my time for a second or so until the server decides where the other guy actually is.

I'm sure this can be exploited - a judicious chop of the throttle with a con coming up on dead 6 could easily turn the hunter into the hunted.

"Do some of that pilot stuff, Mav."

LePaul · « **Reply #25 on:** March 07, 2006, 12:55:30 AM »

Ok, some numbers from my end...

I'm in Bangor, Maine using Adelphia Cable Internet

206.123.111.42

C:\Documents and Settings\Paul>tracert 206.123.111.42

Tracing route to argon.gamerslobby.net [206.123.111.42]
over a maximum of 30 hops:

1 26 ms 14 ms * 70-33-144-1-gate.agstme.adelphia.net [70.33.144.1]
2 11 ms 13 ms 12 ms 68.168.97.73
3 19 ms 19 ms * 24.54.23.153
4 30 ms 39 ms * 24.48.204.197
5 28 ms 28 ms * unk-426d0e99.adelphiacom.net [66.109.14.153]
6 31 ms 28 ms * p1-00-00-00.a0.cdp00.adelphiacom.net [66.109.1.46]
7 36 ms 35 ms * p3-02-00-00.r0.nyc90.adelphiacom.net [66.109.1.21]
8 70 ms 67 ms 79 ms p3-02-00-00.c1.chi75.adelphiacom.net [66.109.0.101]
9 72 ms 68 ms 69 ms p3-00-00-00.p0.chi91.adelphiacom.net [66.109.3.26]
10 69 ms 67 ms 69 ms ge-4-3-0.r00.chcgil06.us.bb.verio.net [206.223.119.12]
11 95 ms 95 ms * p16-0-1-2.r20.dllstx09.us.bb.verio.net [129.250.2.26]
12 92 ms 94 ms 93 ms xe-0-0-0.r21.dllstx09.us.bb.verio.net [129.250.2.223]
13 134 ms 93 ms 92 ms xe-4-1.r03.dllstx09.us.bb.verio.net [129.250.3.226]
14 82 ms 83 ms 84 ms ge-0.internap.dllstx09.us.bb.verio.net [129.250.12.118]
15 99 ms 198 ms 203 ms border4.ge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.94]
16 88 ms 82 ms 84 ms colo4dallas-3.border4.ext1.dal.pnap.net [216.52.189.10]
17 93 ms 85 ms 83 ms 206.123.64.38
18 86 ms 87 ms 83 ms 206.123.64.98
19 84 ms 82 ms * argon.gamerslobby.net [206.123.111.42]
20 84 ms 82 ms 83 ms argon.gamerslobby.net [206.123.111.42]

Trace complete.

C:\Documents and Settings\Paul>ping 206.123.111.42

Pinging 206.123.111.42 with 32 bytes of data:

Reply from 206.123.111.42: bytes=32 time=84ms TTL=241
Reply from 206.123.111.42: bytes=32 time=84ms TTL=241
Reply from 206.123.111.42: bytes=32 time=82ms TTL=241
Reply from 206.123.111.42: bytes=32 time=85ms TTL=241

Ping statistics for 206.123.111.42:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 85ms, Average = 83ms

C:\Documents and Settings\Paul>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

1 13 ms 13 ms * 70-33-144-1-gate.agstme.adelphia.net [70.33.144.1]
2 11 ms * 10 ms 68.168.97.73
3 28 ms 18 ms 17 ms 24.54.23.153
4 29 ms 28 ms * 24.48.204.197
5 29 ms 30 ms * unk-426d0e99.adelphiacom.net [66.109.14.153]
6 34 ms 27 ms * p1-00-00-00.a0.cdp00.adelphiacom.net [66.109.1.46]
7 34 ms 35 ms * p3-02-00-00.r0.nyc90.adelphiacom.net [66.109.1.21]
8 36 ms 37 ms * g1-00-00-00.p0.nyc90.adelphiacom.net [66.109.1.14]
9 40 ms 39 ms * ge-7-18.car2.NewYork1.Level3.net [65.59.196.33]

10 94 ms 35 ms 36 ms ae-1-53.bbr1.NewYork1.Level3.net [4.68.97.65]
11 43 ms 41 ms * as-3-0.bbr2.Washington1.Level3.net [4.68.128.206]
12 42 ms 44 ms * ae-23-52.car3.Washington1.Level3.net [4.68.121.48]
13 44 ms 42 ms * att-level3-oc192.Washington1.Level3.net [209.244.219.142]
14 75 ms 73 ms 79 ms tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
15 72 ms 74 ms 73 ms tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
16 72 ms 72 ms 75 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
17 72 ms 72 ms 74 ms gbr2-p100.dlstx.ip.att.net [12.122.12.82]
18 72 ms 70 ms 71 ms gar1-p370.dlstx.ip.att.net [12.123.16.237]
19 71 ms 73 ms 70 ms mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
20 72 ms 74 ms 73 ms mdf1-bi8k-1-eth-2-2.dal1.attens.net [63.241.192.226]
21 73 ms 70 ms 72 ms 206.16.60.38

Trace complete.

C:\Documents and Settings\Paul>ping 206.16.60.38

Pinging 206.16.60.38 with 32 bytes of data:

Reply from 206.16.60.38: bytes=32 time=74ms TTL=237
Reply from 206.16.60.38: bytes=32 time=73ms TTL=237
Reply from 206.16.60.38: bytes=32 time=73ms TTL=237
Reply from 206.16.60.38: bytes=32 time=72ms TTL=237

Ping statistics for 206.16.60.38:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 72ms, Maximum = 74ms, Average = 73ms

Lost vox 4 times tonight!

AutoPilot · « **Reply #26 on:** March 07, 2006, 01:28:06 AM »

Quote

The close-in warps are appalling. Any time I get under 400 I have to bide my time for a second or so until the server decides where the other guy actually is.

Now what Hitech posted:

If you previouly had a very bad connection that now is working great please respond to this thread.

If you have already posted that your connection is much worse to the new /current location please do not post to this thread.

Thank You that is all........

Crusher · « **Reply #27 on:** March 07, 2006, 02:19:53 AM »

Generally, the only difference in the servers is that the current one has less large spikes. The current server is very flat. The old server would spike to over 100 ms peak every 15 seconds or so. I imagine that it had to do with routers doing their thing with the silly electrons and not so much with the game.
I have to say, though, that I just installed a new Video card and Joystick/throttle. As I tweak these out, the warping has been improving.
I do not often see the same warps at the same times as others report warps, so I feel that much of the warping has to do with the computer that is "seeing" the warp not so much the connection.
As to vox, I lost vox for the first time since I installed an Audigy 2 ZS 2 months ago. That was a surprise.

Over all, from my side, the difference I've seen is negligible. Some small things are better.

F4J · « **Reply #28 on:** March 07, 2006, 02:36:42 PM »

SanJose1.Level3.net is generally terrible for me. The Denver Global Crossing was bad last night too. I would fire my ISP and get another one if I had any choice.

Target Name: argon.gamerslobby.net
IP: 206.123.111.42
Date/Time: 3/6/2006 7:25:26 PM to 3/6/2006 7:27:41 PM

1 170 ms 123 ms 123 ms 123 ms 123 ms 123 ms 123 ms 123 ms 123 ms 123 ms vancwacobr2.vancwacoro1.centu rytel.net [69.29.185.10]
2 124 ms 124 ms 124 ms 124 ms 124 ms 124 ms 124 ms 124 ms 124 ms 124 ms vancwacoro2.vancwacoro1.centu rytel.net [64.91.105.1]
3 327 ms 327 ms 296 ms 311 ms 327 ms 327 ms 311 ms 311 ms 327 ms 311 ms so-0-0-2.ar2.DEN2.gblx.net [208.48.23.217]
4 343 ms 358 ms 327 ms 343 ms 343 ms 374 ms 327 ms 343 ms 358 ms 327 ms so5-0-0-2488M.ar1.SJC2.gblx.net [67.17.67.154]
5 327 ms 358 ms 327 ms 358 ms 358 ms 374 ms 327 ms * 342 ms 327 ms so-4-0-0.edge1.SanJose1.Level3.net [4.68.127.53]
6 327 ms 374 ms * 343 ms 343 ms 343 ms 390 ms 343 ms 358 ms 327 ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141]
7 358 ms N/A N/A N/A 405 ms 390 ms N/A N/A 405 ms N/A as-1-0.bbr2.Dallas1.Level3.net [64.159.0.245]
8 N/A N/A N/A N/A N/A N/A N/A N/A 218 ms N/A ae-12-55.car2.Dallas1.Level3.net [4.68.122.142]
9 374 ms 421 ms 390 ms 389 ms 405 ms 405 ms 390 ms 390 ms 405 ms 421 ms [4.78.224.74]
10 233 ms 202 ms 202 ms 202 ms 202 ms 202 ms 218 ms 218 ms 202 ms 233 ms [206.123.64.30]
11 436 ms 421 ms 373 ms 390 ms 405 ms 405 ms 373 ms 374 ms 405 ms 373 ms [206.123.64.98]
12 392 ms 393 ms 361 ms 361 ms 377 ms 376 ms 361 ms 361 ms 377 ms 361 ms argon.gamerslobby.net [206.123.111.42]

Ping statistics for argon.gamerslobby.net
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 361ms, Maximum = 393ms, Average = 372ms

F4J · « **Reply #29 on:** March 07, 2006, 02:40:33 PM »

Another sample from last night.

Target Name: argon.gamerslobby.net
IP: 206.123.111.42
Date/Time: 3/6/2006 7:57:26 PM to 3/6/2006 7:59:41 PM

1 155 ms 123 ms 186 ms 123 ms 123 ms 123 ms 139 ms 123 ms 201 ms 123 ms vancwacobr2.vancwacoro1.centu rytel.net [69.29.185.10]
2 155 ms 124 ms 186 ms 124 ms 140 ms 124 ms 140 ms 124 ms 140 ms 124 ms vancwacoro2.vancwacoro1.centu rytel.net [64.91.105.1]
3 343 ms 343 ms 374 ms 374 ms 327 ms 374 ms 389 ms 374 ms 358 ms 327 ms so-0-0-2.ar2.DEN2.gblx.net [208.48.23.217]
4 374 ms 389 ms 374 ms 389 ms 358 ms 405 ms 405 ms 405 ms 374 ms 405 ms so5-0-0-2488M.ar1.SJC2.gblx.net [67.17.67.154]
5 374 ms 389 ms 402 ms 405 ms 372 ms 405 ms 402 ms 405 ms 372 ms 389 ms so-4-0-0.edge1.SanJose1.Level3.net [4.68.127.53]
6 374 ms 390 ms 373 ms 390 ms 358 ms 421 ms * 405 ms 374 ms 358 ms so-1-2-0.bbr2.SanJose1.Level3.net [209.244.3.141]
7 421 ms N/A 421 ms 436 ms N/A N/A N/A N/A 405 ms N/A ae-0-0.bbr1.Dallas1.Level3.net [64.159.1.109]
8 233 ms N/A N/A N/A 233 ms N/A N/A 218 ms 218 ms N/A ae-22-52.car2.Dallas1.Level3.net [4.68.122.46]
9 436 ms 421 ms 405 ms 436 ms 405 ms 452 ms 436 ms 436 ms 421 ms 421 ms [4.78.224.74]
10 233 ms 218 ms 202 ms 202 ms 201 ms 218 ms 202 ms 202 ms 233 ms 201 ms [206.123.64.30]
11 421 ms 421 ms 405 ms 434 ms 421 ms 451 ms 452 ms 451 ms 421 ms 421 ms [206.123.64.98]
12 392 ms 408 ms 392 ms 424 ms 408 ms * 424 ms 424 ms 408 ms 377 ms argon.gamerslobby.net [206.123.111.42]

Ping statistics for argon.gamerslobby.net
Packets: Sent = 10, Received = 9, Lost = 1 (10.0%)
Round Trip Times: Minimum = 377ms, Maximum = 424ms, Average = 406ms