On this page
Player impact in 30 seconds
0.5.4e improves Shader loading and reduces Shader size, disables the Steam Vulkan Fossilize layer, and changes the default VSync to Capped.
A slower first load after the patch is expected because Shaders recompile; do not judge final performance from the first entry alone.
This page never claims 'stutter fully fixed'. Renderer, platform and first-vs-repeat run must be separated.
Where 0.5.4e sits in the family
Content baseline that 0.5.4e technically follows.
atlasitemsbossesOath Rune fix; separate from the 0.5.4e technical changes.
expeditionfixShader loading, Vulkan cache and VSync default changes on this page.
shadersvulkanperformance
Impact dashboard
First load
Expect a slower first entryShaders recompile after the patch. This is normal and distinct from a true performance regression.
Steam + Vulkan
Fossilize layer disabledTargets the Shader Cache sometimes ballooning. Does not apply to DX12 or Standalone the same way.
VSync
Default now CappedAdaptive is no longer recommended because of frame-pacing issues.
Community
Results are not uniformSome players report smoother maps, others still report crashes or scene stutter. No single universal claim.
Official changes, reorganised by player problem
Shader loading improved and size reduced
First entry may recompile Shaders; later entries are faster. Judge by repeat run, not first run.
Steam Vulkan Fossilize layer disabled
Aims at Shader Cache abnormal growth. Specific to Steam + Vulkan; do not attribute to DX12.
Default VSync changed to Capped
Adaptive is dropped because of frame-pacing issues.
Residual crash / stutter cases
Some reports persist; they are not yet confirmed as fully resolved and stay in Known Issues.
First run vs repeat run
Technical environment matrix
steam-vulkan
Check first Shader recompile, Steam Shader Cache size and Vulkan stability. Do not borrow DX12 or Console conclusions.
steam-dx12
Separate first compile from later loads. The Fossilize change targets Steam + Vulkan, not DX12 directly.
standalone
Standalone does not use the Steam Fossilize layer. Check renderer, drivers, cache directory and behaviour after repeated entry.
console
Official 0.5.4e notes describe Shader and Vulkan/Steam behaviour. Console reports must be recorded separately, not merged with PC.
Affected content queue
| Content | Type | Trigger | Action | Status |
|---|---|---|---|---|
| Performance Troubleshooting Guide | Guide | 0.5.4e | Add first-run vs repeat-run section | Reviewing |
| Shader Cache FAQ | Guide | 0.5.4e | Document Fossilize disable | Queued |
| Vulkan Setup Guide | Guide | 0.5.4e | Note VSync default change | Queued |
Community evidence
Shader count dropped noticeably, but results still vary by hardware.
Some still crash or stutter in specific scenes after the patch.
Video and timestamps
Official Path of Exile 2
0.5.4e Shader and performance explained
Official explanation of Shader recompile, Vulkan cache and VSync default.
What to watch for: Watch the first-run vs repeat-run segment before drawing conclusions.
Open source ↗Direct answers
Why is the first load slower after 0.5.4e?
Officially, Shaders are recompiled, so the first area entry can be slower.
Judge the effect by separating first entry from repeat entries.
Did 0.5.4e fix all stutter?
No universal claim is supported. Some players report smoother maps, others still report crashes or scene stutter.
Renderer, platform and run type must be separated before any conclusion.
Known issues
- OpenResidual crashes or scene-specific stutter reported after 0.5.4e; not yet confirmed fully resolved.
- TrackingConsole-specific shader reports tracked separately from PC conclusions.
Sources and verification
Official source for Shader, Vulkan and VSync changes.
Changelog
- Published the 0.5.4e Shader and performance rich article.
Information is compiled from public web sources and in-game observations; some visuals are original editorial diagrams. External information and images remain the property of their authors or platforms; contact us for removal requests.