3.22.1d dramatically decreased performance in DX12/Vulkan (resolved by itself?)

Hi,

Ever since the introduction of DX12 and Vulkan, my FPS has been great using either of them, often sitting steady at 120+ with only slight jumps in intense combat, and slightly lower numbers in very messy scenes (ie, very juiced t16 maps).

However, patch 3.22.1d made it so that I cannot go above 71~ish FPS using DX12, and I get 10 less FPS using Vulkan.

DX11 seems to have improved to a point where it gets me 144 FPS in both my hideout and in combat, which is more than before, but it somehow doesn't feel as smooth as DX12 did, perhaps because it gotta cache everything again? Still, it's playable with DX11, but DX12 and Vulkan are thoroughly and firmly seated in the trash bin for me as of now.


Windows 10
Computer specs: i9-10900k, 2080Ti, 32GB RAM.
Game Settings: Triple Buffering OFF, Multithreading ON, VSync OFF, Dynamic Culling ON, Dynamic Resolution OFF, foreground FPS 154, background 15, mostly low graphic settings. Changing any of the above settings did nothing to improve the situation.

I tried taking off all my MTX, and nothing resulted in any notable improvements to my FPS. I've tried restarting the game multiple times, and I've tried turning off background applications, but no dice there either.

I also checked my Nvidia settings for the game, and nothing looks out of place, and as far as I can tell, nothing have changed either. All my settings outside of the game are as they always have been, and PoE worked as well as it always has- even as recently as 12 hours ago. This morning, as of this patch, 3.22.1d, PoE no longer feels playable due to much worsened FPS using either DX12 or Vulkan.


A quick screenshot of the game now running with DX11. Let me know if you need a similar graph of DX12 or Vulkan.

A day later I log in again, feeling hopeful, and I try changing my renderer back to DX12. My problem suddenly appears to be resolved, as if by magic?

Restarting and changing settings did nothing, but a day later it's as if the problem was never there to begin with.

I guess this is resolved now. Thanks.