Constantly Rubberbanding and Disconnecting on PC

This is 100 percent THERE PROBLEM, its nothing to do with our internet, sure it can be, but this clearly isn’t a user issue. Its disgusting

2 Likes

More info, should it provide any additional information. Earlier in the date the rubberbanding was omnipresent, the winMTR data looked like this.

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

|                                      WinMTR statistics                                   |

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

|------------------------------------------------|------|------|------|------|------|------|
|host-131-239-211-185.customer.veroxity.net -  0 | 1830 | 1830 |    0 |    1 |   43 |    1 |
|             160.72.248.50.lightower.net -    0 | 1830 | 1830 |    2 |    4 |   51 |    5 |
|          ae11-nycmnyzrj93.lightower.net -    0 | 1830 | 1830 |    1 |    2 |   89 |    4 |
|      et-2-0-0.mcs2.lga5.us.zip.zayo.com -    0 | 1830 | 1830 |    3 |    4 |   36 |    7 |
|            ae1.cs2.lga5.us.eth.zayo.com -    0 | 1830 | 1830 |    3 |    4 |   26 |    3 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                            72.14.215.92 -    0 | 1830 | 1830 |    4 |    4 |   15 |    5 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |  372 |    0 |    0 |    0 |    0 |    0 |

However tonight, the rubberbanding was gone, all other game and internet settings untouched. This is something I mentioned earlier also happened last weekend. But this time I at least have some winMTR data:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|host-131-239-211-185.customer.veroxity.net -    0 |  280 |  280 |    0 |    1 |   16 |    0 |
|             160.72.248.50.lightower.net -    0 |  280 |  280 |    2 |    5 |   79 |    2 |
|          ae11-nycmnyzrj93.lightower.net -    0 |  280 |  280 |    1 |    3 |   39 |    2 |
|      et-2-0-0.mcs2.lga5.us.zip.zayo.com -    0 |  280 |  280 |    3 |    5 |   44 |    6 |
|            ae1.cs2.lga5.us.eth.zayo.com -    0 |  280 |  280 |    3 |    5 |   22 |    6 |
|          ae19.ter1.ewr1.us.zip.zayo.com -   99 |   58 |    1 |    0 |    6 |    6 |    6 |
|                            72.14.215.92 -    0 |  280 |  280 |    4 |    4 |   13 |   13 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|                   No response from host -  100 |   57 |    0 |    0 |    0 |    0 |    0 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

I’m not saying any of this makes sense, I just wanted to pass along the data.

1 Like

According to those, you have a good connection. The 100% loss on some servers just mean they don’t respond to the test. The others were 0. So… No issues that I can see with either result.

1 Like

I am having the same issue.
Yesterday i tried the following and the amount of disconnects got reduced drasticly.

  1. Removed my secondary monitor
  2. Closed discord

None of the two solutions is in my opinion viable, but it seems to me that diablo cant handle processes from the second screen.
Having discord open while using one monitor still gave alot of disconnect.

Maybe one of you can use the info to get closer to a solution. Hope it helps

I found a fix for my issues with crashing that might help a few. Mind you I still rubber-band a bit when loading into zones but at least I am not straight up crashing.

I have an SLI bridge with 2x Nvidia 1080s. I had issues where the usage of card 1 was 90%+ and the fan would scream despite being only on medium graphic settings (I had lowered them trying to find a fix). They game would also heavily act up if I ever left the game to do anything on my 2nd monitor.

I had heard that Nvidia cards have some vram usage issues when doing multi-displays. So I finally had the bright idea after trying many other fixes to actually unplug my 2nd monitor from card #1 and plug it into card#2 and “activate all monitors” in the Nvidia control panel.

Ever since I have made this change my card usage is below 10% while playing on high graphics settings and I don’t straight up crash after about 30 mins to an hour of gameplay.

1 Like

A possible fix that worked for me was changing my router settings to change the default DNS server to Cloudflare 1.1.1.1 and secondary to Google 8.8.8.8. After this I rebooted the modem and router.

This helps but is not perfect, it just made the rubber banding about 1/3rd as bad.

Hello,
This is an issue with how Diablo 4 cloud servers are setup unfortunately. I don’t know where you are connecting from but let me give you a sample.

I am connecting from Hong Kong and D4(Google) servers are hosted there, Taiwan, Japan and Korea. When I load into a zone and get connected to a Hong Kong server, happy days no lag. Now when I load into another zone, D4 can put me in other far servers like Korea or Japan, then it gets really laggy and unplayable.

I don’t know who in the right state of mind would design it that way and consider any anyone in Southeast Asia to connect to any server without the player having a choice of connecting to the nearest server.

Assumming your connection to your ISP isn’t broken, I don’t think Blizzard cares to fix any of this. The best way to make it playable on your end is to use a VPN service with 2 things to try.

  1. Connect to the nearest game server that you know. I am not sure if they are also using Google cloud servers in your region. The problem with this is that you can still get loaded into any server in your cluster even though the lowest ping/latency is the nearest game server.
  2. Connect to the game server that is in the middle of your cluster. In my case, if I was playing from the Philippines, I would connect to Taiwan so that my average ping/latency would be better in average as I can be thrown into either Hong Kong, Japan, Korea servers - this way, the worst server blizz throws me into isn’t so horrible. This is unfortunately where my game servers are for my region.

I think you also get put into a server cluster consisting of different states/countries near each other depending on your region and the game randomly puts you into any of the servers in your cluster.

GL HF!

Note: I just used “cluster” for discussion’s sake. I don’t know if that is correct term at all.

1 Like

How has this thread been going on for 3 weeks and not a single answer from Bliz? This is a pretty fundamental issue with your product.

1 Like

I got annoyed enough with not being able to get to the bottom of the issue to tinker with Diablo IV on my macbook and it now runs flawlessly, so I guess the fix is… get a macbook? :laughing:

Wait so it runs laggy and perfect on same connection with two different hardware set up? Makes no sense…

It does if one machine has some issues. But no one will admit to that being possible so it must be Blizzard’s fault entirely.

And I get it. But still.

Me on other hand, I cannot get a problem to manifest. I even built a second gaming system two days ago. AMD based, with a 2070. Even cranked the settings to max and what not. Other than the system not liking Ultra in general performance wise, it was still consistently running the game ok for over an hour.

But I have more things to try to break that system. Will see if I can manage to re-create some of these problems.

1 Like

In my sistuation,I do know I have an unstable connection (high speed but low signal, so unstable). It’s a rental house with internet included and I’m moving out soon thank God, so currently I take some latency issues for granted. However, it is very frustrating to die on the boss of a dungeon, being disconnected and coming back to town. Now I have to start the same dungeon from scratch. That’s just keyboard-smashingly frustrating.

1 Like

So the other day, I tried NORDVPN. It made things worse if anything, and I paused the VPN connection and it got stuck and I uninstalled in frustration. A weird message about AVG Anti Virus scanning connection came up and Ive never seen that before. I logged onto D4 again with MTR and it was perfect 40-50 ping, at 7pm peak EU time… and it gets weirder, it seemed to suggest I had 1% loss on one of the ip address. But man it all ran smooth as butter. I played for over an hour. Next time I logged on, back to rubberband, 30-1200 ping.

Tried turning off all of AVG Anti Virus, firewall even (stupid thing to do I know!), but it still has the lag issue. Is it possible using VPN,connection getting stuck and reloading normal connection did something weird to make it work that one time?

I also got someone to reply to me on a server and he confirmed he was EU based. So my theory about being put on wrong region server is doubtful.

You’re going to get a lot of “its your connection, I’m fine” replies, but this is also happening to me and everyone I know playing this game. You aren’t alone. Blizzard won’t acknowledge it, bad press.

3 Likes

Yeah I mean they got off almost scot-free from that abuse lawsuit, so why care about a “small” issue like this. If they can say “nah didnt happen” they can ignore this.

1 Like

Those replies kill be every time like “oh it’s not happening to me so it doesn’t exist or it’s your ISP” :joy:

3 Likes

I’ve said this in plenty of other post and create a reddit post as well. The only solution that has worked for me is using my hotspot internet purposely for this game. I have no idea why it works, but it just does. This is coming from someone who has tried playing on PC as well as console (Xbox Series X & PS5)

1 Like

While I get your point. A few of these HAVE turned out to be exactly that. Not all. But some have.

Point being, there are a LOT of variables.

This means your normal ISP hates the D4 traffic. Something that I think is at the root of the issue. This does not mean there isn’t something wrong with how the D4 traffic is operating and potentially causing the issue.

I mean, one user even found when they turned off their DDOS protection in their modem, it started working just fine after that.

So far, I haven’t seen any posts from users on Centurylink/Brightspeed (DSL), nor anyone using Starlink, having these problems. (I have both, and both work just fine with this game)

1 Like

interesting my ISP is Verizon Fios

Just as bad on my Verizon hotspot as it is on AT&T 1gig fiber. Both Xbox and PC. So no your fix isn’t a fix for the broken networking.

Literally unplayable last 36 hours.

2 Likes