Game unplayable

[HawkerMKII]

The MA is getting really bad with LAG, to the point it is unplayable and its just not me. That LOST UDP crap has to be from HT and not the players computers or phone lines, to many people are having the same problem. Thinks its time to FIX something!!!!!!!!!

[Turbot]

Lag was very bad at times.   I was in a bomber formation and a LA7 and 190 were attacking me, I was wondering why they were such awful shots.  A couple of minutes later (with the enmy quite some distance away)  ping ping ping - NOW the damage is registering.

All this while my ping was the usual 70 or 80 ms.  We got us some sever lag boys, but I'm sure HTC is on the case.

[TheFatz]

Lag =

[easymo]

14 packets go bye bye.




Target Name:
         IP: 216.234.247.240

 1   37 ms    9 ms    9 ms   32 ms    8 ms    9 ms    7 ms    8 ms   10 ms   11 ms  [10.51.128.1]
 2   38 ms   46 ms    9 ms    8 ms    9 ms   11 ms   37 ms    8 ms   29 ms   59 ms  pos5-0.hstntxlut-rtr1.houston.rr.com [24.28.97.206]
 3   10 ms   10 ms   10 ms   12 ms   10 ms    9 ms   11 ms   10 ms   70 ms   33 ms  srp2-0.hstntxeas-rtr1.houston.rr.com [24.28.96.1]
 4   13 ms   13 ms   10 ms   11 ms   13 ms    9 ms   10 ms   10 ms   13 ms    9 ms  pos6-2.hstntxtid-rtr1.houston.rr.com [24.28.97.25]
 5   12 ms   31 ms   11 ms   10 ms   10 ms   11 ms   12 ms   10 ms   10 ms   11 ms  srp8-0.hstntxtid-rtr3.texas.rr.com [24.93.33.147]
 6   20 ms   50 ms   13 ms   10 ms   11 ms   46 ms   11 ms   13 ms   12 ms   11 ms  pop1-hou-P7-2.atdn.net [66.185.136.77]
 7   11 ms    9 ms   20 ms   12 ms   11 ms    9 ms   12 ms   10 ms   11 ms    9 ms  bb2-hou-P0-1.atdn.net [66.185.146.101]
 8   99 ms   67 ms   51 ms   43 ms   42 ms   80 ms   76 ms   44 ms   44 ms   43 ms  bb2-pho-P7-0.atdn.net [66.185.152.214]
 9   43 ms   44 ms   44 ms   42 ms   41 ms   48 ms   73 ms   41 ms   44 ms   64 ms  bb1-pho-P1-0.atdn.net [66.185.152.73]
10   53 ms   50 ms   53 ms   90 ms   73 ms   50 ms   56 ms   51 ms   51 ms   52 ms  bb1-las-P7-0.atdn.net [66.185.152.53]
11   52 ms   55 ms   62 ms   84 ms   51 ms   51 ms   51 ms   51 ms   55 ms   50 ms  pop2-las-P0-0.atdn.net [66.185.137.162]
12   51 ms   52 ms   55 ms   50 ms   52 ms   51 ms   50 ms   51 ms   66 ms  102 ms  aol-gw.la2ca.ip.att.net [192.205.32.101]
13   68 ms   85 ms   64 ms   61 ms   54 ms   59 ms   65 ms   63 ms   94 ms   56 ms  tbr1-p012801.la2ca.ip.att.net [12.122.11.225]
14   *       *       *       *       *       *       *       *       *       *       []
15   69 ms   71 ms   72 ms   70 ms  111 ms   70 ms   70 ms   70 ms   70 ms   71 ms  gbr1-p10.dlstx.ip.att.net [12.122.12.58]
16   68 ms   69 ms  112 ms   71 ms   68 ms   92 ms   70 ms   74 ms   69 ms  106 ms  gar1-p360.dlstx.ip.att.net [12.123.16.233]
17   70 ms  105 ms   70 ms   69 ms   70 ms   90 ms   72 ms   85 ms   72 ms   70 ms  gar1-p340.dlrtx.ip.att.net [12.123.196.97]
18   49 ms   58 ms   92 ms   49 ms   49 ms   47 ms   48 ms   49 ms   48 ms   71 ms  [12.119.136.22]
19   48 ms   47 ms   47 ms   68 ms   47 ms   48 ms   61 ms   49 ms   51 ms   49 ms  border3.ge3-1-bbnet1.ext1.dal.pnap.net [216.52.191.22]
20   68 ms   47 ms   49 ms   86 ms   87 ms   47 ms   81 ms   63 ms   47 ms   50 ms  theplanet-2.border3.003.dal.pnap.net [216.52.189.222]
21   48 ms   47 ms   49 ms   53 ms   47 ms   49 ms   47 ms   79 ms   83 ms   47 ms  [216.234.247.240]

[Roscoroo]

Hawker  please get a ping plotter and check your connection when this happens to help htc with this and yourself .

Ive played over 108 hours this month with only 1 disco , and 3 ucp tcp disco's and everytime i got one of these it was in my route to htc .  thanks

[goaly]

I had four lost UDP boots in 15 minutes tonight... That's enough

[beet1e]

I have been playing AH since November, and you've never seen me whine about lag. (I used to do that all the time *over there*)

Anyway, I'm not going to start now because I know that the matter is in the very capable hands of Hitech/HTC.

But I too have noticed some very strange occurrences.

• Damage occurring in exactly the manner described by Mr. Turbot above.
• Shooting a con at 300 yards, and being blown up myself! Lag collision perhaps, but this happened to two of my squad mates last night.

These problems typlically occur with crowded arenas, and I saw more than 300 online last night at around midnight my time.

Last night for me was the worst in terms of server lag that I have ever seen.

[Innominate]

Originally posted by beet1e
Shooting a con at 300 yards, and being blown up myself! Lag collision perhaps, but this happened to two of my squad mates last night.

I actually did this to a squadmate once.  We were both chasing down a 109 trying to steal each others kill.  I edged out ahead of him, and my wing went inside his while he was shooting.  He never saw my wing get just slightly in front of his guns before he exploded.  It might be nice if killshooter were disabled against friendlies which were within 10-30 yards of you.

[moose]

I think today (Sept 3) is the day they move the servers

From what I remember it's supposed to be like.. better then

[beet1e]

Insomniate - No, this was nothing to do with killshooter. What happened to my squaddies did so in separate incidents. When I shot up a 190, I blew up myself - no other cons or friendlies in sight.

[Revvin]

Got to say for the first time last night I was faced with lag that caused me to log off in sheer frustration. I lit up an F4F's wing like a christmas tree and he flew on like I had just tickled him and then I had a P51 go from D1.3 about me to 300 off my six with no transitional movement in between these two distances, he did this twice. I watched several cons and friendlies warp in an out and other's change aspect radically flopping in the sky like fish. I hope this can be sorted out soon.

[beet1e]

LOL Revvin!  The air around you was turning quite blue.

[Vulcan]

Well Hawker I play all the way from NZ without any real problems. The first release of 1.10 was a bit dodget, but I've had no real issues since the patches. Now the next furtherest hop away from HTC is the International Space Station.

That LOST UPD crap indicates you have a crap internet connection and in the past you've simply got away with it or ignored the cries of 'warper' thrown at you.

To many people ARE NOT having the same problem. When you consider that there are roughly 3000-4000 subscribers (guessing by the ranking system) its a vocal few who are having issues. Those issues are mixed between UDP configuration problems with firewalls or routers, and low quality ISPs.

If you want to fix something I'd suggest first you get a half decent internet connection, shortly followed with someone who knows a bit about networking to make sure you have an optimal setup. You'd be suprised at what a savvy networking person can do for you.

Originally posted by HawkerMKII
The MA is getting really bad with LAG, to the point it is unplayable and its just not me. That LOST UDP crap has to be from HT and not the players computers or phone lines, to many people are having the same problem. Thinks its time to FIX something!!!!!!!!!

[akak]

Originally posted by HawkerMKII
The MA is getting really bad with LAG, to the point it is unplayable and its just not me. That LOST UDP crap has to be from HT and not the players computers or phone lines, to many people are having the same problem. Thinks its time to FIX something!!!!!!!!!

Before you go off half-cocked again, download Pingplotter.  Next time you get that Lost UDP error message and get discoed, run Pingplotter and do a tracert to the AH servers, ( IP: 216.234.247.240 ).  This will pretty much tell whether or not the problem is on your end or HTC's.  If the problem turns out to be on HTC's end, then email   HiTech support or post the tracert in the Internet Connectivity message board.


Ack-Ack

[hazed-]

Vulcan thats nonsense mate. Ive been playing AH for over 2 years with no problems up until the latest patches.I have adsl and a very good connection but im still getting lost udp's and CTDs regularly.

also for me last night was so laggy that i switched to CT.

all the symptoms mentioned above went away in CT and as you know the ping times to CT are higher than the MA.It has nothing to do with poor connections per say, its the routers that seem to be at fault and MA routers last night SUCKED EGGS!