FPS & Stuttering / Black Myth: Wukong / Unreal Engine 5

Black Myth: Wukong — UE5 Shader Stutter and Traversal Fix

A shader-cache and streaming baseline for Black Myth: Wukong on Unreal Engine 5.

Official Steam Store header artwork for Black Myth: Wukong.

Black Myth: Wukong looks spectacular partly because it streams a lot of detail. That makes the first traversal through a new area a poor performance benchmark.

Wukong — UE5 Shader Stutter and Traversal Fix

Verified field fix

The shortest safe order for this issue:

  1. Complete two full runs of the same area before treating a hitch as a permanent issue.
  2. Cull overlays and recording tools that hook the Unreal renderer.
  3. Cap the streaming pool below the VRAM limit and reduce shadow quality before textures.

Shader compile or streaming?

If the hitch is a one-time freeze when a new enemy or effect appears, it is likely pipeline compilation. If it repeats near the same cliff or temple entrance, it is streaming or CPU work. Clearing the cache helps only the first category and only after a driver change.

%LOCALAPPDATA%/b1/Saved/Config/Windows/Engine.ini
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
r.PSOPrecaching=1
t.MaxFPS=120
Back up Engine.ini. Some keys may be overridden by the game’s scalability files.

Keep VRAM for render targets

The biggest streaming pool is not always the smoothest. On a 12 GB card at 1440p, a cap around 6–7 GB leaves room for high-quality effects. Make one change, repeat the route twice, and compare the 1% low.

Field notes before you change the build

Frame time is the evidence for Black Myth: Wukong. Record the average, the 1% low, and the location of the worst spike on the same save or route. A higher average built on a 30 FPS low is not an upgrade, especially in a Unreal Engine 5 scene with heavy streaming.

Test at the same resolution, preset, upscaler, and refresh cap. If GPU utilisation falls while frame time rises, investigate CPU or streaming pressure; if memory is pinned, reduce the working set rather than adding more speculative config lines.

  • Do not compare a menu screenshot with a combat or traversal route.
  • Do not enable frame generation while measuring the native baseline.
  • Do not clear the shader cache before every session.

Check it before you keep it

Repeat the same shrine-to-boss route twice

0 / 5 complete

If the low returns

Re-test the patch and driver first, then the last two changes. Restore the stable profile rather than layering more tweaks on top of an unknown regression.

The line to keep

A repeatable route beats a benchmark fly-through. Fix the repeated hitch, not the first-run shader warm-up.

Did this fix work on Patch 1.0.14 — shader and traversal fixes?

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

Verified against 1.0.14 — shader and traversal fixes. Votes are local-only telemetry.

Black Myth: Wukong: bench questions

2 answers
Does Wukong always stutter on the first run?
New effects can compile pipelines on first encounter. Judge the second run on the same route before changing files.
Is a larger streaming pool safer on a 16 GB card?
It can help, but only if other allocations have headroom. The cap is a ceiling, not a target.
Filed under

FPS & Stuttering

Patch tested: 1.0.14 — shader and traversal fixes

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.