Constantly Rubberbanding and Disconnecting on PC

Well, other than a latency above 100ms, that test shows no loss at all. So according to that, you look good there.

1 Like

So that’s unfortunate. The rubberbanding on the one from 6/17 is, arguably, worse than the one from 6/16. The latency in-game is definitely a worse baseline as well: consistently > 500ms. Back to the drawing board.

Well, that means the problem may be further up.

At this point I can’t really rule anything out, even the server themselves causing some of the issue. I have some tests that showed definitive issues, but others that I thought I was certain about, after doing research I’m not as sure about now.

So I’m trying to be careful in analyzing these.

1 Like

Same problem, unplayable until i relog again and again

2 Likes

Blizzards server sucks, its that simple.
Only game causing issues are diablo4, i can run CS, Warframe, valheim, lol. dota2, Warhammer, etc etc with NO issues at all.
Its totally unplayable.

5 Likes

Just adding to this thread. On the first day of playing everything was seamless, I just had to wait 4-6 minutes to login. Ever since the server maintenance no queue times but constant rubber banding, several clashes and latency hovering in the hundreds of ms, sometimes up to 3000ms! Tried a myriad of fixes but nothing really helped significantly.

I am trying to play on PC in Singapore, connected to America servers (which where we supposed to connect according to blizzard). It is basically unplayable in the current state.

5 Likes

Just jumping on the bandwagon here, constant dc issues after every conceivable fix. It’s frustrating to spend a boatload of money for a product that doesn’t work. I hope blizzard comes up with a fix soon, bringing more servers online, whatever. Just yet another ding to a once amazing company.

5 Likes

Too little money spent on servers and too much on that island…

2 Likes

My girlfriend is getting these random disconnects while I don’t.

There are no issues in other games, and the net works fine. :expressionless:

2 Likes

Just curious if she plays on weaker hardware or another platform? The only thing Blizzard said (in the latest campfire chat) was about working on performance issues for the next big patch that might affect lag and disconnects. I’m hoping your case implies that’s the main reason for these issues if she has different hardware, and we might get a fix soon.

2 Likes

Absolutely UNPLAYABLE. the very definition of unplayable. I know those words get exaggerated but ive spent the whole morning in absolute disgust at this pile of crap. 70 quid for a game thats rubber banding so hard every second. It never goes away. They should be issuing everyone with refunds.

Im AM FURIOUS. about this. Its been like it from the start and the only time it let me play without unplayable lag is in early hours and times when millions are in bed lol

My first diablo game too. Ps5. F##k this game.

2 Likes

It is identical to my computer, so it is odd, but I read on the tech help forum, that the game has been very unstable today for some reason.

2 Likes

yeah stop playing and let as many people know that Blizz got their money and wont address a huge issue. Corporate greed…

3 Likes

Disconnects every 5 mins on average Fri/Sat/Sun. Have not yet made it through a cut scene. Often cannot make it to the next teleport point. This is ridiculous and surely must be Blizzard’s server code.
400MB down/200MB up fibre connection. Running across ethernet cables and not wifi.
Latency to server usually under 37ms.
And this is with just me using the connection and just for D4 at the time of disconnects.

2 Likes

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.