FPS & Stuttering / Path of Exile 2 / Proprietary Engine

Path of Exile 2: Shader Cache, Vulkan, and DX12 in the Endgame

How to stabilise Path of Exile 2's endgame frame time by separating shader compilation, renderer choice, and network effects.

Official Steam Store header artwork for Path of Exile 2.

Path of Exile 2 is a live-service ARPG, which means “stutter” can originate in four places: your CPU, your GPU and its shader cache, the game server, or the network path between them. Endgame juiced maps combine all four. A benchmark in the hideout tells you almost nothing about the experience.

This file uses the 0.5.0b patch as its baseline. The method is more durable than the exact numbers: make one change, test the same map layout, and separate local frame time from server or network lag.

The endgame stutter split

Local vs server
  • Does the frame-time graph spike while the game is still rendering? That is local.
  • Does the screen freeze while the network indicator spikes? That is connection or server.
  • Does the hitch happen only the first time a monster ability appears? That is shader compilation.
  • Test with a fixed map layout and a low-density first run to create a baseline.

Renderer choice is hardware-specific

Vulkan and DX12 are both first-class paths in the current build. On the bench, Vulkan had the better 1% low in dense maps, especially after 0.5.0b’s cache changes. DX12 was more resilient to alt-tab and multi-monitor transitions. That is a trade-off, not a winner.

Path of Exile 2 / endgame map frame-time check
Scale 0–150 FPS
Black: average / Blue: 1% low
DX12 / first run after launch 118 FPS / 54 low
DX12 / third run 121 FPS / 82 low
Vulkan / first run after launch 116 FPS / 61 low
Vulkan / third run 120 FPS / 91 low

Bench: i9-13900K / RTX 4080 SUPER / 1440p / quality preset. Three runs per renderer on a repeatable tier-16 map. The map was not fully juiced; these are not worst-case numbers.

The first-run data matter because the first map after a patch is not representative. If you judge a renderer after one play session, you are mostly measuring cache warming.

The config file

Path of Exile 2 stores renderer and quality choices in a local config. The game may rewrite it when you change a menu setting, so close the client first, copy the file, and make one edit.

%USERPROFILE%\Documents\My Games\Path of Exile 2\production_Config.ini
[DISPLAY]
renderer=vulkan
resolution_width=2560
resolution_height=1440
fullscreen=0
vsync=0
fps_limit=141

[GRAPHICS]
texture_quality=3
antialiasing=2
screen_shake=0
; Key names and accepted values vary by build.
; Confirm after launch; the game may rewrite this file.
A 141 FPS cap on a 144 Hz display leaves a small buffer for frame-time spikes. If the graph still overshoots, lower the cap to the 1% low rather than adding more config lines.
Config builder / Path of Exile 2 Custom

Built locally in your browser. Nothing is uploaded.

Game config directory
; GamePathHub // Path of Exile 2
; Engine: Custom | GPU class: 12 GB | Target: 144 FPS
; Upscaler: DLSS Quality
; Change one group at a time. Back up the original file first.
# Generic engine baseline
# USE WITH CAUTION: the game may not read these keys.
[Graphics]
TargetFrameRate=144
VSync=0
Upscaler=DLSS Quality
TexturePoolMB=7552
ShaderCacheMB=15104
Custom engines require title-specific keys. Confirm the key names in the game files before saving changes.

The generator’s generic profile is intentionally cautious for a custom engine. Do not copy every key into the game file; treat it as a planning note and verify against what the game actually reads.

Shader cache: corrupt once, not every session

If the client crashes on a specific zone transition and the crash repeats after a clean driver install, the pipeline cache may be corrupted. Back it up, remove only the documented cache folder, and let the game rebuild it. Do not clear it before every session.

The same rule applies to GPU driver “cache cleaners.” They are not maintenance. They are a troubleshooting step with a measurable cost.

PoE2 endgame frame-time isolation

0 / 7 complete

The network qualifier

A live ARPG cannot be benchmarked like a single-player game. If your character teleports, the server is late even though your GPU is fine. Test with a local or low-latency gateway, avoid a VPN, and stop background updates. If other players report the same lag in the same area at the same time, your config is not the problem.

The conservative recommendation

Start with Vulkan, a 141 FPS cap on a 144 Hz display, texture quality high rather than maximum, and one full session before you judge. If alt-tab reliability matters more to you than the dense-map 1% low, DX12 is a defensible choice. Do not chase a renderer victory based on the hideout average. Endgame is the test.

Did this fix work on Patch 0.5.0b — shader cache and Vulkan stability?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 0.5.0b — shader cache and Vulkan stability. Votes are local-only telemetry.

Path of Exile 2: bench questions

3 answers
Should I use Vulkan or DirectX 12 in Path of Exile 2?
Test both on your own GPU. On the GamePathHub bench, Vulkan had steadier frame times in dense endgame maps after 0.5.0b, while DX12 recovered from alt-tab more reliably. Neither is universally faster.
Why does the first map of a session stutter?
New effects and monster abilities compile pipelines on first encounter. That is shader compilation. A repeatable hitch in the same map after several runs is more likely asset streaming, server effects, or a network spike.
Can I delete the shader cache to fix a crash?
Only when the cache is corrupted or a driver/game update invalidated it. Repeatedly deleting the cache forces recompilation and makes the first hour worse. Back it up and do it once.
Filed under

FPS & Stuttering

Patch tested: 0.5.0b — shader cache and Vulkan stability

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.