i can play d3 on my pc with no issues or lag. d4 on my ps5 is a laggy, rubber banding nightmare.
both wireless, same bandwidth to both (300/20), low ping (7-100 via speedtest) same isp, it may not be d4 servers, but whatever the issue is, it’s localized to d4, i have no problems in other games.
I do see a bit of loss at your first hop here: (I have highlighted in bold the numbers we are looking at)
That shows a 2% loss. While that doesn’t sound like much, even a 1% loss can affect voice communication for example. It won’t affect normal web use much or watching video though. It can muck with gaming however.
That 2% is right at your router. Now it could be because you are using a wireless connection, but I’m guessing there.
However at your Comcast, you have a 42% loss. That’s nearly half the traffic!
I do see that the latency is a bit all over here as well and a bit high overall.
TraceRT doesn’t show the problems like the WinMTR did, nor did the pathping.
But there are obviously issues as WinMTR shows. So Comcast is causing an issue with your path while you are playing Diablo IV.
Thank you for taking the time to do these tests! And everyone else that can do them will help to narrow this down as well.
Please if you can, attempt to run these tests on your connection as well. My post is above:
I get massive rubberbanding now and then in EU. When I do a traceroute to the D4 EU IP that blizzard supplies (35.240.124.178) I get a hop to a US IP (209.85.174.232) and everything after that is nil. Why is there a US hop in there?
exactly the same, game is virtually unplayable, it has been for the past damn week, its ridiculous. 2 bad the first 2 hours worked perfectly, just so I cant refund lol
I’m on 600MB line connection from my home, PC hardwired to a very modern gaming router, and on several random tests here in the afternoon from Central Florida to several speed test servers in Chicago (where the Blizzard servers are located) I just pulled 139-154 Mbps down with 0% packet loss… and Diablo IV has been rubberbanding and disconnecting me over and over for the past hour.
It’s definitely on their server’s side, and quite annoying at this point this long after the launch of their biggest title in years.
Blizzard needs to get their server performance cleaned up or get more servers online.
Post the results here. Lets find out for sure? I have been tracking this issue for the past 2 days. This also will help us find out what the real problem is. I think their network traffic is trigging some of the ISPs to block it. Lets find out if they are blocking you too.
So far I have at least 4 or 5 now that show the ISP causing up to 50% loss on the game traffic.
Thanks!
WinMTR just does TraceRt and Ping in a single tool, same you can get with PowerShell or just PathPing - but many servers may/will not respond to such requests so you’ll get timeouts all along the route just from that server setting alone (this prevents “ping of death” DoS attacks). I tried TraceRT (in PowerShell) and WinMT to Blizzard’s Central US Diablo IV server (34.170.230.40) and there were many Unresponsive servers, because that’s just Ping commands, not TCP packets (which I believe Diablo IV uses way more of than UDP for gameplay).
I don’t know enough about network commands to create my own TCP “ping” that wouldn’t get filtered out… but considering literally nothing else online has any issues for me except trying to play Diablo IV without getting disconnected and rubberbanded very frequently, I’m sticking with my assertion that it’s their servers with the issue.
I received the game on Saturday and since I have been unable to really play because of serious rubber banding and ping issues (Usually between 300-1500). I’m the only one on my network (wireless) at the moment. I have an older gaming laptop, but I can still play games (Like WH40K Darktide, even if I have to go to low graphics settings) just fine. Blizzards servers are the only ones I’m having this issue with. D3 and D4 (sorry not gonna resubscribe to WoW to get a ping) both are giving me the ping issue.
The problem I have is that between 11pm and 2am central last night I was able to play with no rubber banding or ping issues at all. My ping stayed between 75 and 120.
So I logged on again this morning and low and behold, 300-1500 ping and rubber banding like a fiend with skills going off 2-3 seconds after I click em. If Diablo 3 wasn’t having the same issue as 4 I would probably have accepted that it’s my laptop, but since it is, I know it’s at Blizzards end.
Yes, but it runs while you play the game. And that is because the issue is only happening with the game’s traffic. Please, take the time to do the test, unless you are afraid of the results?
Here’s my take on it. The reason I’m trying to get as many of these run as I can, is to prove there is an issue with the traffic itself. We have reports on the forum about the game causing network routers to stop working, why wouldn’t it be possible for ISPs to block their traffic too? So I need to prove this. And I can only do that with as many of these test results as I can gather.
Ok? Please just run the test as described and post the results when you have time. Thanks!
Well, its funny when looking at these two you posted. D4 is showing a loss of only 1% at one location, but D3 is showing a 63% loss just after ASNet here:
So there actually may be an issue someplace after it leaves Charter, but its not showing up all the time, if that makes sense. I will say the results are mixed, but if need be you can run the WinMTR again when you are in the middle of having the high ping. (once it starts, just run the app)
Let me know if you find anything different, but thank you for doing this!
Those are the WinMTR readings I took while playing just now while experiencing the high ping. I’ve seen other WinMTR readouts that have packet loss and the loss continues down the line, but if you look at the one for D3 the 63% packet loss doesn’t continue, it just experiences loss at that point but no more afterwards. It also only receives 1/4 of the packets sent for other pings. So maybe I just don’t know how to read it.
I also tried to do the pingpath test, but it just ends at the first hop outside my router.
In the end it’s just a shame I was having fun last night.
Well, the program tests each node along the path. That node apparently showed a 63% loss of traffic. That is pretty huge.
1-2% can cause issues gaming. It will even cause voice and video calls to break up. At 5% some websites start having issues. And 10% or more can start affecting video playback on some services.
But still, thanks for taking the time. I have had a couple like yours that show no issues, and several that did. But its best to check them all.
I have virtually no issues when inside a dungeon - my own personal instanced area. Solid 60+ FPS on any setting (low, medium, high, etc.).
However, once I am outside in the world it’s a never ending parade of FPS stuttering, rubber banding and disconnecting. I can barely get by in the open world with* the FPS stutters and rubber banding, however, once I TP anywhere there is a solid chance I disconnect. I have never seen my latency (as listed in-game) higher than 150 either.
I feel I’ve done everything and everything I could possibly do with no avail - like the rest of these poor souls. I understand that with new games there are always going to be optimization issues (especially with PCs), however, I think with the amount of people - and the wide array of devices (console included), this is simply more than just something on the players’ end.
Hopefully Blizzard will at least acknowledge this because being unable to play nor being able to get a refund is simply an awful experience.
Edit:
Running around through the more world, I am seeing spikes as high as 600.
Crossplay is turned off in the settings and I still receive the “You have cross network play enabled.” message.
