Same issues happens to me on my mac. My latency is low and doesn’t seem to be the reason for this issue. The issue happens in many instances. If I stop moving in SW, characters around me stop mid run and start running in place four about 5-6 seconds until they resume (UNLESS I move my character, then everybody starts moving normally).
So literally, the issue seems to be stopping movement. If I run around Stormwind, everybody moves normally and there’s no lag. As soon as I stop, the lag comes back. This also happens when turning in quests: I hit “Complete Quest” the window freezes and doesn’t update, forcing me to take a step with my character, then the quest window updates with the new quest.
Seems to be a serious performance issue for macs, blues, what can we do to help remediate this?
Same problem here. 15" Macbook Pro Vega 20 graphics. Lag occurs at all times and places, constantly–unless I keep my character or the camera moving. When I am in a battle I have to stay moving around the entire time or else it will just freeze there for about 5 seconds at a time.
If it’s happening on a fully different PC that does point towards network. Can you run a WinMTR test on the PC while this happens? You can just use the first IP address listed for WoW for this. You want to restart the test every 10-15 minutes until you catch one of these problems. Once you’ve caught one red handed, run the test for about 5 more minutes. This will let us look for problems between your house and our servers which may cause this, and may help us confirm if it’s indeed an ATT thing or even something with one of our peers.
If you have problems with posting it due to a link error, go ahead and copy paste this into your next post, and replace “WinMTR goes here” with your test.
This is happening to me on WoW classic. I’m playing on a 2019 MacBook Pro with Vega 20 graphics card. It’s more noticeable on my mage and my hunter. I seem to freeze after turning on auto shot unless I cast another shot or move my character constantly. Because of this I’m now constantly strafing left or right after the 0.5 seconds I need to stand still for auto shots.
First, just an FYI … asking me to do something technical with a Windows OS is like asking a brain surgeon to do open heart surgery. I know the basics, but I certainly cannot claim to know what I’m doing.
Well, running WinMTR on the Windows laptop seemed to “cure” the lag on the laptop. However, it is just as bad as ever on the Mac. I hate playing on the little screen of the laptop.
Is there a Mac version of WinMTR?
I did notice that 75.8.128.104 seemed to have a pretty bad % number even though there wasn’t really any notable lag. Is that something you can do anything about?
LOL … Runsinshadow, please refer to the first paragraph in my reply above. No way I’m doing anything on Terminal unless the President of Blizzard sends a post with precise directions for the coding-impared. Maybe they could code a button in the interface panel? “System Batching Disabled”
Very pretty characters who run in place on my Mac … hoping that ends soon.
This is where I’m actually concerned for now - there’s some loss of packets and latency spikes between your PC and router. (The % number is packet loss percentage). The IP you saw later in the test (75.8.128.104) is just ignoring some of your test packets - you can tell this is what’s happening because everything goes back to normal right after that node. Meanwhile, the packet loss we see between your PC/Router persists through the whole test.
Let’s turn off both your windows/mac machine, unplug the modem/router for 10 minutes, and retest. If that fails, can we run a path ping from the mac instead and post it here? I’d like to compare it to your winMTR, and that might work a bit better with your brain surgeon training.
that feeling you get when you find the forum post in the technical support section pertaining to your exact problem… but its not been resolved yet.
So I game on a PC usually, but had to move to my Mac for now. Things seemed fine until I actually started to play and noticed this exact problem going on.
I have a 2017 iMac 5k, 27", 3.8 i5, 8gb, lotsa room, lotsa bandwidth, no latency.
Okay, now you’re asking me to do rocket science! I had reset my router once before to no effect; however, I don’t think I turned everything off and unplugged it for 10min. So, I did that yesterday afternoon. The entire rest of the day and for about an hour this morning the game ran wonderfully. Then, bam … lag reasserted itself. Well, hubby will be most annoyed if I make him turn off the football game over and over … So I ran a path ping. Hope this tells you something. (FYI, I had to delete the “t” on net in line 2 and 6 so it wouldn’t think it was a link.)
1 homeportal (192.168.1.254) 10.546 ms 4.699 ms 4.852 ms 4.910 ms 4.297 ms 4.490 ms * 3.714 ms 4.475 ms 5.287 ms 4.573 ms 5.834 ms * 3.562 ms 4.474 ms 4.718 ms 4.327 ms 4.638 ms * 4.913 ms (15% loss)
2 75-13-84-1.lightspeed.austtx.sbcglobal.ne (75.13.84.1) 25.678 ms 25.665 ms 31.344 ms 26.534 ms 45.181 ms 55.952 ms 24.936 ms 35.303 ms 25.735 ms 25.719 ms 26.742 ms 26.060 ms 32.012 ms 25.617 ms 24.880 ms * 25.625 ms 25.320 ms 26.110 ms 26.000 ms (5% loss)
3 71.149.76.45 (71.149.76.45) 25.648 ms 27.096 ms 25.070 ms 24.596 ms 26.682 ms 26.216 ms 26.846 ms 24.819 ms 27.318 ms 29.158 ms 28.562 ms 26.706 ms 34.235 ms 25.686 ms 25.362 ms * 30.614 ms 25.760 ms 25.914 ms 25.540 ms (5% loss)
4 * * 75.8.128.104 (75.8.128.104) 26.392 ms 27.809 ms 26.851 ms 27.929 ms 25.299 ms 25.644 ms 28.031 ms 26.373 ms 30.069 ms 26.683 ms * * * * * * * * (50% loss)
5 12.81.225.241 (12.81.225.241) 26.289 ms 26.574 ms
12.81.225.237 (12.81.225.237) 27.981 ms 27.522 ms
12.81.225.241 (12.81.225.241) 27.760 ms 27.761 ms
12.81.225.237 (12.81.225.237) 28.310 ms 27.467 ms
12.81.225.241 (12.81.225.241) 28.365 ms 27.415 ms
12.81.225.237 (12.81.225.237) 27.206 ms 27.915 ms
12.81.225.241 (12.81.225.241) 28.337 ms
12.81.225.237 (12.81.225.237) 26.584 ms
12.81.225.241 (12.81.225.241) 27.982 ms 27.474 ms
12.81.225.237 (12.81.225.237) 27.721 ms 28.114 ms
12.81.225.241 (12.81.225.241) 28.024 ms 27.427 ms (0% loss)
6 dlstx409me9.ip.att.ne (12.123.18.133) 31.797 ms 31.469 ms 31.135 ms 32.837 ms 31.956 ms 31.332 ms 32.561 ms 31.681 ms 31.068 ms 31.340 ms 30.661 ms 33.287 ms 34.004 ms 33.218 ms 34.440 ms * 36.852 ms 31.666 ms 29.717 ms 31.040 ms (5% loss)
7 * * * * * * * * * * * * * * * * * * * * (100% loss)
8 * * * * * * * * * * * * * * * * * * * * (100% loss)
9 * * * * * * * * * * * * * * * * * * * * (100% loss)
10 * * * *
Thanks for providing the pathping test and trying the extended powercycle , Morgane!
There’s definitely still some signs of packet loss on the home network here.
The * are indications of packet loss. We’ll want to focus our troubleshooting on the home network. What’s the router/modem models in the household? Does this happen during a certain time in the day or when others are online and using other network devices?
I have the AT&T Uverse Wireless Modem and WAP. There’s no specific name on those items, but there’s a number on the front of the modem: 5268AC. I also use a Netgear extender across the house. I tried turning it off, but there was no change from above. I ran a pathping without opening the game just for grins and this is what I got: 1 homeportal (192.168.1.254) 7.537 ms 3.559 ms 5.050 ms 5.031 ms 5.055 ms 4.560 ms * 10.075 ms 4.687 ms 4.576 ms 4.823 ms 4.703 ms * 9.895 ms 4.987 ms 5.329 ms 4.959 ms 4.947 ms
Don’t know if that tells you anything other than there was only one asterisk.
It happens intermittently all the time … people on other devices, everyone off, a couple things on, etc.
There have been two extended periods when the lag was stopped: the first time I reset my UI for the game and again when I unplugged the modem/router for ten minutes. Repeating these attempts didn’t yield the same positive results. It’s like the gremlin in the works learned what I had “deleted” to make the game work and put it back in, denying me the second time!
There seem to be a lot of people saying that they’re having the same problem, also the exact same problem. How would fixing my network help them? Not trying to be argumentative … just curious.
I can concur with Morgane on some of the similarities, that my problem is intermittent now. I seemed to notice it more on my hunter and not as much on my druid. I am playing my hunter solo though, but playing my druid with my wife and we’re both on the same network, but she is on a PC laptop with no problems. Were also running off a AT&T Uverse Wireless Modem 5268AC. No bridge, no extenders.
The problem was mostly non-existent yesterday. Started to show back up again last night after playing on my hunter for awhile. The only things I can think of on my side of the network thats going on throughout the day and evening is other users in the house streaming videos, netflix, youtube, etc.
It is awesome that there is attempt to find a resolution …
But Morgane raised a valid point… if the problem is a home network problem for Morgrane, how is that going to help the rest of us with the exact same problem… who are not logged on to Morgane’s home network???
Same issue. It is like the game is batching the animations. If I A/D while skinning or even wanding everything plays properly. If I am not doing additional movements like using A/D it just seems to pause and suddenly catch up.
Easy test is skinning, I can tell by the sound when the skill is up as that lines up with the cast bar. Yet the character can be stuck skinning unless I am also twirling the character with A or D or just rapidly tapping both. Herbing is longer cast so I only need A/D right at the end. Since it also seems extra likely to happen on a killing blow it really feels as if animations are not queuing correctly or being batched so they wait for more things to happen before the execute. the sounds are on time
When servers are near capacity the problem seems to increase. Yet always adding the A/D smooths it out.
Thanks for your reports everyone! It was tagged onto the last response to try and see if the channel lag was due to the home network as well. The same behavior in both connection tests for Morgane was still persisting, which is why some additional details were requested from Morgane.
Though with this brought up there’s definitely some details I think will help, would each of you be able to provide a pathping and traceroute test as well as the router/modem model? Though it doesn’t seem to be impacting every player on the home network, these details may help in case it may be due to similar hardware or settings like mitigation or prioritization of the home network causing the same issue for everyone here.
Going to load up the Windows Machine and see if it has similar issues. nope, the windows copy plays smoothly. what is more annoying is retail has no issues and I am obviously using the same iMac for retail and classic.
Okay, this is just odd. The iMac stops at #6 which is the last AT&T hop just before blizzard takes over 137.221.75.33 stuff++
(EDIT: FWIW I have to edit out dns names as it says its a link and that is not allowed)
Well here is the trace route from the iMac
iMac:~ WhiteStar$ traceroute 24.105.62.129
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 52 byte packets
1 homeportal (192.168.1.254) 12.308 ms 4.320 ms 3.222 ms
2 (107.128.92.1) 5.659 ms 7.468 ms 5.281 ms
3 107.212.168.126 (107.212.168.126) 8.949 ms 9.400 ms 7.531 ms
4 12.83.82.209 (12.83.82.209) 12.306 ms 20.431 ms 39.150 ms
5 (12.122.96.89) 12.321 ms 11.372 ms 11.051 ms
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
if I trace route from the Windows PC right next to it
1 3 ms 2 ms 2 ms homeportal [192.168.1.254]
2 5 ms 5 ms 6 ms [107.128.92.1]
3 7 ms 6 ms 10 ms 107.212.168.126
4 10 ms 9 ms 11 ms 12.83.82.209
5 9 ms 9 ms 8 ms [12.122.96.89]
6 9 ms 9 ms 11 ms 12.247.68.74
7 31 ms 31 ms 31 ms [137.221.75.33]
8 893 ms 218 ms 218 ms [137.221.65.46]
9 31 ms 33 ms 30 ms [137.221.69.71]
10 30 ms 31 ms 30 ms 24.105.62.129
JUST SO YOU KNOW - IT IS IMPOSSIBLE TO POST LOOKING GLASS RESULTS BECAUSE " YOU CAN’T POST LINKS IN YOUR EDIT"
Okay, fixed the trace route issue. OS X/Unix platforms do not default to ICMP packets so apparently that is being blocked by that one router which servers the blizzard farm; it is blocking UDP in an attempt to prevent DDOS?
traceroute to 24.105.62.129 (24.105.62.129), 64 hops max, 72 byte packets
1 homeportal (192.168.1.254) 5.082 ms 4.673 ms 5.115 ms
2 '(107.128.92.1) 6.375 ms 11.884 ms 11.908 ms
3 107.212.168.126 (107.212.168.126) 9.264 ms 9.420 ms 9.945 ms
4 12.83.82.209 (12.83.82.209) 12.633 ms 11.584 ms 11.556 ms
5 (12.122.96.89) 12.755 ms 10.622 ms 10.253 ms
6 12.247.68.74 (12.247.68.74) 11.091 ms 11.038 ms 11.085 ms
7 (137.221.75.33) 33.410 ms 32.073 ms 33.914 ms
8 (137.221.65.46) 31.797 ms 31.759 ms 31.499 ms
9 (137.221.69.71) 32.917 ms 35.467 ms 34.432 ms
10 24.105.62.129 (24.105.62.129) 32.390 ms 33.910 ms 33.567 ms
,