There is absolutely no reason when you enter a portal from town, you come right back out in town again. Sometimes it takes up to 4 tries to finally go back.
There is no reason this should even be happening
FIX this!
Hmm, I’ve never seen this… At least not regularly enough to remember it, or dismiss it as a mis-click on my part.
AMD Ryzen 9 5950x
32GB DDR4
1TB NVMe SSD
4070Ti
Extremely stable connection.
I can only assume that you’re dealing with packet loss, which there isn’t much that Blizzard can do about. Diablo 2 has always had trouble with any amount of packet loss.
This is a known issue with people speculating on the cause but this is something Blizzard can fix:
I should have put my specs so here they are:
This is an all Straight DDR5 all black build (No RGB)
Asus z690 Plus wifi D5
i9 13900k
RTX 3090ti (FE)
32gb (16x2) Kingston Fury silver DDR5 @6400\ MT/s
Upgrading to Kingston Fury Beast 64gb (32x2) @6400 MT/s in the nest 4 days
Arctic Liquid Freezer III AIO 360
1 TB nvme 4.0
Samsung Odyssey G7 28" 144hz 4k monitor
My CONNECTION is real a fiber optic connection not this Cox/Comcast/Verizon coax they called fiber. I mean the the buried in the ground with glass in the wire fiber optic
You play only by yourself iirc?! Try Baalruns, it happens there sometimes.
Yesterday, I was plaing by myself and I had it happen at least three times when I wanted to go back to Bloody Foothills from Harrogath. So even solo isn’t 100% safe, although that was the first time it happened to me playing by myslef that I actually remember.
It’s just typical desync and it doesn’t matter what PC you have. Especially not your cooling system or monitor…
never had this happen in 20 years, sorry im not with this issue.
The way the game works (especially now as that changed with the move to Battle.net 2.0 for D2R), I’m leaning more toward it’s an issue where the instance has either become corrupted or the ID was munged or is now occupied by another actual instance with the same ID. In WoW you could force the instance ID for raids to bug in vanilla, but it may just be a byproduct of somewhat older baseline netcode with D2/D2R. Thankfully the netcode did get some upgrades for D2R, as noted by less frequent rubberbanding when making tight turns or getting caught on terrain corners repeatedly.
A desync wouldn’t send you back to down like that - it’d just flat out DC you. This is closer to how the “instance transfer aborted” scenario works, only without the long timeout wait.
Regardless of the reason, it’s annoying!
as I left 2 links to topics that are at least 2 years old so this isn’t anything new