I’ve benchmarked SoA on a couple of systems, I’ve collected logs from Radeon GPU Profiler and there is likely a clear reason why this dungeon after 9.0.5 has low FPS for some users.
So for RX 460 4GB and 1050Ti the FPS will be quite low while for stronger GPUs like even GTX 1070 at 1080p or RTX 3070 at 3440x1440 it will be lower than before but still “overkill” in most cases.
RX 460 4GB + i5-9400F average FPS at the entrance:
SoA: 37,6 FPS
HoA: 43,1 FPS
ToP: 52,6 FPS
Necrotic Wake: 84,7 FPS
De Other Side: 120 FPS
If you collect data with Radeon GPU Profiler the amount of GPU events per frame is similar, amount of shaded vertices is similar… but when you compare amount of shaded pixels per frame then SoA is top at 125 million pixels (121 million for Ardenweald test spot, 60 million for Theater and 29 million for Necrotic Wake).
It looks like SoA compared to other dungeons shades way more pixels thus lower performance, way lower for iGPU/dGPU with low pixel fill rate/VRAM bandwidth.
Similar bug was in Rustbolt in BfA when after a hotfix the FPS dropped noticeably and the profiler also showed vastly more pixels shaded.
They cannot do that for the simple fact that this issue happens both on very high end specs as well as very low specs.
They have to address this issue because it’s ridiculous, especially in arenas (there’s a bastion-themed arena map with the same issue) and in M+ where FPS can affect the quality of gameplay by a lot, especially on high keys where you need to be very precise.
What do you mean I bump threads for the sake of bumping them ? It’s a huge issue that affects a lot of people and to which we get no answer so the thread goes down in the dust bin. I’m not going to let the thread fade into obscurity, I want this issue addressed. If you have a problem with it, then tough luck.
I can’t believe it’s been months and still no fix or even a word from Blizzard. And yet they have the resources to re-record old VA lines from 6 expansions earlier for no good reason. Shameful.
nope, as it shows up even at mode 1. What some did was to switch to DX11 legacy when like looking at SoA exist, then back to DX12 and it could temporary “fix” it.
Jira says they seen it, but likely they can’t fix it that easily