Just to be clear,
I think you might have subclinical routing issues (spikes on the way up to the blizzard network).
Game buffers are designed to accommodate spikes while keeping you on the bleeding edge. Think of it as a tradeoff.
Random bad spikes in an otherwise very stable network context will have these kind of results.
Let’s keep things civil please.
If the issue goes away on your mobile connection, and returns as soon as you use an ISP in your area, then it still points to the ISPs as the source of the problem.
It does sound like a city or province level hub is the culprit, but Blizzard doesn’t control those lines, hubs, or the routing they use – the ISP does.
Because of this, my best advice (other than relocating) is to try some VPNs and see if you can find improvement with one of them.
I do not believe that Blizzard will contact the ISP on your behalf since you are the ISP’s customer, but if you were going to ask that, you should use the ticket service.
I re-tested this theory and it turned out to be coincidental, the issue persisted when using a VPN. The problem still actually happens on the phone’s connection as well. Keeping in mind of course out here we only have two real ISPs and all the others use their lines. Actually this double animation issue has gotten worse since a patch a little while back. It was actually completely gone for about 2 weeks then a game patch hit and now it consistently happens almost every shot.
The issue was hard to diagnose before as it used to only happen seemingly at certain times but now its constant. I tested many locations with the VPN and they all still had the same problem.
If anything it would be provincial as I had two people from Calgary contact me after they saw a video I uploaded of the issue. Also wouldn’t all these ISPs use separate hubs? Or do they all share one? Not really sure how that works as I’m nowhere near a network technician.
But more than that I’m curious how 2 completely separate ISPs have the same issues, because I currently have Shaw 600mbps (cable) as well as Telus (DSL) 50mbps. Also of course I tested Telus fibre as well at the Internet cafe with the same problems.
And I apologize for my frustration but I’ve been going back and forth for close to 3 years now trying to get an answer to this problem with no end in sight.
I’m a programmer with experience in netcode and I’ve had some interest in OW’s netcode lately (top-notch). So I see your problem through that lens (for instance routing is beyond me). But what you show in your video is something I know about through my experience with OW’s networking. I know how to produce network conditions that consistently result in these double animations (nothing super complicated, as I mentionned it’s just making the server run out of buffered commands).
The problem with the ingame graph is that it’s the client view. It only indirectly hints at what’s happening on the server side.
If you’re desperate (like, really desperate) I can help you do some debugging with the network. But that involves more tedious attempts (like digging into network dumps) and uncertain results. It would (might) validate the network as being the culprit. You’d need to evaluate what’s wrong with your ISP by some other means then, which is even more tedious/uncertain.
Also from experience (in professional contexts) it’s very hard to get anything from an ISP (or any online provider). So unless you intend to lobby them hard or get divine intervention from Blizzard, all of this would end up being just for sports.
This is an exact description of what I think might be your problem:
loss or delayed packets (latency spikes).
Your connection (judging from your graphs) is otherwise super stable, so buffering for you in the game would be super minimal.
Yeah I’ve had support tickets that lasted for months on both ends that they gave up on so I know how that usually works.
It looks like Shaw is going to at least take a look to see if there’s anything wrong, they’ve escalated the issue for me and want me to run more testing. I still have no idea where the blame lies but hopefully they find something. All I know so far is it had nothing to do with my equipment or area node.
Something between Shaw/Telus & connecting to blizzard is where the issue is. Just finding and convincing whomever needs to fix it is always the issue.
Honestly with my poor knowledge in routing I would have thought the problem lay at the interconnection between Blizzard and your local infrastructure.
But that you have the same issue connecting through various VPN sort of points to your local infrastructure as having very odd quirks.
Can only confirm that from my experience it does look like random lag spikes on your way up to the blizz network.
Either way definitely very odd. Keep us posted I wanna know.
VeiledFlame,
Been a while, looks like I missed your previous reply. I have a totally network-unrelated idea here since we have exhausted that pretty extensively. If this happens on multiple PCs in multiple locations and on multiple networks, I am somewhat curious about HOW you play the characters that you are having this problem on. I’ve never been able to reproduce this myself. When you are throwing your shuriken, are you single pressing the right click button, or do you have some kind of spam macro programmed or are you spamming the button or scrollwheel or something like that? I’m curious if potentially some of your commands are just getting swallowed as you are one of a single digit number of reports we’ve ever gotten of this.
Well I play the character like I would imagine any normal user would. The easiest way for me to replicate this issue is specific to genji sadly (which is my main). I still get the delayed actions on all characters however, probably close to 0.25-0.5s delay on shots though it varies heavily almost like the connection spikes but its not reported that way. I don’t use macros or anything special.
Also keep in mind even though you only have single-digit reports of issues I tested this quite literally across my city and it happened on every single PC (15 of them). I didn’t even so much as bring my keyboard or mouse, it was all different configurations and ISPs (though here we’re limited to Shaw & Telus only). I reproduced the issue simply by going into the training grounds, picking genji and using right click. Also worth mentioning I had two people from Calgary contact me about the identical issue, they found a couple forum posts I made and saw the video I had posted on my twitch channel.
I literally just right click and time the right click for when I assume the previous animation will finish, which is how I always played when I was playing on Edmonton’s ‘official’ e-sports team. Only difference is back then this issue didn’t happen consistently and I was very content. I’m not sure what changed but over time the issue has gotten drastically worse. I’m actually testing it right now and it happens almost every shot.
So its as simple as this:
This results in one of 3 things:
However nothing else is wrong with the game (that i can see), other heroes don’t rubber-band only shots that I take & abilities are being effected.
Personally I believe the issue is somehow province specific, I don’t know how or why but this seems to be the case. And since I can’t isolate where on the route its happening I can’t even attempt to fix it. All I know is its not my equipment specifically, hence why I tested it wherever I could in my city.
VeiledFlame,
If it’s not some kind of mouse macro spamming, that rules that out at least. Is there any change if you go into the Settings>Gameplay menu and limit the client or server send rate? How about if you limit them individually? Is it better, or worse? Obviously we don’t want you doing this long term if you have sufficient bandwidth but it may be useful diagnostic information.
Limit Client send rate seems to change nothing at all
Limit Server send rate causes audio for connecting shots to disappear as well as a delay, ping goes up by 10ms
Double animations still persist on any variation of the two.
VeiledFlame,
We’re running out of ideas here. Can you put in a ticket on this issue and link them the thread? We’ll need a new copy of your MSinfo and DXDiag and for you to send in a callback request. This is really deep in the woods so we’ll want to talk with you live about it. I left a note on your account about this situation. If we can’t identify anything else, this may be something to bug report.
Much appreciated I’ll fill that out as soon as possible, I’ve made my ISP aware of this as well so we’ll see if they find anything
For what it’s worth I tried reproducing your issue by creating retention on the upstream line (client to server), basically: occasionally buffering a few outbound packets and then delivering them all at once.
It does create double animations (mispredictions), slight shot delays, does not spike the netgraph as it takes place on the upstream band, does not appear as loss either as it’s just delay in delivery.
Though it does not appear exactly as in your video so it might be off.
Maybe you have a faulty node in your region that throttles packets? Something along those lines. Does it happen on other servers? regions? in other games?
For reproducing: clumsy on “udp” with outbound throttling and a low delay (~30ms) and reasonable frequency (~5% chance) so the server is not given a chance to adapt.
Good luck and for posterity, let us know ![:slight_smile:](https://d74zh8edaijub.cloudfront.net/en/overwatch/images/emoji/twitter/slight_smile.png?v=6" ":slight_smile:")
Its hard to determine if its happening in other games since the netcode I believe is quite different in Overwatch compared to some other FPS so I can’t confidently say it doesn’t happen. The only fact I know for sure is both ISPs exhibit the same symptoms.
More Tests for Blizzard:
Telus WinMTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 580 | 580 | 0 | 0 | 20 | 1 |
| 10.145.148.1 - 0 | 580 | 580 | 4 | 7 | 26 | 6 |
| STTLWAWBCI01.bb.telus. com - 0 | 580 | 580 | 21 | 22 | 44 | 22 |
| 154.11.2.145 - 0 | 580 | 580 | 22 | 23 | 70 | 22 |
| ae1-br01-eqse2.as57976 .net - 0 | 580 | 580 | 71 | 73 | 141 | 72 |
| xe-0-0-0-1-br01-eqsv5.as57976 .net - 0 | 580 | 580 | 76 | 78 | 139 | 76 |
| xe-0-0-1-1-br02-eqla1.as57976 .net - 0 | 580 | 580 | 71 | 80 | 194 | 75 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 117 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Shaw WinMTR
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.1 - 0 | 494 | 494 | 0 | 0 | 3 | 0 |
| 96.52.128.1 - 0 | 494 | 494 | 7 | 29 | 43 | 7 |
| rh9we-cmts.ed.shawcable.net - 0 | 494 | 494 | 8 | 15 | 87 | 17 |
| 66.163.70.129 - 0 | 494 | 494 | 8 | 18 | 94 | 15 |
| rc3no-be6.cg.shawcable.net - 0 | 494 | 494 | 12 | 19 | 53 | 16 |
| rc2wt-be100.wa.shawcable.net - 0 | 494 | 494 | 27 | 33 | 57 | 32 |
| rc6wt-tge0-10-0-11.wa.shawcable.net - 0 | 494 | 494 | 27 | 33 | 73 | 32 |
| ae1-br01-eqse2.as57976.net - 0 | 494 | 494 | 52 | 59 | 121 | 57 |
| xe-0-0-0-1-br01-eqsv5.as57976.net - 0 | 494 | 494 | 53 | 61 | 193 | 58 |
| xe-0-0-1-1-br02-eqla1.as57976.net - 0 | 494 | 494 | 54 | 66 | 156 | 59 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 101 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Telus Looking Glass
TRACEROUTE:
traceroute to 198.166.124.252 (198.166.124.252), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.243 ms 0.244 ms 0.244 ms Blizzard(24.105.18.3) 0.898 ms 0.918 ms 1.470 ms
3 137.221.105.16 (137.221.105.16) 0.605 ms 0.850 ms 0.888 ms
4 137.221.66.22 (137.221.66.22) 0.600 ms 0.853 ms 0.865 ms
5 137.221.83.68 (137.221.83.68) 30.255 ms 30.272 ms 30.277 ms
6 137.221.65.68 (137.221.65.68) 30.121 ms 30.364 ms 30.354 ms
7 137.221.65.1 (137.221.65.1) 30.346 ms 30.332 ms 30.331 ms
8 137.221.65.7 (137.221.65.7) 30.124 ms 30.139 ms 30.107 ms
9 137.221.65.41 (137.221.65.41) 30.207 ms 30.220 ms 30.217 ms
10 137.221.73.32 (137.221.73.32) 30.443 ms 29.915 ms 29.961 ms
11 154.11.2.144 (154.11.2.144) 29.753 ms 29.682 ms 29.647 ms
12 * * *
13 * * *
14 d198-166-124-252.abhsia.telus.net (198.166.124.252) 55.511 ms 55.117 ms 55.221 ms
14/04/2019 19:21:40 UTC
--------------------
TRACEROUTE:
traceroute to 198.166.124.252 (198.166.124.252), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.252 ms 0.241 ms 0.241 ms Blizzard(24.105.18.3) 5.625 ms 5.751 ms 6.063 ms
3 137.221.105.16 (137.221.105.16) 1.027 ms 1.042 ms 1.057 ms
4 137.221.66.22 (137.221.66.22) 1.037 ms 1.034 ms 1.032 ms
5 137.221.83.68 (137.221.83.68) 30.202 ms 30.216 ms 30.219 ms
6 137.221.65.68 (137.221.65.68) 30.001 ms 31.334 ms 31.343 ms
7 137.221.65.1 (137.221.65.1) 31.353 ms 31.348 ms 31.347 ms
8 137.221.65.7 (137.221.65.7) 31.345 ms 31.347 ms 31.344 ms
9 137.221.65.41 (137.221.65.41) 29.981 ms 31.071 ms 31.063 ms
10 137.221.73.32 (137.221.73.32) 30.184 ms 29.940 ms 29.904 ms
11 154.11.2.144 (154.11.2.144) 29.780 ms 29.802 ms 30.813 ms
12 * * *
13 d198-166-124-252.abhsia.telus.net (198.166.124.252) 55.180 ms 55.199 ms 55.179 ms
14 d198-166-124-252.abhsia.telus.net (198.166.124.252) 56.040 ms 55.350 ms 55.304 ms
14/04/2019 19:21:40 UTC
--------------------
MTR:
Start: Sun Apr 14 19:21:40 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.5 0.2 3.0 0.7 Blizzard 0.0% 10 0.6 0.6 0.5 1.2 0.0
3.|-- 137.221.105.16 0.0% 10 0.6 0.6 0.5 0.8 0.0
4.|-- 137.221.66.22 0.0% 10 0.6 0.6 0.6 0.8 0.0
5.|-- 137.221.83.68 0.0% 10 30.2 34.8 30.1 51.6 8.6
6.|-- 137.221.65.68 0.0% 10 30.1 31.1 30.0 39.7 3.0
7.|-- 137.221.65.1 0.0% 10 30.3 31.5 30.1 38.9 2.9
8.|-- 137.221.65.7 0.0% 10 30.2 30.1 30.0 30.4 0.0
9.|-- 137.221.65.41 0.0% 10 30.1 30.1 30.1 30.2 0.0
10.|-- 137.221.73.32 0.0% 10 29.9 30.8 29.9 37.5 2.2
11.|-- 154.11.2.144 0.0% 10 30.1 30.0 29.8 30.7 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- d198-166-124-252.abhsia.telus.net 0.0% 10 55.2 54.6 54.0 55.2 0.0
14/04/2019 19:21:40 UTC
--------------------
MTR:
Start: Sun Apr 14 19:21:41 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.5 0.0 Blizzard 0.0% 10 0.7 0.7 0.5 0.9 0.0
3.|-- 137.221.105.16 0.0% 10 0.7 0.7 0.5 0.9 0.0
4.|-- 137.221.66.22 0.0% 10 0.7 0.8 0.5 1.9 0.0
5.|-- 137.221.83.68 0.0% 10 30.3 34.6 30.0 67.6 11.7
6.|-- 137.221.65.68 0.0% 10 30.3 36.5 30.1 62.8 13.1
7.|-- 137.221.65.1 0.0% 10 30.2 31.2 30.0 40.2 3.1
8.|-- 137.221.65.7 0.0% 10 30.1 30.2 30.0 31.3 0.3
9.|-- 137.221.65.41 0.0% 10 30.1 30.3 30.0 30.9 0.0
10.|-- 137.221.73.32 0.0% 10 30.1 30.0 29.8 30.8 0.0
11.|-- 154.11.2.144 0.0% 10 29.9 29.9 29.8 30.1 0.0
12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
13.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14.|-- d198-166-124-252.abhsia.telus.net 0.0% 10 55.2 55.4 55.1 56.1 0.0
14/04/2019 19:21:40 UTC
--------------------
Shaw Looking Glass
TRACEROUTE:
traceroute to 96.52.141.244 (96.52.141.244), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.252 ms 0.247 ms 0.247 ms
2 24.105.18.131 (24.105.18.131) 0.724 ms 0.728 ms 0.777 ms
3 137.221.105.12 (137.221.105.12) 0.547 ms 0.606 ms 0.702 ms
4 137.221.66.16 (137.221.66.16) 0.657 ms 0.661 ms 0.648 ms
5 137.221.83.66 (137.221.83.66) 12.832 ms 12.835 ms 12.838 ms
6 137.221.65.68 (137.221.65.68) 12.700 ms 12.920 ms 12.897 ms
7 137.221.65.1 (137.221.65.1) 12.860 ms 12.872 ms 12.872 ms
8 137.221.65.7 (137.221.65.7) 13.003 ms 13.010 ms 13.010 ms
9 137.221.70.32 (137.221.70.32) 19.720 ms 19.710 ms 19.702 ms
10 rt0sj-equinix.cl.shawcable.net (206.223.116.20) 16.313 ms 15.461 ms 14.919 ms
11 rc1wt-be60.wa.shawcable.net (66.163.75.89) 30.967 ms 30.868 ms 30.641 ms
12 rc2wt-be18-1.wa.shawcable.net (66.163.64.82) 51.872 ms 51.865 ms 51.341 ms
13 rc3no-be100.cg.shawcable.net (66.163.75.234) 47.360 ms 46.761 ms 46.723 ms
14 rc1we-be6.ed.shawcable.net (66.163.64.70) 50.236 ms 50.257 ms 50.107 ms
15 dx6lo-lag1.ed.shawcable.net (64.59.186.166) 50.304 ms 50.209 ms 52.305 ms
14/04/2019 19:25:39 UTC
--------------------
TRACEROUTE:
traceroute to 96.52.141.244 (96.52.141.244), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.390 ms 0.390 ms 0.392 ms
2 24.105.18.131 (24.105.18.131) 0.860 ms 0.925 ms 0.999 ms
3 137.221.105.12 (137.221.105.12) 0.735 ms 0.827 ms 0.946 ms
4 137.221.66.16 (137.221.66.16) 0.727 ms 0.744 ms 0.745 ms
5 137.221.83.66 (137.221.83.66) 12.964 ms 12.970 ms 12.972 ms
6 137.221.65.68 (137.221.65.68) 12.711 ms 12.770 ms 12.742 ms
7 137.221.65.1 (137.221.65.1) 12.883 ms 12.893 ms 12.884 ms
8 137.221.65.7 (137.221.65.7) 13.136 ms 13.132 ms 13.129 ms
9 137.221.70.32 (137.221.70.32) 12.653 ms 12.662 ms 12.667 ms
10 rt0sj-equinix.cl.shawcable.net (206.223.116.20) 15.809 ms 15.696 ms 14.972 ms
11 rc1wt-be60.wa.shawcable.net (66.163.75.89) 30.879 ms 31.081 ms 30.730 ms
12 rc2wt-be18-1.wa.shawcable.net (66.163.64.82) 44.633 ms 44.021 ms 43.998 ms
13 rc3no-be100.cg.shawcable.net (66.163.75.234) 47.335 ms 47.347 ms 47.341 ms
14 rc1we-be6.ed.shawcable.net (66.163.64.70) 52.809 ms 52.131 ms 52.107 ms
15 dx6lo-lag1.ed.shawcable.net (64.59.186.166) 51.608 ms 51.764 ms 50.176 ms
14/04/2019 19:25:39 UTC
--------------------
MTR:
Start: Sun Apr 14 19:25:39 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.7 0.2 2.8 0.6
2.|-- 24.105.18.131 0.0% 10 0.5 1.8 0.5 7.1 1.9
3.|-- 137.221.105.12 0.0% 10 0.5 0.7 0.5 2.0 0.3
4.|-- 137.221.66.16 0.0% 10 0.4 0.7 0.4 1.0 0.0
5.|-- 137.221.83.66 0.0% 10 12.6 12.8 12.6 13.0 0.0
6.|-- 137.221.65.68 0.0% 10 12.8 23.5 12.7 98.1 27.0
7.|-- 137.221.65.1 0.0% 10 59.3 20.9 12.6 59.3 15.4
8.|-- 137.221.65.7 0.0% 10 12.7 12.8 12.7 12.9 0.0
9.|-- 137.221.70.32 0.0% 10 12.4 12.8 12.4 13.8 0.0
10.|-- rt0sj-equinix.cl.shawcable.net 0.0% 10 12.5 14.5 12.5 16.0 1.1
11.|-- rc1wt-be60.wa.shawcable.net 0.0% 10 32.4 31.1 30.8 32.4 0.3
12.|-- rc2wt-be18-1.wa.shawcable.net 0.0% 10 30.7 31.7 30.7 37.8 2.2
13.|-- rc3no-be100.cg.shawcable.net 0.0% 10 45.9 46.4 45.8 50.6 1.4
14.|-- rc1we-be6.ed.shawcable.net 0.0% 10 50.0 50.0 50.0 50.1 0.0
15.|-- dx6lo-lag1.ed.shawcable.net 0.0% 10 50.3 50.4 50.2 51.6 0.3
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14/04/2019 19:25:39 UTC
--------------------
MTR:
Start: Sun Apr 14 19:25:39 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.5 0.2 2.4 0.6
2.|-- 24.105.18.131 0.0% 10 0.5 0.6 0.4 1.4 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.8 0.5 1.5 0.0
4.|-- 137.221.66.16 0.0% 10 0.5 1.6 0.5 9.5 2.7
5.|-- 137.221.83.66 0.0% 10 12.8 13.1 12.7 15.2 0.7
6.|-- 137.221.65.68 0.0% 10 25.3 25.7 12.8 77.2 22.2
7.|-- 137.221.65.1 0.0% 10 14.0 18.4 12.7 59.8 14.8
8.|-- 137.221.65.7 0.0% 10 12.8 15.8 12.7 42.8 9.4
9.|-- 137.221.70.32 0.0% 10 12.6 12.7 12.6 13.0 0.0
10.|-- rt0sj-equinix.cl.shawcable.net 0.0% 10 15.4 14.9 13.0 16.4 0.9
11.|-- rc1wt-be60.wa.shawcable.net 0.0% 10 31.7 34.5 30.9 42.2 4.3
12.|-- rc2wt-be18-1.wa.shawcable.net 0.0% 10 30.7 31.4 30.7 32.3 0.0
13.|-- rc3no-be100.cg.shawcable.net 0.0% 10 46.1 46.2 45.9 47.3 0.0
14.|-- rc1we-be6.ed.shawcable.net 0.0% 10 49.8 50.1 49.6 52.0 0.6
15.|-- dx6lo-lag1.ed.shawcable.net 0.0% 10 50.2 50.3 50.2 50.3 0.0
16.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
14/04/2019 19:25:39 UTC
--------------------
Hey all,
Currently we’re in agreement with Cgg that this is probably some kind of Sim misprediction. Since the server is considered the ‘source of truth’ of what actually happens in game, what is likely happening is that VeiledFlame’s client is mis-predicting when his attack animation can go off. The client then receives a packet from the server which then corrects the animation, resulting in the odd behavior.
I’ve changed the title of this thread to better reflect the area that this is occurring in. If anybody else in Alberta is seeing this behavior, please post the following information:
Copy the code I have below and paste your tests into the designated lines:
~~~~
WinMTR goes here
~~~~
~~~~
Looking Glass goes here
~~~~
In the mean time, we’re gut checking ourselves with the engineers on this to make sure we’re on the right track. Thanks for all the help so far VeiledFlame. We’ll provide more insight as we can.
What I suggest if it helps, I can make you connect to a game for which I know the netcode. I’ll be able to tell if there’s something odd there.
Because it’s a different system it could provide new insights and help us understand. I’ll share the data (in private). It takes 1h max if you’re down.
Sorry to have barged in btw, that ended up catching my curiosity.
Appreciate the all the help so far Drakuloth, I’ll keep an eye out for any updates. If you guys happen upon anything relating to either Shaw or Telus let me know as well so I can make them aware.
That would be great if you wouldn’t mind. The biggest thing is trying to find out if there’s network instability with other games, so this would be incredibly helpful.
Not at all, I’m curious about it.
Any way we can get in touch so I have you get the game? Or I can just leave my battletag.
If that’s okay I’ll make you connect to a dev server. That way I’ll also have a network dump of your packets.
I’ll connect along with you. It shouldn’t take more than 20m once you’re set up. Also maybe have your VPN handy so we can test a different route.
Sure leave me your battletag and I’ll add you when I’m off work. I’ll use the more stable of the two ISPs for the test, and yeah my VPN is all good to go on that PC.
Sounds great, and thanks again for helping me out. It’s been…interesting trying to figure this out to say the very least.