Bad connect and other strange things happening

[Schatzi]

Theres been a lot of strange things going on lately in the MA. I dont know what to think about it, i dont know what to do about it. Feels like im slowly going mad.


Ingame netstat is flatline, ping a steady 141, no PL on startup screen.

Heres some of the "happenings"

- dissappearing planes, no kill, no trace, not reappering anywhere
- planes without icons
- 2 bomber drons (no icon) hanging motionless in the air above a field
- rubber bullets (i know they dont exist, but they do): Im 150 off another plane in my 110, hes not evading, i put almost ALL my ammo into the guy, never seing a single hit sprite. Huh? how the h*** did i miss that much? While im still wondering the guy suddenly falls into a thousand pieces 5 secs AFTER i stopped firing, still no visible hit sprites. No one else in firing range either
-my hit% didnt drop much, but i seem to MISS almost all my shots, my *felt* hit% should be about 1-2% max, cant get more then 1 or 2 kills with Hurr before running out of ammo, where i used to easily have ammo for 4 or 5
- many a plane suddenly start firing when im 150 off their tail (i dont know it, but i think they see me in front of them)
- a planes icon dissappears and suddenly reappears (film here - Edit: If you look from my plane, the B26 looses its icon for a few secs, watched from the B26s view, he never does.... weird)
- i loose sight of enemies in fights a lot more in the last week. i know i know, it might be my SA, but it feels strange.... i *know* i can track an opponent in a 1 vs 1.... and i wouldnt wonder if it happened once... but its about half of my fights.




AH Main just feels downright spooky.

Am i the only one? Any ideas what might be the cause? Anything i can check on my end to find out whats going on?

Please, someone tell me im not crazy (at least not more then I used to....)




PS: Two ping tracers on the MA from this morning:

Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 25.04.2006 11:55:21

 1    1 ms    0 ms    1 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    1 ms    0 ms    1 ms  localhost [192.168.1.1]
 2   20 ms   19 ms -32764 ms   20 ms -32764 ms   20 ms   19 ms   21 ms   20 ms   21 ms   21 ms   19 ms -32764 ms   19 ms   21 ms  dslb-082-083-192-001.pools.arcor-ip.net [82.83.192.1]
 3   21 ms   20 ms   53 ms   21 ms   *       20 ms   19 ms   21 ms   20 ms   19 ms   21 ms   20 ms   52 ms   19 ms   20 ms  han-145-254-11-201.arcor-ip.net [145.254.11.201]
 4   21 ms   23 ms   21 ms   23 ms   22 ms   23 ms   22 ms   21 ms   22 ms   22 ms   23 ms   22 ms   24 ms   22 ms   21 ms  hmb-145-254-18-142.arcor-ip.net [145.254.18.142]
 5   22 ms   24 ms   22 ms   24 ms   23 ms   21 ms   23 ms   22 ms   24 ms   40 ms   22 ms   24 ms   22 ms   23 ms   22 ms  so-2-0-0.ar2.ham1.gblx.net [64.215.181.93]
 6  109 ms  108 ms  110 ms  108 ms  110 ms  119 ms    7 ms  109 ms  108 ms   12 ms  109 ms  110 ms  109 ms  110 ms  109 ms  so7-2-0-2488M.ar1.DCA3.gblx.net [67.17.64.69]
 7  349 ms -32764 ms -32764 ms -32764 ms -32764 ms  351 ms    7 ms -32764 ms -32764 ms -32764 ms -32764 ms -32764 ms  477 ms   *      350 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
 8 -32764 ms   24 ms   21 ms   26 ms    6 ms -32764 ms -32764 ms  352 ms   *       *       *      335 ms   *      303 ms   *      mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
 9   *       *     -32764 ms   35 ms   *       *      131 ms -32764 ms   *       *       *     -32764 ms   36 ms   *       *      att-3.ar1.DCA3.gblx.net [208.50.13.254]
10   21 ms   35 ms   21 ms   *       21 ms   19 ms   *       20 ms   35 ms   *        4 ms   34 ms   *       19 ms   20 ms  att-3.ar1.DCA3.gblx.net [208.50.13.254]
11   55 ms   *       67 ms   39 ms   53 ms   53 ms   *       54 ms   *     -32764 ms   38 ms   *       70 ms   37 ms   55 ms  tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
12   *       23 ms   *       *       *       *       21 ms   *       38 ms   21 ms   *       37 ms   *       *       *      tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
13 -32764 ms -32764 ms   *       *       23 ms   24 ms   24 ms   22 ms    8 ms   23 ms   24 ms   *       *       *       22 ms  tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
14   *       24 ms    6 ms   41 ms -32764 ms -32764 ms -32764 ms   *     -32764 ms   *       *       24 ms   22 ms   23 ms   *      tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
15 -32764 ms -32764 ms -32764 ms -32764 ms   *     -32764 ms -32764 ms -32764 ms   25 ms    8 ms    9 ms    9 ms    7 ms   25 ms    8 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
16    7 ms  256 ms   23 ms   38 ms    8 ms    6 ms    8 ms    7 ms    6 ms    8 ms   22 ms    8 ms    7 ms   37 ms    7 ms  gbr2-p100.dlstx.ip.att.net [12.122.12.82]
17   *       *       *      262 ms   *       *       *       *       *       *      301 ms    3 ms    5 ms  292 ms    4 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
18    5 ms   37 ms   22 ms   22 ms   21 ms    7 ms    6 ms    8 ms   22 ms    5 ms   23 ms    6 ms    8 ms    6 ms    8 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
19  145 ms  146 ms  145 ms  147 ms  146 ms  146 ms  147 ms  147 ms  147 ms  145 ms  147 ms  145 ms  147 ms  146 ms  147 ms  [206.16.60.39]







Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 25.04.2006 12:03:11

 1    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms    0 ms  localhost [192.168.1.1]
 2   21 ms   21 ms   20 ms   21 ms   20 ms   19 ms   20 ms   21 ms   20 ms   20 ms   21 ms   20 ms   19 ms   20 ms   20 ms  dslb-082-083-192-001.pools.arcor-ip.net [82.83.192.1]
 3   19 ms   21 ms   19 ms   21 ms   20 ms   19 ms   20 ms   19 ms   21 ms   20 ms   19 ms   21 ms   19 ms   21 ms   20 ms  han-145-254-11-201.arcor-ip.net [145.254.11.201]
 4   21 ms   23 ms   22 ms   20 ms   23 ms   21 ms   23 ms   22 ms   21 ms   23 ms   22 ms   23 ms   23 ms   21 ms   23 ms  hmb-145-254-18-142.arcor-ip.net [145.254.18.142]
 5   23 ms   21 ms   24 ms   22 ms   22 ms   22 ms   21 ms   23 ms   22 ms   24 ms   23 ms   22 ms   24 ms   22 ms   24 ms  so-2-0-0.ar2.ham1.gblx.net [64.215.181.93]
 6  212 ms  108 ms  110 ms   14 ms  108 ms  110 ms  108 ms  110 ms  109 ms  108 ms  110 ms  109 ms  111 ms  109 ms  109 ms  so7-2-0-2488M.ar1.DCA3.gblx.net [67.17.64.69]
 7   *      351 ms  350 ms  352 ms  351 ms  350 ms  351 ms  350 ms  350 ms  351 ms  350 ms  352 ms  351 ms  350 ms  351 ms  mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
 8  321 ms   *       *       *       *       *       *       *       *       *       *       *       *       *       *      mdf1-bi8k-1-eth-2-1.dal1.attens.net [63.241.192.194]
 9   *       *       *       *       *       *       *       *       *       *       *       *       *       *       *       [-]
10   *       20 ms   21 ms   *       19 ms   20 ms   19 ms   18 ms   20 ms   19 ms   21 ms   20 ms   19 ms   20 ms   19 ms  att-3.ar1.DCA3.gblx.net [208.50.13.254]
11 -32764 ms -32764 ms -32764 ms -32764 ms   53 ms   52 ms   53 ms   52 ms   54 ms   53 ms   52 ms   54 ms   53 ms   54 ms   54 ms  tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
12   *       *       *       23 ms   *       *       *       *       *       *       *       *       *       *       *      tbr1-p011701.wswdc.ip.att.net [12.123.9.114]
13   23 ms   24 ms   24 ms   23 ms   24 ms   22 ms   24 ms   23 ms   23 ms   24 ms   23 ms   24 ms   24 ms   22 ms   25 ms  tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
14   *       *       *       *       *       *       *       *       *       *       *       *       *       *       *      tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
15    6 ms    5 ms    6 ms    5 ms    7 ms    7 ms    7 ms    9 ms    8 ms    9 ms    8 ms    8 ms    9 ms    8 ms    7 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
16    8 ms    7 ms    7 ms    6 ms    6 ms    8 ms    6 ms    8 ms    7 ms    6 ms    8 ms    7 ms    8 ms    8 ms    6 ms  gbr2-p100.dlstx.ip.att.net [12.122.12.82]
17    5 ms    4 ms    6 ms    4 ms    3 ms    3 ms    4 ms    3 ms    4 ms    3 ms    6 ms    4 ms    4 ms    4 ms    4 ms  gar1-p370.dlstx.ip.att.net [12.123.16.237]
18    5 ms    7 ms    6 ms    8 ms    7 ms    9 ms    7 ms    6 ms    7 ms    6 ms    5 ms    8 ms    7 ms    8 ms    7 ms  mdf1-gsr12-2-pos-7-0.dal1.attens.net [12.122.255.170]
19  145 ms  147 ms  144 ms  147 ms  146 ms  144 ms  146 ms  145 ms  144 ms  146 ms  145 ms  147 ms  146 ms  145 ms  147 ms  [206.16.60.39]

[Docc]

No ...you are not crazy.   I too have noticed an extreme amount of lag in the last week.  And it seems intermittant....game is fine for an hour and then awful for an hour then back to good again.

[The Fugitive]

My pings have been good, and pretty steady, but Im getting a lot of packet loss. Been going on for a few weeks, just thought it was the internet having a big hick-up or something

[Ghosth]

Cause & effect. All of the above lag related.

Shooting someone full of lead to no effect, then having him explode 5, 10, 15, or 20 seconds later. Packets are logjammed, not getting through to him. Then all of a sudden they arrive. BANG he's dead in tower going WTF happened?

Your Alive with no ammo going WTF happened!

Fyi last week was rough for me as well. Worst I've seen in a couple of years.

[guttboy]

WOW I'M NOT CRAZY!

I was flying last night and I thought about half of the folks were messing with their modems but ONLY when I was 200-400 off their 6's.....very strange indeed.

[dedalos]

Deleted for flame

[Schatzi]

Originally posted by Ghosth
Cause & effect. All of the above lag related.

Shooting someone full of lead to no effect, then having him explode 5, 10, 15, or 20 seconds later. Packets are logjammed, not getting through to him. Then all of a sudden they arrive. BANG he's dead in tower going WTF happened?

Your Alive with no ammo going WTF happened!

Fyi last week was rough for me as well. Worst I've seen in a couple of years.

Yes, but what i dont understand is that my connect seems to be rock steady as far as variance in delay, ping and packet loss go. But then, when have i ever understood anything about the internet.....



Is there anything one can do to help things? (Besides avoiding the MA...)








PS: Dedalos, you *flamed* my thread?? Im SHOCKED!

[Max]

Schatzi I can tell you that ghi had problems staying connected yesterday. Most of the guys in the FC were losing UDP. Something seems to be "off". By the same token, the entire internet seemed sluggish yesterday.

[Jackal1]

The invisible plane deal I have been seeing a lot of lately.

[hitech]

Schatzi: Your trace route shows the problem with dal1.attens.net.

Issues like this can be very spoty. Some time every thing will be clean then for a few mins, all go hay wire.  I would assume that router is in dallas, and hence other people would be having the same issue.

We will make some calls and see if we can help.


HiTech

[mars01]

Yeah I had some of the same happening last night as well.  I unloaded a wole clip into a YAK with no kill and hit sprites up the wazoo.  

Also it seemed every time I pulled back on the stick in the spit 8 it snap rolled.  I was flying the 8 successfully a lot, until last night, and eventually gave it up because it seemed bugged???  I jumped in a Hog and all was well.

Oh well musta been my lucky night LOL.

[ghi]

Originally posted by Max
Schatzi I can tell you that ghi had problems staying connected yesterday. Most of the guys in the FC were losing UDP. Something seems to be "off". By the same token, the entire internet seemed sluggish yesterday.

 I got disco, 30-40 times, last 3  days,  The internet works ok, i'm on the same computer,now, same comection Bell Toronto, dsl.  Last evening i called Bell's technicians came and checked my modem, cables,  tested :everythink ,ok. I reinstaled the game, same , unstable UDP  

[Larokkit]

hey Shatzi ,
       i saw the same no icon 2 bomber formation yesterday,around 2 in the afternoon. they were higher than i was,i ignored them ,went about wacking for a bit,on my way back to base i saw them at about 1k,i was 5 or 6 ,still no icon.
          i dove on them,2 lancs, picked one and drilled it. it never returned fire and i was instantly kill shot.
       fyi  my ping is always in the 15 -30 range,i have cable (roadrunner) and live in austin, reletively close to dallas.other than getting dropped  now and then its been reliable.
   the wierd bombers are the only thing ive noticed, i'd have to actually shoot near a plane to see hits or no hits.
                 good luck

[Schatzi]

Originally posted by hitech
Schatzi: Your trace route shows the problem with dal1.attens.net.

Issues like this can be very spoty. Some time every thing will be clean then for a few mins, all go hay wire.  I would assume that router is in dallas, and hence other people would be having the same issue.

We will make some calls and see if we can help.


HiTech

Wow, thats great! Thank you very much.


If you need any more ping data or any other info from my part,  ill gladly provide that.

>>S<<

[Schatzi]

Those two drones just appeard over a friendly base, hung in the air motionless and then dissppeared again. Never an icon, no bomber close that they couldve belonged to. They were about 4-5 k AGL.