lag?

[viking73]

I'm almost even afraid to bring this up. This has been real bad the last couple of months. I have been looking at planes 90* from me shooting behind me. I've even watched the tracers go well behind my plane and I think they are missing just to then get damaged or killed. tonight in the MA it was at it's worse. Showed hits on my plane from bullets being fired way behind me. I have a great connection and a high end, fairly new system. I've noticed the same goes for when I'm shooting. I have more trouble anymore hitting anything.




From the Spitfire's view....

[Rob52240]

http://youtu.be/RZ87lXSegjM?hd=1

This is the best lag demonstration I can give.  Notice the 190 landing hits on my spitfire after it turned away.

So his front end registered the hits and then tells the arena server which then tells my front end.  Combine this with the limitations of the speed of light.

[ImADot]

If you had HIS film, you would see it was a legit shot. The US political race is polluting the Interwebz with YouTube vids, billions of web searches, etc., which makes game lag even worse than usual. It should settle down eventually...prolly just in time for all the Holiday online research and shopping...   

[Skuzzy]

Your connection to the Internet is irrelevant, for the most part.  The problem is within Comcast itself and should be easily exhibited in any arena.

The new server location is actually a little better than the old server location.

I have been seeing problems in Comcast for some time, especially during prime time hours.  They really are having issues at te gateways to other ISP's.  This is indicative of too much data trying to go through too small of a connection.  Basically, the connections they have to the Internet are simply way oversold.

They will blame Youtube and Netflix as being the biggest problem and they probably are right, to a degree.  You get enough continuous data streams going and any gateway will eventually get swamped.

Of course, if what I am saying is correct, you should see it in a Ping Plot, during the hours where this problem is so bad.

Here is the IP addresses to use if you want to run a Ping Plot:

66.151.248.2
206.16.60.38

Here is one I ran from the original Late War server.  It did not reach its final destination.

 1  206.16.60.46 (206.16.60.46)  0.297 ms  0.252 ms  0.255 ms
 2  mdf001c7613r0002-gig-10-2.dal1.attens.net (63.241.193.17)  0.503 ms  0.335 ms  0.320 ms
 3  12.122.251.57 (12.122.251.57)  37.537 ms 12.122.251.61 (12.122.251.61)  1.012 ms 12.122.251.57 (12.122.251.57)  1.014 ms
 4  cr1.dlstx.ip.att.net (12.122.85.70)  5.116 ms  2.640 ms cr2.dlstx.ip.att.net (12.122.138.190)  5.957 ms
 5  gar26.dlstx.ip.att.net (12.123.16.85)  1.322 ms gar26.dlstx.ip.att.net (12.123.16.109)  1.463 ms gar26.dlstx.ip.att.net (12.123.16.85)  1.399 ms
 6  be-200-pe01.1950stemmons.tx.ibone.comcast.net (75.149.230.161)  6.903 ms  4.927 ms  12.050 ms
 7  pos-2-1-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.93)  2.866 ms  3.754 ms  3.597 ms
 8  pos-2-11-0-0-cr01.denver.co.ibone.comcast.net (68.86.87.29)  17.877 ms  19.552 ms  15.917 ms
 9  68.86.89.41 (68.86.89.41)  36.159 ms  37.183 ms  35.839 ms
10  pos-0-12-0-0-ar01.area4.il.chicago.comcast.net (68.86.90.54)  42.384 ms  35.080 ms  35.972 ms
11  pos-1-13-0-0-ar01.indianapolis.in.indiana.comcast.net (68.86.187.246)  40.420 ms  40.251 ms  40.090 ms
12  te-3-1-ur01.champaign.il.chicago.comcast.net (68.85.176.2)  45.924 ms  45.831 ms  45.932 ms
13  te-17-10-cdn05.champaign.il.chicago.comcast.net (68.85.131.130)  65.521 ms  59.068 ms  60.745 ms
14  * * *
15  * * *


Here is one I ran to the same location, from the new server.  It did not reach its final destination either.  You wil notice there is one less hop and it is slightly faster than the original location trace.

 1  66.151.248.1 (66.151.248.1)  0.304 ms  0.334 ms  0.256 ms
 2  core1.pc2-bbnet2.ext1a.dal.pnap.net (216.52.191.104)  1.208 ms core1.pc1-bbnet1.ext1a.dal.pnap.net (216.52.191.39)  1.439 ms core1.pc2-bbnet2.ext1a.dal.pnap.net (216.52.191.104)  1.137 ms
 3  144.228.250.125 (144.228.250.125)  1.372 ms  1.211 ms  1.182 ms
 4  sl-st31-dal-0-0-2-0.sprintlink.net (144.232.0.45)  2.881 ms  2.899 ms  1.829 ms
 5  144.232.25.34 (144.232.25.34)  5.000 ms  4.213 ms  12.554 ms
 6  pos-2-4-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.87.217)  4.058 ms  3.052 ms  3.874 ms
 7  pos-2-13-0-0-cr01.denver.co.ibone.comcast.net (68.86.86.209)  17.823 ms  16.777 ms  15.881 ms
 8  68.86.85.245 (68.86.85.245)  35.767 ms  38.283 ms  35.282 ms
 9  pos-0-12-0-0-ar01.area4.il.chicago.comcast.net (68.86.90.54)  37.510 ms  43.786 ms  36.879 ms
10  pos-1-15-0-0-ar01.indianapolis.in.indiana.comcast.net (68.87.230.10)  40.905 ms  41.315 ms  40.508 ms
11  te-3-1-ur01.champaign.il.chicago.comcast.net (68.85.176.2)  49.234 ms  49.136 ms  50.291 ms
12  te-17-10-cdn05.champaign.il.chicago.comcast.net (68.85.131.130)  61.685 ms  50.691 ms  59.620 ms
13  * * *
14  * * *

[bmwgs]

Every time I try to run PingPlotter it tells me the Destination Address is Unreachable.

Fred

[Skuzzy]

Every time I try to run PingPlotter it tells me the Destination Address is Unreachable.

Fred

My bad.  I fat fingered that one.

66.151.248.2

[Wiley]

I'm almost even afraid to bring this up. This has been real bad the last couple of months. I have been looking at planes 90* from me shooting behind me. I've even watched the tracers go well behind my plane and I think they are missing just to then get damaged or killed. tonight in the MA it was at it's worse. Showed hits on my plane from bullets being fired way behind me. I have a great connection and a high end, fairly new system. I've noticed the same goes for when I'm shooting. I have more trouble anymore hitting anything.

Just because nobody's specifically mentioned it, I thought I would.

Both in game in real time, and any time you're looking at video, the other guy's bullets and aircraft position are only an approximation.  They're where your machine put them based on the information from the server, but it's not exactly what he is seeing on his end.  In my experience, the incoming bullets are almost always showing behind you.

This is important because gunnery is calculated on the machine doing the shooting.  In simple terms, he is shooting at his machine's approximation of your location, and based on what damage is done to your plane on his PC, that information gets relayed to the server, and then out to everybody in sight's PC who then see the bullets fire, and the damage occur.

The bottom line is, if everybody's connection is good, avoiding fire is a pretty close approximation, but at all times, it's an approximation.

Wiley.