FPS & Stuttering / Phantom Blade Zero / Unreal Engine 5

Phantom Blade Zero: Ending UE5 Shader Compilation Stutter

A patch-aware method for separating first-run shader compilation from traversal stutter in Phantom Blade Zero's Unreal Engine 5 build.

Official cover artwork for Phantom Blade Zero, featuring S-GAME, Unreal Engine 5, and Action RPG cues.

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 runs

Before 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.

%LOCALAPPDATA%\PhantomBladeZero\Saved\Config\Windows\Engine.ini
[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
Key names can be overridden by the game's own scalability files. Back up Engine.ini, change only one group, and remove the file if the game stops honouring in-game settings.

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.

Config builder / Phantom Blade Zero Unreal Engine 5

Built locally in your browser. Nothing is uploaded.

Game config directory\Engine.ini
; 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
The streaming pool is intentionally capped below the 12 GB card limit. Remove r.Streaming.PoolSize if the game already manages VRAM cleanly.

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.

Phantom Blade Zero / 1440p traversal frame-time verification
Scale 0–120 FPS
Black: average / Blue: 1% low
Default pool / first run after patch 112 FPS / 48 low
Default pool / third run 114 FPS / 71 low
Capped pool / third run 116 FPS / 83 low
Capped pool + reduced shadow quality 119 FPS / 91 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 complete

Storage 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 answers
Why does Phantom Blade Zero stutter at the same spot every time?
A repeatable stutter at the same location is usually traversal or asset streaming, not one-time shader compilation. Clear the pipeline cache and repeat the exact route twice to separate the two.
Should I delete the shader cache before every session?
No. Delete it once after a driver or game patch that invalidates the cache, then let the game rebuild it. Repeatedly clearing the cache forces compilation again and makes performance worse.
Does a higher streaming pool always reduce stutter?
No. A pool that is too large competes with the rest of the frame for VRAM. On an 8 GB card, keeping the pool below the card limit is usually more stable than maxing it out.
Filed under

FPS & Stuttering

Patch tested: 1.0.4 — shader pipeline hotfix

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.