What it says on the tin. I’m currently in Act III (no spoilers, please 🙂) somewhere close to the end of it, if I’m guessing correctly, and I’ve been noticing the game getting more and more choppy the farther I go.
At first I just thought it was the main town, but then it happened in the enemy town/prison, then in the mountain area, then on the way to Kehjistan, each progressively worse in terms of stutters, frame drops for no apparent reason, and lag (complete with teleportation and massive input delay).
Scosglen was worse than Fractured peaks (in which I didn’t notice this problem except rare occasions). Dry Steppes is worse than Scosglen. I’m worried I’ll have to mail my input commands to Blizzard and wait for the USPS to return my results by the final acts! 😆
I can only think it must be a network condition problem, but on Blizzard’s side. I have 1Gb down and low pings, no other traffic on my network (or similar traffic during the day as when I play other games online).
My machine, an AMD 5600X with 3060ti and an NVMe drive, running at 1440p with DLSS on Balanced, hovers at 150+ fps when conditions are good.
Anyone else experiencing this sort of progressive performance degradation, or are the servers really just getting hammered that badly? Maybe someone has a remedy to try?
Anyway, loving the game, and all of this is in good spirits. Not looking to create a hate-fest in the comments. Just wondering if I’m not the only one who notices this stuff.
You must log in or register to comment.
I noticed this too, especially once you have your horse. I’d get stuck at the boundary between zones as if there was an invisible wall. Best guess is it’s just server lag and/or maintenance stuff that coincidentally lines up with when you’re later in the game and moving around the map more. I can’t imagine a technical reason why Act III would be choppier than Act I.
Yepp, central EU hast pretty bad lags. usually it starts with some laggy input transfering into litterly stutter. Game itself runs fine with stable frametimes… if you have a chance try it at a less busy time.
There’s times where I get some lag during prime time but it’s not that bad in that regard.
The game does have several performance issues though. One is a vram issue where it fills your vram no matter what. During the betas I also had the performance degrade over time (not game progress), which required a restart of the game client to get back to full performance. I heard some people still experience this, so maybe this was just fixed through Linux drivers on my end instead. There’s another issues however that is still ongoing: The game sometimes when you teleport or alt tab just degrades performance. You can usually fix this by toggling certain graphics option, like the shader quality back & forth or the smooth shadows off & on. I didn’t notice a vram difference after that so I’m not sure if it’s related to that or not but at least it is a quick momentarily fix until it happens again. Not sure if it works under Windows but I’d give it at least a try.Edit: Skip the lag comment. It’s been unplayable rubberbanding now.
My system chugged like hell in the last part of the game. Pretty much from the cinematic that you see from the trailer onwards. Don’t know what about it but it didn’t like it at.
(Ryzen 7 1700, RX5700XT, 32gb ram) How much ram do you have? Previously i was running the game on max with 16gb of ram and it was an absolute stutter fest. Noticed it was eating shitloads of ram and i was running out. Only way to fix was to close firefox and run the game on medium.
I have since acquired an additional 16gb to total 32gb of ram and i can play the game flawlessly at 100fps @ 1080p max settings even with firefox in the background. I hit about 22/32gb utilization when playing D4 on max with all my other background programs running.
You could just need more ram!
The game runs about the same in each area in the higher difficulties where mob density is the sameish everywhere. I would guess you are feeling the server lag.
The mid June Nvidia driver was also broken in Diablo. The update yesterday seems to have fixed it.
