Here's the results. Looks shitty, but nothing crazy that would cause so much lag. Keep in mind this only started happening when Blizzard introduced that "pre-patch patch". I've been playing for over a year before that with not a single problem like this.
PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 56(84) bytes of data.
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=1 ttl=51 time=88.6 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=2 ttl=51 time=88.3 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=3 ttl=51 time=88.2 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=51 time=88.8 ms
--- xxx.xxx.xxx.xxx ping statistics ---
traceroute to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.403 ms 0.496 ms 0.525 ms
2 * * *
3 12.129.199.181 (12.129.199.181) 0.341 ms * *
4 12.129.193.253 (12.129.193.253) 0.440 ms 0.459 ms 0.566 ms
5 cr1.la2ca.ip.att.net (12.122.128.182) 51.567 ms 51.585 ms 51.592 ms
6 cr1.la2ca.ip.att.net (12.122.128.182) 51.601 ms 51.118 ms 50.350 ms
7 cr1.slkut.ip.att.net (12.122.30.29) 49.456 ms 49.470 ms 49.465 ms
8 cr2.dvmco.ip.att.net (12.122.30.26) 49.473 ms 49.486 ms 52.019 ms
9 cr1.cgcil.ip.att.net (12.122.31.86) 48.922 ms 48.946 ms 48.944 ms
10 ggr3.cgcil.ip.att.net (12.122.133.17) 100.199 ms 99.488 ms 99.487 ms
11 12.250.102.6 (12.250.102.6) 48.393 ms 48.409 ms 48.413 ms
12 199.212.160.237 (199.212.160.237) 63.736 ms 64.079 ms 64.088 ms
13 wnpgmb020xw-gr01-be2.as7122.net (104.145.12.90) 64.093 ms 64.161 ms 64.212 ms
14 * * *
15 wnpgmb1316w-ds01-165-30.dynamic.mtsallstream.net (xxx.xxx.xxx.xxx) 88.342 ms 88.849 ms 89.090 ms
I did this and it came back normal. At least I didn't see anything wrong. The weird thing is that nothing happens on the PTR, it's completely normal there. Hopefully when the patch hits, it'll fix whatever my problem is. I really need this to be fixed before Season 5 starts.
Rollback Post to RevisionRollBack
The hardest thing in this world, is to live in it.
I really don't know what else to do. I have tried everything I know to do to fix this issue. So far it's nothing with my computer, and it's only happening in Diablo. I get massive lag (Not frame lag, only rubber-banding). It's making doing anything with density practically impossible. I really need to get this fixed before Season 5 starts as I plan on going hard when the season starts. I've done everything short of reinstalling the game freshly. If I have to as a last resort I might just do a complete reinstall of windows.
Also, the replies above, I don't know what IP address I should be pinging. I put my own in and nothing seemed to be worrisome. Average pingback of 0ms. Am I doing it wrong?
Rollback Post to RevisionRollBack
The hardest thing in this world, is to live in it.
I have been playing Diablo for over a year now, and haven't had a single problem yet on my computer, but today I woke up and there was a tiny little patch. After downloading it, I tried to do some rifts and greater rifts with some friends and the game was completely lagging out and I was getting like 1200ms. The skills weren't going off when I clicked them, and I would rubber-band like crazy. I tried resetting my router, resetting my computer, and doing the "scan and repair" tool on the Blizzard Launcher, but nothing fixed it. Nothing else on my computer is lagging, so I doubt it's on my end. I didn't change anything in the settings except for lowering the graphics to see if that changed any of the lag (It didn't). I even tried playing the game with literally nothing else opened on my computer. None of these things worked. Please help!
--Quickk
Rollback Post to RevisionRollBack
The hardest thing in this world, is to live in it.
To post a comment, please login or register a new account.
I did a bunch more tests on the PTR and the rubber banding hasn't been happening at all. I hope it's the same when 2.4 comes live.
The hardest thing in this world, is to live in it.
PING xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx) 56(84) bytes of data.
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=1 ttl=51 time=88.6 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=2 ttl=51 time=88.3 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=3 ttl=51 time=88.2 ms
64 bytes from xxx.xxx.xxx.xxx: icmp_seq=4 ttl=51 time=88.8 ms
--- xxx.xxx.xxx.xxx ping statistics ---
traceroute to xxx.xxx.xxx.xxx (xxx.xxx.xxx.xxx), 15 hops max, 60 byte packets
1 Blizzard (Blizzard) 0.403 ms 0.496 ms 0.525 ms
2 * * *
3 12.129.199.181 (12.129.199.181) 0.341 ms * *
4 12.129.193.253 (12.129.193.253) 0.440 ms 0.459 ms 0.566 ms
5 cr1.la2ca.ip.att.net (12.122.128.182) 51.567 ms 51.585 ms 51.592 ms
6 cr1.la2ca.ip.att.net (12.122.128.182) 51.601 ms 51.118 ms 50.350 ms
7 cr1.slkut.ip.att.net (12.122.30.29) 49.456 ms 49.470 ms 49.465 ms
8 cr2.dvmco.ip.att.net (12.122.30.26) 49.473 ms 49.486 ms 52.019 ms
9 cr1.cgcil.ip.att.net (12.122.31.86) 48.922 ms 48.946 ms 48.944 ms
10 ggr3.cgcil.ip.att.net (12.122.133.17) 100.199 ms 99.488 ms 99.487 ms
11 12.250.102.6 (12.250.102.6) 48.393 ms 48.409 ms 48.413 ms
12 199.212.160.237 (199.212.160.237) 63.736 ms 64.079 ms 64.088 ms
13 wnpgmb020xw-gr01-be2.as7122.net (104.145.12.90) 64.093 ms 64.161 ms 64.212 ms
14 * * *
15 wnpgmb1316w-ds01-165-30.dynamic.mtsallstream.net (xxx.xxx.xxx.xxx) 88.342 ms 88.849 ms 89.090 ms
HOST: Blizzard Loss% Snt Last Avg Best Wrst StDev
1. Blizzard 0.0% 10 0.5 0.5 0.4 0.9 0.2
2. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
3. 12.129.199.181 0.0% 10 0.3 0.9 0.3 5.1 1.5
4. 12.129.193.253 0.0% 10 0.8 2.5 0.4 20.3 6.3
5. cr1.la2ca.ip.att.net 0.0% 10 50.0 50.2 48.8 51.5 1.1
6. cr1.la2ca.ip.att.net 0.0% 10 51.1 50.0 48.2 51.6 1.2[/pre]
The hardest thing in this world, is to live in it.
Yep. Just used a program that completely updated all my drivers and everything. Didn't fix the problem.
The hardest thing in this world, is to live in it.
I did this and it came back normal. At least I didn't see anything wrong. The weird thing is that nothing happens on the PTR, it's completely normal there. Hopefully when the patch hits, it'll fix whatever my problem is. I really need this to be fixed before Season 5 starts.
The hardest thing in this world, is to live in it.
I really don't know what else to do. I have tried everything I know to do to fix this issue. So far it's nothing with my computer, and it's only happening in Diablo. I get massive lag (Not frame lag, only rubber-banding). It's making doing anything with density practically impossible. I really need to get this fixed before Season 5 starts as I plan on going hard when the season starts. I've done everything short of reinstalling the game freshly. If I have to as a last resort I might just do a complete reinstall of windows.
Also, the replies above, I don't know what IP address I should be pinging. I put my own in and nothing seemed to be worrisome. Average pingback of 0ms. Am I doing it wrong?
The hardest thing in this world, is to live in it.
I have been playing Diablo for over a year now, and haven't had a single problem yet on my computer, but today I woke up and there was a tiny little patch. After downloading it, I tried to do some rifts and greater rifts with some friends and the game was completely lagging out and I was getting like 1200ms. The skills weren't going off when I clicked them, and I would rubber-band like crazy. I tried resetting my router, resetting my computer, and doing the "scan and repair" tool on the Blizzard Launcher, but nothing fixed it. Nothing else on my computer is lagging, so I doubt it's on my end. I didn't change anything in the settings except for lowering the graphics to see if that changed any of the lag (It didn't). I even tried playing the game with literally nothing else opened on my computer. None of these things worked. Please help!
--Quickk
The hardest thing in this world, is to live in it.