Slight Combat Input Lag?

Support Technical Support
1

< Edit > Found out that it’s related to an issue that came up in December/January with being in a highly populated shard. No current fix available.

Hello! I’m looking for any help/suggestions that you guys can throw my way for dealing with this issue as it’s pretty detrimental to the overall experience whilst playing.

The issue is very difficult for me to describe accurately, but once actively using combat abilities (both in and out of instances), after a few seconds of being in combat and firing off abilities, it becomes very messy. It feels like there is slight delay (maybe less than half a second) in between the GCD being used and the actual ability itself going off. I tend to float around 20-45ms while in and out of instances.

I’ve restarted my router & computer, reinstalled my AddOns & WoW, played around with the spellqueuewindow, updated all graphic drivers, disabled antivirus, checked for any new network drivers, disabled unnecessary background programs, and scanned for any viruses to no avail.

I used the battlenet looking-glass to run a traceroute to Tichdonrius and got this.

TRACEROUTE:
traceroute to 70.190.243.154 (70.190.243.154), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.354 ms 0.325 ms 0.306 ms
2 24.105.18.131 (24.105.18.131) 0.696 ms 1.164 ms 1.177 ms
3 137.221.105.12 (137.221.105.12) 0.648 ms 1.153 ms 1.200 ms
4 137.221.66.20 (137.221.66.20) 1.155 ms 1.156 ms 1.155 ms
5 137.221.83.68 (137.221.83.68) 6.577 ms 6.580 ms 6.579 ms
6 137.221.65.68 (137.221.65.68) 6.531 ms 5.764 ms 5.760 ms
7 137.221.68.32 (137.221.68.32) 5.507 ms 5.504 ms 5.564 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.369 ms 5.441 ms 5.445 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 18.365 ms 18.346 ms 18.342 ms
10 ip70-190-243-154.ph.ph.cox. net (70.190.243.154) 28.605 ms 28.597 ms 32.289 ms

14/04/2019 07:41:08 UTC

PING:
PING 70.190.243.154 (70.190.243.154) 56(84) bytes of data.
64 bytes from 70.190.243.154: icmp_seq=2 ttl=53 time=28.7 ms

— 70.190.243.154 ping statistics —
4 packets transmitted, 1 received, 75% packet loss, time 2998ms
rtt min/avg/max/mdev = 28.715/28.715/28.715/0.000 ms

14/04/2019 07:41:08 UTC

TRACEROUTE:
traceroute to 70.190.243.154 (70.190.243.154), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.686 ms 0.692 ms 0.695 ms
2 24.105.18.131 (24.105.18.131) 2.316 ms 2.345 ms 2.346 ms
3 137.221.105.12 (137.221.105.12) 0.678 ms 0.680 ms 1.577 ms
4 137.221.66.20 (137.221.66.20) 3.114 ms 3.136 ms 3.140 ms
5 137.221.83.68 (137.221.83.68) 6.299 ms 6.304 ms 6.307 ms
6 137.221.65.68 (137.221.65.68) 5.793 ms 5.728 ms 5.716 ms
7 137.221.68.32 (137.221.68.32) 5.512 ms 5.556 ms 5.567 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.338 ms 5.459 ms 5.451 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 17.821 ms 17.730 ms 17.725 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

14/04/2019 07:41:08 UTC

PING:
PING 70.190.243.154 (70.190.243.154) 56(84) bytes of data.

— 70.190.243.154 ping statistics —
4 packets transmitted, 0 received, 100% packet loss, time 3008ms

14/04/2019 07:41:08 UTC

TRACEROUTE:
traceroute to 70.190.243.154 (70.190.243.154), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.465 ms 0.548 ms 0.565 ms
2 24.105.18.131 (24.105.18.131) 1.699 ms 1.706 ms 1.712 ms
3 137.221.105.12 (137.221.105.12) 1.524 ms 1.567 ms 1.640 ms
4 137.221.66.20 (137.221.66.20) 1.568 ms 1.574 ms 1.579 ms
5 137.221.83.68 (137.221.83.68) 5.974 ms 6.000 ms 6.007 ms
6 137.221.65.68 (137.221.65.68) 6.640 ms 6.063 ms 6.046 ms
7 137.221.68.32 (137.221.68.32) 5.961 ms 5.959 ms 5.972 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.645 ms 5.684 ms 5.693 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 20.524 ms 19.692 ms 19.661 ms
10 ip70-190-243-154.ph.ph.cox. net (70.190.243.154) 27.594 ms * *

14/04/2019 07:41:13 UTC

PING:
PING 70.190.243.154 (70.190.243.154) 56(84) bytes of data.
64 bytes from 70.190.243.154: icmp_seq=2 ttl=53 time=29.1 ms

— 70.190.243.154 ping statistics —
4 packets transmitted, 1 received, 75% packet loss, time 3004ms
rtt min/avg/max/mdev = 29.191/29.191/29.191/0.000 ms

14/04/2019 07:41:13 UTC

TRACEROUTE:
traceroute to 70.190.243.154 (70.190.243.154), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.459 ms 0.481 ms 0.493 ms
2 24.105.18.131 (24.105.18.131) 1.308 ms 1.352 ms 1.364 ms
3 137.221.105.12 (137.221.105.12) 1.294 ms 1.337 ms 1.382 ms
4 137.221.66.20 (137.221.66.20) 1.342 ms 1.350 ms 1.356 ms
5 137.221.83.68 (137.221.83.68) 6.122 ms 6.165 ms 6.178 ms
6 137.221.65.68 (137.221.65.68) 5.884 ms 10.101 ms 10.110 ms
7 137.221.68.32 (137.221.68.32) 5.500 ms 5.930 ms 5.940 ms
8 langbbrj02-ae1.301.r2.la.cox. net (68.105.30.129) 5.552 ms 5.555 ms 5.561 ms
9 chnddsrj01-ae1.0.rd.ph.cox. net (68.1.5.211) 17.879 ms 17.901 ms 17.909 ms
10 * ip70-190-243-154.ph.ph.cox. net (70.190.243.154) 29.282 ms *

14/04/2019 07:41:15 UTC

PING:
PING 70.190.243.154 (70.190.243.154) 56(84) bytes of data.
64 bytes from 70.190.243.154: icmp_seq=1 ttl=53 time=28.8 ms
64 bytes from 70.190.243.154: icmp_seq=2 ttl=53 time=28.4 ms

— 70.190.243.154 ping statistics —
4 packets transmitted, 2 received, 50% packet loss, time 2998ms
rtt min/avg/max/mdev = 28.439/28.627/28.816/0.253 ms

14/04/2019 07:41:17 UTC

MTR:
Start: Sun Apr 14 07:41:08 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 1.1 0.3 5.0 1.4
2.|-- 24.105.18.131 0.0% 10 0.7 0.7 0.5 1.4 0.0
3.|-- 137.221.105.12 0.0% 10 0.9 0.7 0.5 0.9 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 0.7 0.5 0.9 0.0
5.|-- 137.221.83.68 0.0% 10 5.9 7.3 5.8 19.5 4.2
6.|-- 137.221.65.68 0.0% 10 5.8 19.0 5.7 76.1 27.7
7.|-- 137.221.68.32 0.0% 10 5.7 5.7 5.5 6.1 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.6 5.7 5.4 7.3 0.5
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 23.5 23.3 17.5 54.0 11.8
10.|-- ip70-190-243-154.ph.ph.cox. net 0.0% 10 28.5 28.8 27.8 29.7 0.3

14/04/2019 07:41:08 UTC

MTR:
Start: Sun Apr 14 07:41:09 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.4 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.6 1.8 0.5 12.9 3.9
3.|-- 137.221.105.12 0.0% 10 0.7 1.2 0.5 6.3 1.6
4.|-- 137.221.66.20 0.0% 10 0.6 1.8 0.5 11.5 3.4
5.|-- 137.221.83.68 0.0% 10 5.7 6.6 5.6 13.0 2.2
6.|-- 137.221.65.68 0.0% 10 5.9 12.3 5.6 40.8 13.9
7.|-- 137.221.68.32 0.0% 10 5.6 5.6 5.4 5.7 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 7.5 5.3 25.0 6.2
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 17.5 19.7 17.5 37.6 6.3
10.|-- ip70-190-243-154.ph.ph.cox. net 20.0% 10 29.6 29.5 28.4 32.0 1.0

14/04/2019 07:41:09 UTC

MTR:
Start: Sun Apr 14 07:41:09 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.4 0.3 0.6 0.0
2.|-- 24.105.18.131 0.0% 10 1.4 0.7 0.5 1.4 0.0
3.|-- 137.221.105.12 0.0% 10 0.5 0.6 0.5 0.8 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 0.7 0.6 1.2 0.0
5.|-- 137.221.83.68 0.0% 10 5.7 9.1 5.7 28.0 7.3
6.|-- 137.221.65.68 0.0% 10 7.1 8.1 5.7 27.4 6.8
7.|-- 137.221.68.32 0.0% 10 5.6 5.7 5.5 5.9 0.0
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 5.4 5.4 5.6 0.0
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 17.7 17.8 17.6 18.0 0.0
10.|-- ip70-190-243-154.ph.ph.cox. net 90.0% 10 28.4 28.4 28.4 28.4 0.0

14/04/2019 07:41:08 UTC

MTR:
Start: Sun Apr 14 07:41:14 2019 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.2 0.4 0.0
2.|-- 24.105.18.131 0.0% 10 0.8 1.3 0.5 6.9 1.9
3.|-- 137.221.105.12 0.0% 10 1.1 0.7 0.5 1.1 0.0
4.|-- 137.221.66.20 0.0% 10 0.7 1.2 0.7 5.9 1.5
5.|-- 137.221.83.68 0.0% 10 6.0 5.8 5.7 6.0 0.0
6.|-- 137.221.65.68 0.0% 10 5.7 13.6 5.6 52.1 16.5
7.|-- 137.221.68.32 0.0% 10 5.6 5.8 5.5 7.4 0.5
8.|-- langbbrj02-ae1.301.r2.la.cox. net 0.0% 10 5.4 7.6 5.3 26.9 6.7
9.|-- chnddsrj01-ae1.0.rd.ph.cox. net 0.0% 10 22.8 18.8 17.6 22.8 1.6
10.|-- ip70-190-243-154.ph.ph.cox. net 50.0% 10 34.1 29.7 27.7 34.1 2.5

14/04/2019 07:41:14 UTC

I also ran a WinMTR to the west coast IP and got this.

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|------------------------------------------------|------|------|------|------|------|------|

| 192.168.0.1 - 0 | 224 | 224 | 0 | 0 | 6 | 0 |

| 10.97.100.1 - 0 | 224 | 224 | 6 | 8 | 16 | 8 |

| 100.127.77.0 - 0 | 224 | 224 | 7 | 9 | 21 | 9 |

| 100.120.100.36 - 0 | 224 | 224 | 10 | 14 | 53 | 14 |

| 68.1.4.252 - 0 | 224 | 224 | 22 | 28 | 93 | 38 |

| 68.105.30.130 - 0 | 224 | 224 | 20 | 24 | 50 | 23 |

| ae1-br01-eqla1.as57976. net - 0 | 224 | 224 | 27 | 34 | 120 | 35 |

| et-0-0-2-br01-swlv10.as57976. net - 0 | 224 | 224 | 27 | 36 | 219 | 32 |

| et-0-0-31-pe02-swlv10.as57976. net - 0 | 224 | 224 | 24 | 28 | 44 | 27 |

| las-swlv10-ia-bons-04.as57976. net - 0 | 224 | 224 | 26 | 30 | 38 | 30 |

| 137.221.105.2 - 0 | 224 | 224 | 24 | 29 | 35 | 27 |

I’m not very savvy at reading & troubleshooting this type of stuff, so any advice/solutions are greatly appreciated!

1 Like
2

Noticed this myself just a few minutes ago. I guess its similar. Every time I cast a spell there is a delay with the spell actually triggering. Was doing the dinosaur quest at warbeast in zuldazar where you have to out run the T rex, and everytime I would push the run button, and throw the toy button to distract dino, it took a good 15 seconds for the spell to activate. Had no problems this morning. Just started happening within the last hour. Latency is 43 ms(home), 40 ms(world). My fps hover around 90 to 100. Edit. Also happening when trying mount up.

3

This generally seems to be a WoW thing at times. Zone lag happens for whatever reason and you get annoying spell delay despite your MS being good.

4

This has been an issue for me since BFA launched. For me it’s only in the open world though. Instanced content hasn’t been affected. I’m not on a high population realm though.

1 Like
5

Just logged back into game after being logged off for a couple hours to see if it was fixed. Still the same as it was earlier sadly.

6

Seems like the only solution to this issue till they fix it is to either play on a low population server or just play a ranged caster where it’s less noticeable.