Unreal Engine 5 has made “shader stutter” a catch-all phrase. It is not one bug. Phantom Blade Zero can stall because it is compiling a pipeline for a new effect, because the storage path cannot feed the streaming pool, or because the frame is waiting on a CPU-side asset callback. The fixes are different, and only one of them is improved by clearing a cache.
This file uses the 1.0.4 shader-pipeline hotfix as its test context. If your game build moved after that, treat exact menu labels as approximate and verify the log timestamps before you edit files.
The clean-slate method for a stutter report
One route, three runsBefore changing any config, create a repeatable measurement:
- Use the same save, the same route, and the same graphics preset.
- Run once to compile, quit, relaunch, and run the route again.
- Capture frame times with PresentMon. First-run and second-run charts should be different.
- If the second run is smooth at the same location, the first stall was compilation or disk.
Identify the stall from its timing
A one-time shader compilation hitch often happens the first time an attack effect, boss phase, or new material appears. It can present as a single 200–600 ms freeze and then never recur on the same route. Traversal stutter repeats more consistently and often correlates with camera movement into a new zone.
Open the game’s config and log folder and check whether a pipeline cache file is actually growing between runs. If it is not, clearing it will do nothing.
[SystemSettings]
; Conservative baseline for a 12 GB GPU at 1440p.
r.Streaming.PoolSize=7424
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
r.Streaming.HLODStrategy=2
r.Upscale.Quality=2
; Leave PSO precaching enabled unless the developer documents otherwise.
r.PSOPrecaching=1
t.MaxFPS=0 The config is not a magic wand
Unreal’s .ini chain is layered. A value in Engine.ini can be overridden by GameUserSettings.ini, a device profile, or a cooked scalability entry. That is why some players report “the setting does nothing.” If a value does not survive a game restart, it is not in the effective chain.
The baseline above deliberately caps the streaming pool below the VRAM limit. On a 16 GB card, 7.4 GB is conservative; on an 8 GB card it is close to the practical ceiling. Larger is not automatically better. The pool needs to leave memory for render targets, shadow maps, and pipeline state.
Built locally in your browser. Nothing is uploaded.
; GamePathHub // Phantom Blade Zero ; Engine: Unreal Engine 5 | GPU class: 12 GB | Target: 120 FPS ; Upscaler: DLSS Quality ; Change one group at a time. Back up the original file first. [SystemSettings] r.Streaming.PoolSize=7552 r.Streaming.LimitPoolSizeToVRAM=1 r.Streaming.MaxTempMemoryAllowed=1359 r.Streaming.HLODStrategy=2 r.Upscale.Quality=2 r.MaxAnisotropy=8 t.MaxFPS=120 r.VSync=0
What the verification runs looked like
The numbers below compare a repeatable exterior traversal route on the bench. The point is the 1% low, not the highlighted average. A 120 FPS average with a 54 FPS low feels worse than a locked 90 with a 79 low.
Black: average / Blue: 1% low
Bench capture after 1.0.4, same save and route. Configuration notes: High preset, DLSS Quality, motion blur off. Not a hardware leaderboard.
If your own third-run result still shows a 40 FPS low, keep investigating. The fix stack below is ordered from least invasive to most invasive.
Shader stutter isolation sequence
0 / 7 completeStorage and VRAM quietly decide the outcome
Phantom Blade Zero’s fast weapon effects and detailed environments create bursty asset demand. A GPU with 12 GB or more is not a luxury at 1440p high; it is headroom against a sharp hitch. An 8 GB card can still play well with high (not ultra) textures and a conservative pool.
The rule that survives patches
Do not stack a cache deletion, an .ini pack, a driver rollback, and a new Windows build in one evening. You will not know which one worked, and you will not know which one to remove when the next patch arrives. Keep a copy of the original file. Change one group. Measure the same route twice. That is the whole method.
Did this fix work on Patch 1.0.4 — shader pipeline hotfix?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 1.0.4 — shader pipeline hotfix. Votes are local-only telemetry.
Phantom Blade Zero: bench questions
3 answersWhy does Phantom Blade Zero stutter at the same spot every time?
Should I delete the shader cache before every session?
Does a higher streaming pool always reduce stutter?
FPS & Stuttering
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.
Phantom Blade Zero: Shader Stutter, Frame Pacing & Unreal Engine 5 Config Tuning
A measured stutter-hunting routine for Phantom Blade Zero: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unreal Engine 5 settings file to edit.
Phantom Blade Zero: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Phantom Blade Zero without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.
Phantom Blade Zero: Controller, DualSense & Raw Mouse Input Latency Fixes
Fix Phantom Blade Zero input lag, deadzones, DualSense/FFB detection, and raw mouse polling for a clean competitive or simulation control path on Unreal Engine 5.