Alberta Canada - Double Animations/Delayed Shots in Game

VeiledFlame-1983 · January 22, 2019, 5:53am

Hello everyone I’ve been having issues for a very very long time with this game and all blizzard games for that matter. I’ve been trying to isolate the source but I get varying answers from my ISP and from blizzard both blaming each other for issues. I was hoping someone could clear it up for me.

I’m in Alberta Canada, using Shaw as my ISP. No matter what I do my shots feel very delayed and double-animations occur every 2-3 shots (particularly visible when playing Genji).

I ran two tests today, one without a VPN and one with:

TEST ON SHAW ROUTING (NO VPN):

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| DD-WRT - 0 | 206 | 206 | 0 | 0 | 1 | 0 |
| 96.52.128.1 - 0 | 206 | 206 | 7 | 10 | 15 | 9 |
| rh9we-cmts.ed.shawcable.net - 0 | 206 | 206 | 7 | 12 | 72 | 8 |
| 66.163.70.129 - 0 | 206 | 206 | 8 | 14 | 89 | 12 |
| rc3no-be6.cg.shawcable.net - 0 | 206 | 206 | 12 | 15 | 38 | 17 |
| rc2wt-be100.wa.shawcable.net - 0 | 206 | 206 | 26 | 29 | 34 | 27 |
| rc6wt-tge0-10-0-11.wa.shawcable.net - 0 | 206 | 206 | 27 | 31 | 64 | 30 |
| ae1-br01-eqse2.as57976.net - 0 | 205 | 205 | 52 | 71 | 1473 | 53 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 205 | 205 | 51 | 73 | 1334 | 53 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 2 | 183 | 180 | 51 | 166 | 4618 | 53 |
| be2-pe02-eqla1.as57976.net - 0 | 206 | 206 | 52 | 55 | 61 | 53 |
| lax-eqla1-ia-bons-03.as57976.net - 0 | 206 | 206 | 52 | 56 | 61 | 55 |
| 24.105.30.129 - 0 | 206 | 206 | 53 | 56 | 61 | 54 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting &amp; Cloud Provider

TEST USING A VPN TO CHICAGO (BYPASSING SHAW ROUTING):

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 172.21.36.1 - 0 | 134 | 134 | 38 | 40 | 45 | 38 |
| 151.139.44.25 - 0 | 134 | 134 | 37 | 40 | 47 | 38 |
| 151.139.44.9 - 0 | 134 | 134 | 38 | 41 | 45 | 42 |
| eqix-ix-ch1.blizzard.com - 0 | 134 | 134 | 38 | 42 | 66 | 42 |
| ae1-br01-eqch2.as57976.net - 0 | 134 | 134 | 38 | 46 | 144 | 43 |
| be1-pe01-eqch2.as57976.net - 0 | 134 | 134 | 38 | 42 | 48 | 41 |
| chi-eqch2-ia-bons-02.as57976.net - 0 | 134 | 134 | 39 | 41 | 49 | 41 |
| 24.105.62.129 - 0 | 134 | 134 | 39 | 43 | 52 | 43 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting &amp; Cloud Provider

The test without the VPN felt awful with double animations every second shot using Genji in the training grounds. The test with the VPN (to Chicago) had significant improvements and maybe every 15 shots I’d get a double animation along with much less shot delay. I posted these results on my ISPs forums and someone claimed both tests were ‘fine’ but I’m a little skeptical of that since in-game they felt drastically different.

I would appreciate any insight on this matter, I’m out of ideas as to what is causing this.

Nicole-1893 · January 22, 2019, 1:14pm

I have to agree with the response you got there, they do both look very similar. There is a tiny latency spike on your ISP line here:
rh9we-cmts.ed.shawcable.net - 0 | 206 | 206 | 7 | 12 | 72 | 8 |
… but otherwise looking good. Is it possible you’re also experiencing some hardware bottleneck, or have something running in the background causing you to drop frames?

VeiledFlame-1983 · January 22, 2019, 1:56pm

As much as I’d like to think its just a hardware issue I’ve built 3 separate computers and they all have the double animations. I’ve tried literally everything I possibly could on my end:

Done probably 50+ fresh installs of windows (this year alone)
Replaced multiple parts in each computer
Ran selective startup
Disabled many windows services in the background

From what I can tell these double animations seem to coincide with the in-game netgraph. Also if dropping frames was the reason wouldn’t my whole game stutter? I’m not new to stuttering issues as windows 10 is full of them if you don’t tweak it. The game runs extremely smooth other than actions I take with my characters. Anything involving ability use or taking shots is delayed significantly and the double animations occur frequently but at random. However if you believe its hardware related I’d be happy to provide DXDiags of two of my computers if that helps at all.

I’ve actually even tried Telus as an ISP and it had identical symptoms (though their service is much more stable ; DSL connection). If I have to, to figure this out I’d be happy to sign up again with Telus to see if that changes anything.

I can record a video on my Twitch for you if you’d like today showing the double animations. I’m not sure if that would help isolate the issue but I’m willing to try anything at this point as I’d like to play Overwatch again someday.

I appreciate the fast response by the way!

Nicole-1893 · January 22, 2019, 2:22pm

That might be helpful in diagnosing it, especially for the staff.

VeiledFlame-1983 · January 22, 2019, 2:59pm

Hey Nicole I recorded a very quick video for you to take a look at:

https://www.twitch.tv/videos/368002566

0:40 is the first double animation
0:50 is the second/third example of a double animation
3:30 is another example

Picture this happening every 3 shots, it didn’t happen consistently this morning but that’s an example of the issue I’m talking about. My only thought as I mention in the video is its possible its a node issue, but my testing seems to always come out perfectly fine in MTRs. Strange part is this happens with my other ISP on a DSL connection as well (when I had their service). I’ll try recording another later today when I’m back from work and hopefully its more frequent then.

Zhyxen · January 22, 2019, 3:27pm

What’s the model of your modem? Rather than testing with a VPN, do you have a phone with a data plan that supports tethering that you can test with so we can bypass your usual network hardware?

VeiledFlame-1983 · January 22, 2019, 4:14pm

Hey Zhyxen my modem is a Technicolor XB6 (Broadcom chipset) modem. I spent a long time swapping modems to avoid the Puma 6/7 modems that shaw normally provides. So far the modem itself hasn’t given me any problems that I know of, and its very low latency (in comparison to my old modems).

Absolutely I’ll tether my phone this evening and give that a test as well. I’ll probably record the result on my stream as well to be thorough if there’s a noticeable difference.

Let me know if there’s any other information you need in the meantime.

Update: Tried tethering my phone and the double animations went away, other than the fact that the LTE network was generally unstable but that’s to be expected. I’m assuming the issue is relating to my node in my area as I got this test while I was writing a message to my ISP on their forums:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                             192.168.1.1 -    0 |   94 |   94 |    0 |    0 |    2 |    0 |
|                             96.52.128.1 -    3 |   87 |   85 |    7 |   11 |   85 |    7 |
|                           64.59.186.165 -    0 |   94 |   94 |    8 |   12 |   59 |    8 |
|              rc3no-be6.cg.shawcable.net -    0 |   94 |   94 |   12 |   19 |   60 |   17 |
|            rc2wt-be100.wa.shawcable.net -    2 |   91 |   90 |   28 |   33 |   38 |   34 |
|                            72.14.242.90 -    2 |   91 |   90 |   27 |   32 |   37 |   34 |
|                   No response from host -  100 |   20 |    0 |    0 |    0 |    0 |    0 |
|                           74.125.253.60 -    2 |   91 |   90 |   29 |   34 |   38 |   35 |
|                         108.170.245.107 -    2 |   91 |   90 |   27 |   34 |   74 |   33 |
|                           216.239.50.39 -    0 |   94 |   94 |   27 |   34 |   80 |   32 |
|                          108.170.226.97 -    2 |   91 |   90 |   28 |   33 |   38 |   35 |
|                          74.125.243.193 -    2 |   91 |   90 |   27 |   32 |   37 |   28 |
|                          209.85.254.237 -    2 |   91 |   90 |   28 |   40 |  609 |   35 |
|                sea30s01-in-f3.1e100.net -    2 |   91 |   90 |   27 |   33 |   37 |   34 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

So to be honest I really don’t know how to motivate them to look into it but hopefully that’s the only issue.

Nicole-1893 · January 23, 2019, 10:06am

Persistence is the only advice I can personally offer here.

VeiledFlame-1983 · January 23, 2019, 2:11pm

That or I’ll just see if a different ISP will do the trick! Appreciate the help anyways everyone, looks like I’ll be dealing with my ISP for the next while.

VeiledFlame-1983 · January 28, 2019, 6:19pm

Alright so a quick update:

Had a tech fix any issues with the node in my area and the Overwatch issue hasn’t been resolved even after that was done. All other games I’ve tested are perfectly fine, no packet loss no random issues and my stream connection is perfect as well.

I was contacted by another person in Calgary, Alberta using Shaw that plays Overwatch and confirmed he had identical issues with double animations. Asked my friend that uses another ISP (Telus DSL) and he has the issue as well. So it does seem this issue is affecting people in Alberta and not just on my ISP. Worth noting I seem to have the most issues when my connection shows I’m connected to LAX servers in the net graph. If I’m on ORD1 my ping is 20-30ms lower and the double animations are much more infrequent (but I have to use a VPN for that which causes its own instability on occasion).

Is there any reason at all LAX servers for me would be unstable and cause these double animations? Also is there anything I can do or someone I can talk to about this, or am I basically just not going to be able to play Overwatch for the foreseeable future?

Drakuloth · January 28, 2019, 7:59pm

Veiledflame,

I checked out your video and I can’t see any reason for that behavior in that video, though sadly it looks like your netgraph may not have been up while catching the behavior. Is there any way you can try to get a clip of it happening with the netgraph running?

Apart from that - is this a home network you’re playing on or some kind of corporate/business/school network? Do you have a separate modem/router or just a modem/router combo?

VeiledFlame-1983 · January 28, 2019, 8:48pm

I agree it shouldn’t be doing that with the MTRs and lack of packet loss indicators in game which is what makes this difficult to figure out. I’ll definitely record again with the net graph open and submit it (I had tried to do that before but my video was too pixelated to submit). Only thing I noticed in my net graph is my ping value varies a fair amount, and if packet loss occurs its very rare and doesn’t seem to coincide with the double animation.

This is a home network, I’ve tried:

-Direct connection to ISP modem Technicolor XB6 (current modem)
-Swapped ISP modems about 6 times or so
-Used my own personal routers bridged, one has DD-WRT with FQ_Codel QoS and the other is a Netgear XR500 with Netduma. Tried both routers and they had the same problem and the MTRs come out clean from what I understand.
-Tested with Telus as well with the same result and if I remember correctly it was using a Actiontec T3200M
-Tested a connection at a local gaming cafe and had these symptoms
-My friend with Telus has the same problem

The thing that throws me off about this issue is multiple people from Alberta have reported this issue to me some with Shaw and others with Telus DSL (wish some of them had fibre for testing purposes). And I know that the Overwatch team I played on had this issue for years when I was playing with them. I had asked them if they had similar issues as my connection 2 years ago when I was trying to get involved in the competitive scene.

But yeah later today I’ll get a video out to you to take a look at with the net graph.

Drakuloth · January 28, 2019, 8:53pm

Perfect, thanks! While we’re at it if you can throw us a looking glass as well, that could help narrow things down. Maybe the issue is on the back swing to your house instead of out to our servers.

VeiledFlame-1983 · January 29, 2019, 5:37am

Video showing the issue again with netgraph open:

https://www.twitch.tv/videos/371643201

Here’s three looking glass tests (to be thorough):

#1

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=59.5 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=58.5 ms
64 bytes from 70.74.86.188: icmp_seq=3 ttl=49 time=57.0 ms
64 bytes from 70.74.86.188: icmp_seq=4 ttl=49 time=58.1 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 57.073/58.332/59.563/0.889 ms


29/01/2019 05:20:36 UTC
--------------------

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=61.1 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=58.7 ms
64 bytes from 70.74.86.188: icmp_seq=3 ttl=49 time=62.6 ms
64 bytes from 70.74.86.188: icmp_seq=4 ttl=49 time=57.0 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 57.036/59.883/62.630/2.155 ms


29/01/2019 05:20:36 UTC
--------------------

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.298 ms  0.298 ms  0.303 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


29/01/2019 05:20:36 UTC
--------------------

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.250 ms  0.269 ms  0.281 ms
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *


29/01/2019 05:20:36 UTC
--------------------

MTR:
Start: Tue Jan 29 05:20:36 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.3   0.3   0.2   0.3   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


29/01/2019 05:20:36 UTC
--------------------

MTR:
Start: Tue Jan 29 05:20:36 2019 Blizzard  1.|-- Blizzard    0.0%    10    0.2   0.3   0.2   0.4   0.0
  2.|-- ???             100.0    10    0.0   0.0   0.0   0.0   0.0


29/01/2019 05:20:36 UTC
--------------------

#2

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.973 ms  0.970 ms  0.977 ms Blizzard(24.105.18.2)  1.824 ms  1.866 ms  1.900 ms
 3  137.221.105.10 (137.221.105.10)  1.765 ms  1.821 ms  1.886 ms
 4  137.221.66.16 (137.221.66.16)  1.797 ms  1.835 ms  1.844 ms
 5  137.221.83.66 (137.221.83.66)  13.226 ms  15.533 ms  15.605 ms
 6  137.221.65.68 (137.221.65.68)  42.489 ms  39.342 ms  39.313 ms
 7  137.221.65.1 (137.221.65.1)  12.856 ms  12.885 ms  12.977 ms
 8  137.221.65.7 (137.221.65.7)  12.992 ms  13.001 ms  13.145 ms
 9  137.221.70.32 (137.221.70.32)  12.744 ms  12.777 ms  12.832 ms
10  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  13.295 ms  16.427 ms  14.588 ms
11  rc1wt-be60.wa.shawcable.net (66.163.75.89)  30.746 ms  30.691 ms  31.240 ms
12  rc2wt-be18-1.wa.shawcable.net (66.163.64.82)  31.076 ms  31.115 ms  31.042 ms
13  rc3no-be100.cg.shawcable.net (66.163.75.234)  45.849 ms  45.956 ms  45.996 ms
14  rc1we-be6.ed.shawcable.net (66.163.64.70)  49.786 ms  49.984 ms  49.810 ms
15  dx6lo-lag1.ed.shawcable.net (64.59.186.166)  50.074 ms  50.255 ms  50.373 ms


29/01/2019 05:23:08 UTC
--------------------

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  1.158 ms  1.153 ms  1.157 ms Blizzard(24.105.18.2)  2.756 ms  2.821 ms  2.830 ms
 3  137.221.105.10 (137.221.105.10)  1.040 ms  1.048 ms  2.733 ms
 4  137.221.66.16 (137.221.66.16)  0.974 ms  2.737 ms  2.746 ms
 5  137.221.83.66 (137.221.83.66)  13.273 ms  13.315 ms  13.330 ms
 6  137.221.65.68 (137.221.65.68)  47.463 ms  45.602 ms  45.596 ms
 7  137.221.65.1 (137.221.65.1)  12.745 ms  13.007 ms  13.004 ms
 8  137.221.65.7 (137.221.65.7)  12.764 ms  14.645 ms  14.608 ms
 9  137.221.70.32 (137.221.70.32)  20.067 ms  20.073 ms  20.074 ms
10  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  16.243 ms  14.530 ms  14.551 ms
11  rc1wt-be60.wa.shawcable.net (66.163.75.89)  37.854 ms  37.228 ms  34.745 ms
12  rc2wt-be18-1.wa.shawcable.net (66.163.64.82)  31.052 ms  31.043 ms  32.226 ms
13  rc3no-be100.cg.shawcable.net (66.163.75.234)  50.151 ms  46.424 ms  46.430 ms
14  rc1we-be6.ed.shawcable.net (66.163.64.70)  50.664 ms  50.812 ms  50.204 ms
15  dx6lo-lag1.ed.shawcable.net (64.59.186.166)  50.217 ms  50.263 ms  50.408 ms


29/01/2019 05:23:08 UTC
--------------------

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=57.2 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=57.1 ms
64 bytes from 70.74.86.188: icmp_seq=3 ttl=49 time=57.9 ms
64 bytes from 70.74.86.188: icmp_seq=4 ttl=49 time=57.3 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 57.122/57.413/57.956/0.364 ms


29/01/2019 05:23:08 UTC
--------------------

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=57.2 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=56.8 ms
64 bytes from 70.74.86.188: icmp_seq=3 ttl=49 time=57.3 ms
64 bytes from 70.74.86.188: icmp_seq=4 ttl=49 time=57.2 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 56.890/57.196/57.355/0.344 ms


29/01/2019 05:23:08 UTC
--------------------

MTR:
Start: Tue Jan 29 05:23:08 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.2   0.3   0.2   0.9   0.0 Blizzard 0.0%    10    0.7   3.0   0.5  23.8   7.3
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.6   0.4   0.9   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.7   0.6   0.5   0.7   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.8  14.9  12.7  33.0   6.3
  6.|-- 137.221.65.68                        0.0%    10   12.8  15.5  12.6  40.0   8.6
  7.|-- 137.221.65.1                         0.0%    10   13.6  18.3  12.8  51.3  12.3
  8.|-- 137.221.65.7                         0.0%    10   12.8  13.0  12.7  13.7   0.0
  9.|-- 137.221.70.32                        0.0%    10   13.1  14.2  12.6  27.4   4.6
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   12.9  14.5  12.9  16.4   1.1
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   31.7  31.7  30.9  32.9   0.5
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   32.2  31.2  30.8  32.5   0.5
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.3  46.3  45.9  46.9   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.9  49.9  49.7  50.1   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.3  50.3  50.2  50.7   0.0
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net   0.0%    10   57.8  60.1  57.1  63.4   2.6


29/01/2019 05:23:08 UTC
--------------------

MTR:
Start: Tue Jan 29 05:23:09 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard 0.0%    10    0.6   1.2   0.5   5.3   1.4
  3.|-- 137.221.105.10                       0.0%    10    0.5   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.6   0.9   0.5   3.3   0.7
  5.|-- 137.221.83.66                        0.0%    10   13.8  12.9  12.7  13.8   0.0
  6.|-- 137.221.65.68                        0.0%    10   12.8  19.0  12.7  53.5  13.6
  7.|-- 137.221.65.1                         0.0%    10   82.8  20.6  12.7  82.8  21.9
  8.|-- 137.221.65.7                         0.0%    10   12.9  13.0  12.7  14.0   0.0
  9.|-- 137.221.70.32                        0.0%    10   13.2  12.8  12.5  13.4   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   15.4  14.9  13.2  16.5   0.9
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   32.0  31.6  30.8  34.9   1.2
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   30.9  31.2  30.9  32.2   0.0
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.0  46.2  45.8  48.0   0.5
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   50.1  49.9  49.6  50.2   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.2  50.3  50.2  50.5   0.0
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net   0.0%    10   57.3  57.4  56.4  58.9   0.6


29/01/2019 05:23:08 UTC
--------------------

#3

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  0.322 ms  0.321 ms  0.322 ms Blizzard(24.105.18.2)  0.918 ms  0.939 ms  0.977 ms
 3  137.221.105.10 (137.221.105.10)  0.980 ms  0.984 ms  1.119 ms
 4  137.221.66.16 (137.221.66.16)  0.923 ms  0.925 ms  0.927 ms
 5  137.221.83.66 (137.221.83.66)  12.934 ms  12.950 ms  12.955 ms
 6  137.221.65.68 (137.221.65.68)  12.786 ms  12.950 ms  12.882 ms
 7  137.221.65.1 (137.221.65.1)  12.822 ms  13.159 ms  13.158 ms
 8  137.221.65.7 (137.221.65.7)  13.306 ms  13.315 ms  13.313 ms
 9  137.221.70.32 (137.221.70.32)  12.981 ms  12.652 ms  12.671 ms
10  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  14.335 ms  13.747 ms  13.133 ms
11  rc1wt-be60.wa.shawcable.net (66.163.75.89)  37.904 ms  37.426 ms  36.304 ms
12  rc2wt-be18-1.wa.shawcable.net (66.163.64.82)  36.167 ms  35.641 ms  35.568 ms
13  rc3no-be100.cg.shawcable.net (66.163.75.234)  47.642 ms  47.683 ms  47.176 ms
14  rc1we-be6.ed.shawcable.net (66.163.64.70)  49.830 ms  49.824 ms  49.816 ms
15  dx6lo-lag1.ed.shawcable.net (64.59.186.166)  50.283 ms  50.297 ms  50.752 ms


29/01/2019 05:24:49 UTC
--------------------

TRACEROUTE:
traceroute to 70.74.86.188 (70.74.86.188), 15 hops max, 60 byte packets
 1  Blizzard Blizzard  2.694 ms  2.688 ms  2.692 ms Blizzard(24.105.18.2)  2.534 ms  2.559 ms  2.596 ms
 3  137.221.105.10 (137.221.105.10)  2.521 ms  2.587 ms  2.593 ms
 4  137.221.66.16 (137.221.66.16)  2.515 ms  2.501 ms  2.524 ms
 5  137.221.83.66 (137.221.83.66)  13.518 ms  13.540 ms  13.549 ms
 6  137.221.65.68 (137.221.65.68)  13.555 ms  14.027 ms  14.011 ms
 7  137.221.65.1 (137.221.65.1)  13.924 ms  13.940 ms  13.946 ms
 8  137.221.65.7 (137.221.65.7)  13.950 ms  13.976 ms  13.978 ms
 9  137.221.70.32 (137.221.70.32)  13.664 ms  13.176 ms  13.180 ms
10  rt0sj-equinix.cl.shawcable.net (206.223.116.20)  17.173 ms  15.325 ms  15.330 ms
11  rc1wt-be60.wa.shawcable.net (66.163.75.89)  32.836 ms  32.295 ms  30.970 ms
12  rc2wt-be18-1.wa.shawcable.net (66.163.64.82)  31.090 ms  31.308 ms  31.329 ms
13  rc3no-be100.cg.shawcable.net (66.163.75.234)  46.048 ms  46.042 ms  46.493 ms
14  rc1we-be6.ed.shawcable.net (66.163.64.70)  50.081 ms  51.899 ms  51.873 ms
15  dx6lo-lag1.ed.shawcable.net (64.59.186.166)  52.128 ms  53.162 ms  53.192 ms


29/01/2019 05:24:49 UTC
--------------------

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=58.4 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=57.4 ms
64 bytes from 70.74.86.188: icmp_seq=3 ttl=49 time=56.8 ms
64 bytes from 70.74.86.188: icmp_seq=4 ttl=49 time=57.1 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 2997ms
rtt min/avg/max/mdev = 56.836/57.490/58.473/0.632 ms


29/01/2019 05:24:49 UTC
--------------------

PING:
PING 70.74.86.188 (70.74.86.188) 56(84) bytes of data.
64 bytes from 70.74.86.188: icmp_seq=1 ttl=49 time=57.8 ms
64 bytes from 70.74.86.188: icmp_seq=2 ttl=49 time=59.2 ms

--- 70.74.86.188 ping statistics ---
4 packets transmitted, 2 received, 50% packet loss, time 2999ms
rtt min/avg/max/mdev = 57.881/58.560/59.240/0.721 ms


29/01/2019 05:24:49 UTC
--------------------

MTR:
Start: Tue Jan 29 05:24:49 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.4   0.3   0.2   0.5   0.0 Blizzard 0.0%    10    0.5   1.7   0.5   9.3   2.7
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.7   0.6   0.8   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.5   0.6   0.5   0.8   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.9  13.0  12.7  13.3   0.0
  6.|-- 137.221.65.68                        0.0%    10   35.3  17.7  12.7  35.3   8.2
  7.|-- 137.221.65.1                         0.0%    10   29.8  14.6  12.6  29.8   5.3
  8.|-- 137.221.65.7                         0.0%    10   13.0  15.0  12.6  34.4   6.8
  9.|-- 137.221.70.32                        0.0%    10   12.7  13.3  12.6  19.4   2.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   15.2  14.5  13.0  16.6   1.2
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   30.8  31.8  30.7  36.6   1.7
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   32.3  31.8  30.9  32.5   0.0
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.4  46.2  45.9  46.8   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.9  49.9  49.8  50.1   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.5  50.4  50.1  51.4   0.3
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net   0.0%    10   62.0  59.5  57.0  62.8   2.3


29/01/2019 05:24:49 UTC
--------------------

MTR:
Start: Tue Jan 29 05:24:50 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.2   0.3   0.2   0.4   0.0 Blizzard 0.0%    10    0.6   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.5   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.5   0.7   0.5   0.8   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.8  12.9  12.7  13.9   0.0
  6.|-- 137.221.65.68                        0.0%    10   12.8  12.9  12.7  13.1   0.0
  7.|-- 137.221.65.1                         0.0%    10   26.8  16.3  12.7  33.4   7.4
  8.|-- 137.221.65.7                         0.0%    10   12.9  13.1  12.8  14.3   0.0
  9.|-- 137.221.70.32                        0.0%    10   12.6  12.7  12.5  13.3   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   12.8  13.9  12.6  16.5   1.1
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   30.9  31.2  30.8  32.5   0.3
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   32.4  31.2  30.8  32.4   0.5
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.3  46.2  46.0  46.5   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.8  49.9  49.6  50.2   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.3  50.3  50.1  50.9   0.0
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net  10.0%    10   62.3  59.1  56.9  62.8   2.6


29/01/2019 05:24:49 UTC
--------------------

EDIT: Not Sure if this will be helpful at all but I ran more Looking glass tests from my work’s shaw connection:

MTR:
Start: Tue Jan 29 18:35:01 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.4   0.2   1.1   0.0 Blizzard 0.0%    10    0.6   1.2   0.5   6.9   1.8
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.6   0.5   0.9   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.9   0.7   0.5   0.9   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.9  13.8  12.8  22.3   2.9
  6.|-- 137.221.65.68                        0.0%    10  2505. 4612. 2505. 7008. 1505.2
  7.|-- 137.221.65.1                         0.0%    10   12.8  29.5  12.8 118.0  33.2
  8.|-- 137.221.65.7                         0.0%    10   12.9  12.9  12.7  13.0   0.0
  9.|-- 137.221.70.32                        0.0%    10   12.6  12.7  12.5  13.4   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   16.2  14.6  12.7  16.2   0.8
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   30.9  31.2  30.7  32.3   0.5
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   30.9  31.1  30.8  32.3   0.0
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.2  46.1  45.8  46.3   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.9  50.0  49.7  51.5   0.3
 15.|-- dx8ch-la1-s1.ed.int.shawcable.net    0.0%    10   50.2  50.2  50.1  50.4   0.0
 16.|-- S0106a84e3f829583.ed.shawcable.net   0.0%    10   63.1  64.8  58.3  92.3   9.9


29/01/2019 18:35:01 UTC
--------------------

MTR:
Start: Tue Jan 29 18:35:01 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.3   0.0 Blizzard 0.0%    10    0.6   0.6   0.6   0.8   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.7   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.7   0.7   0.5   1.2   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.9  15.3  12.6  27.5   5.2
  6.|-- 137.221.65.68                        0.0%    10  2317. 4540. 2317. 6868. 1454.3
  7.|-- 137.221.65.1                         0.0%    10   15.4  21.5  12.6  62.4  15.7
  8.|-- 137.221.65.7                         0.0%    10   12.8  16.0  12.7  44.6  10.0
  9.|-- 137.221.70.32                        0.0%    10   12.9  12.7  12.5  12.9   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   16.1  14.6  12.6  16.2   0.9
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   32.1  31.3  30.8  32.1   0.3
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   32.4  31.4  30.8  32.4   0.6
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   46.1  46.2  45.9  47.0   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.8  49.9  49.6  50.2   0.0
 15.|-- dx8ch-la1-s1.ed.int.shawcable.net    0.0%    10   50.1  50.1  50.1  50.2   0.0
 16.|-- S0106a84e3f829583.ed.shawcable.net   0.0%    10   63.2  61.9  58.4  70.8   3.6


29/01/2019 18:35:01 UTC
--------------------



MTR:
Start: Tue Jan 29 18:37:31 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.5   0.3   0.2   0.5   0.0 Blizzard 0.0%    10    0.7   0.6   0.5   0.7   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.6   0.5   0.7   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.7   0.7   0.6   0.8   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.9  15.1  12.8  34.8   6.9
  6.|-- 137.221.65.68                        0.0%    10   21.3  15.5  12.8  30.2   5.7
  7.|-- 137.221.65.1                         0.0%    10   12.9  16.0  12.8  43.5   9.6
  8.|-- 137.221.65.7                         0.0%    10   13.0  12.9  12.7  13.3   0.0
  9.|-- 137.221.70.32                        0.0%    10   12.7  12.7  12.5  12.8   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   15.2  14.5  13.0  15.6   0.6
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   30.9  31.2  30.9  32.3   0.3
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   31.0  31.1  30.8  32.1   0.3
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   45.9  46.2  45.9  46.4   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.8  49.9  49.6  50.2   0.0
 15.|-- dx8ch-la1-s1.ed.int.shawcable.net    0.0%    10   50.1  50.2  50.1  50.8   0.0
 16.|-- S0106a84e3f829583.ed.shawcable.net   0.0%    10   64.2  62.5  58.8  69.4   3.9


29/01/2019 18:37:31 UTC
--------------------

MTR:
Start: Tue Jan 29 18:37:31 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.4   0.0 Blizzard 0.0%    10    0.7   0.6   0.5   0.8   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.6   0.5   0.6   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.7   1.1   0.5   5.2   1.2
  5.|-- 137.221.83.66                        0.0%    10   13.0  15.4  12.8  32.4   6.0
  6.|-- 137.221.65.68                        0.0%    10   12.8  18.0  12.8  44.8  10.4
  7.|-- 137.221.65.1                         0.0%    10   12.8  16.4  12.7  48.3  11.2
  8.|-- 137.221.65.7                         0.0%    10   13.1  20.6  12.8  65.3  17.5
  9.|-- 137.221.70.32                        0.0%    10   12.7  12.7  12.6  12.8   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   15.4  14.7  13.1  15.9   0.7
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   32.2  31.1  30.7  32.2   0.5
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   31.0  31.4  31.0  32.3   0.3
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   45.8  46.1  45.8  46.4   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.8  50.0  49.6  50.3   0.0
 15.|-- dx8ch-la1-s1.ed.int.shawcable.net    0.0%    10   50.3  50.2  50.1  50.8   0.0
 16.|-- S0106a84e3f829583.ed.shawcable.net   0.0%    10   62.0  64.0  58.9  83.5   7.2


29/01/2019 18:37:31 UTC
--------------------

Last test from home:

MTR:
Start: Wed Jan 30 02:40:31 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.2   0.2   0.2   0.3   0.0 Blizzard 0.0%    10    0.5   0.5   0.4   0.7   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.6   0.5   0.5   0.7   0.0
  4.|-- 137.221.66.16                        0.0%    10    0.6   0.6   0.5   0.7   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.7  49.3  12.7 168.0  56.8
  6.|-- 137.221.65.68                        0.0%    10   12.8 1213.  12.8 2692. 1022.9
  7.|-- 137.221.65.1                         0.0%    10   12.7  24.1  12.7  86.5  23.4
  8.|-- 137.221.65.7                         0.0%    10   12.7  15.8  12.7  43.8   9.8
  9.|-- 137.221.70.32                        0.0%    10   12.6  12.6  12.5  12.7   0.0
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   14.0  14.5  12.6  16.2   1.1
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   30.9  31.0  30.7  32.2   0.3
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   31.2  30.9  30.8  31.2   0.0
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   45.8  46.0  45.8  46.3   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.9  49.8  49.6  50.1   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.2  50.2  50.2  50.4   0.0
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net   0.0%    10   57.4  57.4  56.8  58.9   0.3


30/01/2019 02:40:31 UTC
--------------------

MTR:
Start: Wed Jan 30 02:40:31 2019 Blizzard  1.|-- Blizzard                         0.0%    10    0.3   0.3   0.2   0.3   0.0 Blizzard 0.0%    10    0.5   0.6   0.5   0.6   0.0
  3.|-- 137.221.105.10                       0.0%    10    0.5   0.9   0.4   3.6   0.7
  4.|-- 137.221.66.16                        0.0%    10    0.8   0.6   0.5   0.8   0.0
  5.|-- 137.221.83.66                        0.0%    10   12.7  59.8  12.7 205.8  73.5
  6.|-- 137.221.65.68                        0.0%    10   12.7 1141.  12.7 2676. 1014.5
  7.|-- 137.221.65.1                         0.0%    10   12.7  35.3  12.7 155.3  47.5
  8.|-- 137.221.65.7                         0.0%    10   12.9  12.9  12.8  13.2   0.0
  9.|-- 137.221.70.32                        0.0%    10   12.6  13.5  12.5  19.7   2.2
 10.|-- rt0sj-equinix.cl.shawcable.net       0.0%    10   14.2  14.4  12.5  16.5   1.2
 11.|-- rc1wt-be60.wa.shawcable.net          0.0%    10   31.8  31.2  30.8  32.1   0.0
 12.|-- rc2wt-be18-1.wa.shawcable.net        0.0%    10   30.8  31.3  30.8  32.3   0.3
 13.|-- rc3no-be100.cg.shawcable.net         0.0%    10   45.8  46.1  45.8  46.4   0.0
 14.|-- rc1we-be6.ed.shawcable.net           0.0%    10   49.9  50.0  49.8  50.2   0.0
 15.|-- dx6lo-lag1.ed.shawcable.net          0.0%    10   50.2  50.2  50.2  50.3   0.0
 16.|-- S0106bc9b688eaf0f.ed.shawcable.net   0.0%    10   56.9  59.5  56.9  63.0   2.5


30/01/2019 02:40:31 UTC
--------------------

Drakuloth · February 1, 2019, 12:27am

VeiledFlame,

Watched the new video and checked the new looking glasses and absolutely none of this explains the behavior - bizarre. Your PNG (black line) fluctuations are totally normal, there’s no packet loss, and there’s no evidence of any of our other metrics that would matter for this having bad spikes. The looking glass traces you sent back are fine, too. There’s one node that appears to be having large latency spikes, but that’s just mitigation (you can tell because the latency goes back down.)

You said the issue as reduced on a VPN but didn’t fully go away. I’m wondering if we’re looking at the wrong culprit here. Would you please send an MSInfo to techinfo@blizzard.com with the subject ATTN: Drakuloth - VeiledFlame Double Animation Error? I’d also like to have you close everything on your PC down and run a user benchmark test. Download the app (in the top-middle of the page), run it with as few programs as possible running on the PC, and then paste the link for the test into your next reply. I’ll give all that a look and see if maybe it’s a bizarre hardware issue or we’ve got some program fighting us on your PC.

VeiledFlame-1983 · February 1, 2019, 3:42am

Appreciate you looking into the issue Drakuloth. I just sent the information over.

I should tell you though this issue happens on 3 separate computers so chances its hardware are unlikely. And like I said I had someone message me on my twitch from Calgary, AB using Shaw that said he had the exact issue as well as my friend on a Telus that lives 5 minutes from me in Edmonton. I don’t really know why all of us would have the same issue. The issue is only visible (from what I’ve tested) when using Genji. But the feeling of input lag/delayed shots happens with all characters.

I built 3 different computers in an attempt to solve the issue as I was pretty serious about competitive play. But that didn’t seem to affect the problem.

Correct but keeping in mind VPNs are unstable connections on their own so the issue happening once in a while would make sense, I would imagine they experience moments of increased latency/packets loss from the nature of a VPN. I truly wish it was my PC as I would think it would’ve solved by building 3 different PCs. But if you see anything that might cause it hardware-side let me know and I’ll look into it.

I’m open to any suggestions you have of course so let me know the next steps when you get a chance.

Drakuloth · February 1, 2019, 3:54am

Looking this over - the only thing I see here is that your AudioDG.exe is losing its everloving mind. Can you try disabling your extra audio apps/adapters and see if you can run straight through USB or a 3.5mm jack on your motherboard? You’ve got audio software I don’t see particularly commonly - IcePower’s IceSound. Sound is heavily processed on the CPU and if the CPU is hiccuping over it, it could theoretically cause this odd behavior. Any luck with that? (Admission here - That is a bit of a hail mary, but I’m still looking for other options.)

While I give this file another once over, can we get another winMTR from you to us? Your netgraph looked perfectly clean, but I just realized that we haven’t gotten a long duration test from you to us since your ISP mentioned they fixed the problem with your local node. Let’s make sure we catch a couple double animation hiccups with this test - maybe leave it running for 5-10 minutes while you practice headshots in either training or a match vs bots. I’m fond of mcree vs 6 ana opponents, headshots only mode, but you could use genji too.

VeiledFlame-1983 · February 2, 2019, 2:35am

Appreciate the tip on the audio issue, wasn’t aware that was going on I had installed Realtek drivers before. I tested this theory by removing all audio drivers, disabling them in the device manager and disabling in the bios as well. Issue happened right away despite having no audio connected whatsoever. So it can’t be that.

I made a headshot custom game and ran an MTR to it as requested to the server I was on but the MTR came out clean other than some what I would assume is fake packet loss on the second hop as it didn’t propagate to any other hops:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -    0 |  644 |  644 |    0 |    0 |    2 |    1 |
|                             96.52.128.1 -    1 |  640 |  639 |    6 |   18 |  514 |    7 |
|             rh9we-cmts.ed.shawcable.net -    0 |  644 |  644 |    7 |   11 |   74 |   11 |
|                           66.163.70.129 -    0 |  644 |  644 |    7 |   12 |   64 |   11 |
|              rc3no-be6.cg.shawcable.net -    0 |  644 |  644 |   11 |   15 |   61 |   20 |
|            rc2wt-be100.wa.shawcable.net -    0 |  644 |  644 |   26 |   29 |   35 |   27 |
|     rc6wt-tge0-10-0-11.wa.shawcable.net -    0 |  644 |  644 |   26 |   30 |   70 |   31 |
|              ae1-br01-eqse2.as57976.net -    0 |  644 |  644 |   51 |   56 |  117 |   52 |
|       xe-0-0-0-1-br01-eqsv5.as57976.net -    0 |  644 |  644 |   44 |   49 |  148 |   45 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |  644 |  644 |   52 |   61 |  195 |   56 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  129 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

The three blizzard hops before the ‘no response’ hops had high latency, but in game I didn’t see any latency being reported. I’m at a loss as to what is happening.

Description of feeling in game:
This game had lots of double animations as well as (what I would describe as) a lot of shot delay. I used to be able to flick shot with genji but it seems like when i click the shot is going off late, then usually a shot later I have the double animation occurring. It felt like input lag that only applies to my actions, such as shooting or using an ability.

So far Overwatch is the only game I own that has any issue resembling double animations. When I played WoW mid 2018 there were tons of latency issues then as well that never went away, which is why I quit that game too; at the time I had both Telus and Shaw, they both had identical issues. VPNs had the same effect on WoW, where my latency was lower routing through chicago. Any other non-blizzard online game seems perfectly fine to play. And I should mention all offline games I own run amazingly well with no sign of these delays or double animations.

Let me know if you have anything else you need me to test and I’ll give it a shot.

EDIT: Tested this on my other PC and had the same issue.

A long test to google as well:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                                10.0.0.1 -    0 | 1720 | 1720 |    0 |    0 |    3 |    0 |
|                             96.52.128.1 -    0 | 1720 | 1720 |    6 |   17 |  745 |    7 |
|             rh9we-cmts.ed.shawcable.net -    0 | 1720 | 1720 |    5 |   10 |   67 |    7 |
|                           66.163.70.129 -    0 | 1720 | 1720 |    7 |   12 |  122 |    8 |
|              rc3no-be6.cg.shawcable.net -    0 | 1720 | 1720 |    9 |   13 |   34 |   13 |
|            rc2wt-be100.wa.shawcable.net -    0 | 1720 | 1720 |   26 |   29 |   47 |   28 |
|                            72.14.242.90 -    0 | 1720 | 1720 |   23 |   28 |   57 |   26 |
|                   No response from host -  100 |  345 |    0 |    0 |    0 |    0 |    0 |
|                         108.170.233.158 -    0 | 1720 | 1720 |   26 |   28 |   45 |   28 |
|                           209.85.242.39 -    0 | 1720 | 1720 |   26 |   28 |   45 |   27 |
|                sea15s07-in-f3.1e100.net -    0 | 1720 | 1720 |   26 |   28 |   49 |   28 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

VeiledFlame-1983 · April 12, 2019, 3:47am

I’m posting back here because its been months after I asked for help with no response so let me just continue where we left off. This is STILL happening with no resolution. I know now this has nothing to do with my ISP or my own personal connection, I went to my friends houses and tried all their PCs/ISPs with overwatch as well as going to an internet cafe here in Edmonton. All 6 PCs i tried at the internet cafe had this issue too. At the very least this is might be Alberta related. Can’t believe I’ve had to wait 3 years to have a blizzard employee even investigate this instead of just telling me to post WinMTRs. So here’s the facts if anyone from blizzard actually does anything:

-Double animations still occur with over 15 computers I’ve tested
-Double animations still occur with 3 different ISPs at approximately 5-7 separate houses/areas I’ve visited to check

If this isn’t enough of a clue that you guys need to investigate something I’m not sure what else I can do. Unless you literally want me to come and troubleshoot it myself.

Cgg-21889 · April 12, 2019, 8:27am

Just my 2 bits. I’ve seen this happen in OW (in bad network conditions).

That looks a lot like a command that didn’t make it in time to the server. So the server ran out of buffer and extrapolated what you wanted by duplicating your latest known command (that’s a reasonable assumption) until it receives the actual command out of band and corrects your situation ingame (you’re firing) with a slight delay.

The client receives the update from the server for the firing event that it had predicted correctly but too early compared to what happened, and the animation rolls back.

I think you might have some subclinical network issues. Your traceroutes aren’t totally okay imo. You have a bad lag spike and some minimal loss when you enter the Blizzard network (as57976).

Also you mentioned it happened with other Blizzard games and apparently other people from your area?

Don’t get mad though. It’s hard to go through self-reported issues when they are fringe cases.