Black Myth: Wukong PC Stutter Explained: Why Unreal Engine 5 Hitches and How DLSS and Frame Generation Actually Help

Short answer: If Black Myth: Wukong feels smooth at 70 fps and then freezes for half a second when you enter a new area or start a boss transformation, you are not seeing weak hardware. You are seeing three different hitches stacked together: shader compilation, world streaming, and a CPU-limited pipeline. DLSS Super Resolution fixes low average fps. Frame Generation hides low fps. Neither fixes hitches by itself. Fix hitches first, then add upscaling.

This guide is for the Windows PC version of Black Myth: Wukong, the 2024 action RPG from Game Science built on Unreal Engine 5 and released for PlayStation 5 and Windows on August 20, 2024. It sold 20 million units in its first month. That scale matters: when millions of very different PCs hit the same UE5 features at once, the same few stutter patterns repeat.

Who this actually affects

You are in the right place if:

• Average fps looks fine in the benchmark or in a small shrine area, but you get 200-500ms freezes when sprinting, turning fast, or entering a dense forest temple
• An RTX 4070 / RX 7800 XT-class PC still stutters at 1440p even with ray tracing off
• Enabling Frame Generation doubles the fps counter but the game still feels late or rubber-banded during dodges
• First launch or first visit to a chapter takes much longer and hitches more than the second visit

If your game crashes to desktop, shows a D3D device-removed error, or never launches, stop here. That is a different failure path — update GPU drivers, verify files, and check official support. This article is about stutter, not launch crashes.

My three-toll-booth model (opinion, but useful)

Most optimization threads treat stutter as one thing. I think that is why they fail.

Think of a Wukong level as a highway with three toll booths in series:

1. The shader booth. DirectX 12 needs a Pipeline State Object for each combination of material, lighting, and geometry. The first time a new fire effect or transformation appears, the driver has to compile it. That compile happens on the CPU and blocks the frame. Result: a sharp hitch the first time something appears, then it disappears on replay.

2. The streaming booth. Unreal Engine 5 can use film-quality assets through Nanite virtualized geometry and stream large maps through World Partition, with Lumen providing dynamic global illumination and reflections that react to scene changes. That power has a cost: when you cross a chapter boundary, the engine must pull geometry, textures, and lighting data from SSD into memory while you are still moving. If the SSD is slow, full, or the shader cache was just cleared, you get traversal hitches — regular micro-freezes every few seconds while moving.

3. The decision booth. Even if the GPU is fast, the CPU must prepare draw calls, physics with Chaos, particles with Niagara, and game logic. At 60+ fps in a boss fight with many spirits and transformations active, the CPU can become the limiter. Upscaling does not help here. Frame Generation makes it look smoother while making input slightly later, which feels terrible for Soulslike-style perfect dodges.

Why does this mental model help? Because each booth needs a different fix. Raising DLSS from Quality to Performance only widens the highway after the booths. It does not remove the booths.

Is this rigorous? No. Epic has not published a Wukong-specific PSO breakdown, and Game Science does not expose its streaming budget. Treat this as a diagnostic lens, not a leaked internal diagram. But it predicts what players actually report: first-run hitches, traversal hitches, and boss-fight input lag are three different complaints.

What each technology actually does

DLSS Super Resolution: renders low, reconstructs high

According to NVIDIA, DLSS Super Resolution boosts performance by outputting higher-resolution frames from a lower-resolution input, using motion data and feedback from prior frames plus a second-generation Transformer model for stability and anti-aliasing. In practice:

• Quality mode at 1440p renders around 67 percent of pixels and reconstructs the rest
• It helps when you are GPU-bound: dense foliage, Lumen lighting, high shadows
• It does not pre-compile shaders or preload the next valley. If your 1 percent lows are caused by compilation, DLSS raises average fps while the hitches remain

Use it as a GPU reliever, not a stutter cure.

FSR 3 upscaling and Frame Generation: open alternative

According to AMD GPUOpen, FidelityFX Super Resolution 3 combines temporal upscaling with Frame Generation through interpolation and optical flow, with Quality, Balanced, Performance, and optional Ultra Performance modes plus a Native AA mode. Key differences from DLSS:

• FSR upscaling runs on a wide range of GPUs, including competitors, and supports DirectX 12, Vulkan, and Unreal Engine 5.1 to 5.6
• FSR 3.1 separates upscaling and frame generation, so you can pair FSR Frame Generation with another upscaler
• Like DLSS, frame interpolation inserts generated frames to raise the displayed rate. AMD notes it works in GPU- and CPU-limited situations, but generated frames do not reduce the underlying simulation or compilation hitch

If you are on AMD or older NVIDIA hardware without DLSS Frame Generation, FSR is the practical path. Do not mix DLSS Super Resolution and FSR Frame Generation unless you have a clear reason and test latency carefully.

Frame Generation plus Reflex: smoother picture, later truth

NVIDIA Frame Generation uses AI to generate frames while maintaining responsiveness with NVIDIA Reflex. Reflex Low Latency reduces PC latency through synchronization across GPU and CPU.

This pairing matters in Wukong:

• Frame Generation roughly doubles displayed fps, but the game simulation still runs at the base rate. A 45 fps base becomes about 90 displayed fps, not 90 real game updates
• Without Reflex, that gap feels like input delay on staff spins and Rock Solid parries
• NVIDIA explicitly ties Frame Generation to Reflex for this reason. Always enable Reflex Low Latency when you enable Frame Generation
• My rule: do not enable Frame Generation below about 55-60 fps base. Below that, artifacts and latency outweigh the smoothness. Fix settings until base fps is stable, then add generation as polish

Practical fix order that works

Do these in order. Do not jump to step 5 first.

Step 1: Establish a baseline with the benchmark tool

Run the free Black Myth: Wukong Benchmark Tool from Steam on the same drive and settings you play on. Note average fps and 1 percent lows. If average is 75 but 1 percent is 22, you have a hitch problem, not an average-fps problem. Re-test after each change.

Step 2: Let shaders settle and keep the cache

• On first launch after a driver or game update, stay in the starting area for 5-10 minutes or run the benchmark once. First-run compilation hitches are expected on DirectX 12 UE5 games
• Do not clear the shader cache or reinstall drivers daily. Repeated clearing forces recompilation
• Put the game on an NVMe SSD with at least 20 percent free space. A SATA HDD turns every World Partition stream into a hitch

Step 3: Update the narrow things first

• Update GPU driver through NVIDIA App or AMD Software, not Windows Update alone
• Set Windows power to Best Performance, disable background recording (Xbox Game Bar, Discord overlay, browser with hardware acceleration) for the test run
• Use fullscreen or borderless consistently. Switching modes can reset Reflex and VRR behavior

Step 4: Cut the heaviest UE5 costs before touching upscaling

In order of fps-per-visual-loss in Wukong on most PCs:

1. Ray tracing / Full Ray Tracing: off first for stutter testing. Lumen already provides dynamic global illumination without full path tracing cost
2. Shadows: High instead of Cinematic. Virtual Shadow Maps at Cinematic are brutal during forest fights
3. Post-processing / Motion blur: lower if traversal feels smeary with Frame Generation
4. View distance / Foliage density: one notch down in Chapters 1-2 if traversal hitches dominate

Retest. If 1 percent lows are now within 70 percent of average, you fixed the streaming and GPU-bound part.

Step 5: Add upscaling correctly

• RTX 20-series and newer: DLSS Super Resolution Quality at 1440p, Balanced at 4K. Try DLAA only if you already exceed your monitor refresh rate at native
• Other GPUs: FSR Quality mode. Avoid Ultra Performance unless you play on a small screen at 4K and accept softness
• Sharpness: leave at default. Over-sharpening plus upscaling creates shimmer on fur and foliage that many players mistake for more stutter

Step 6: Add Frame Generation only at the end

• Enable only after base fps is stable above about 60
• Enable Reflex Low Latency at the same time
• Cap displayed fps 2-3 below monitor refresh rate (for example 141 for 144Hz) to keep VRR engaged and avoid runaway latency
• If dodges feel floaty, turn Frame Generation off and keep Super Resolution on. A responsive 65 fps beats a late-feeling 110 fps in a Soulslike

Expected confirmation: second run through the same path shows fewer long frames in PresentMon, CapFrameX, or NVIDIA overlay, 1 percent lows rise, and input feels connected. If average rises but 1 percent stays flat, you improved GPU load but not hitches — go back to Steps 2-4.

When to stop tuning and ask for help

Stop and seek official support if you see corrupted textures, persistent device-hung errors, audio that desyncs by seconds, or hitches that worsen over 30 minutes (possible memory leak or overheating). Include GPU model, driver version, SSD model and free space, resolution, DLSS/FSR mode, and whether the benchmark tool reproduces it. That information separates a local thermal issue from a game bug.

Open questions I keep thinking about

Here is where I diverge from copy-paste guides:

Are we measuring the wrong thing? Stores sell average fps. Bosses are won on 1 percent lows and input latency. If reviewers led with Chapter 3 traversal 1 percent lows instead of 4K Ultra average, would players buy more appropriate GPUs and complain less?

Is stutter the price of photogrammetry? Nanite lets artists import film-quality scanned temples directly without hand-optimizing every LOD. That is why Wukong looks unlike any low-budget Soulslike. But it shifts optimization from artists to your SSD and shader cache. Do we as players actually prefer denser temples with occasional hitches over simpler arenas with locked 120 fps? I am not sure the community has answered honestly.

Should UE5 games ship a visible Compile Shaders button? Some UE5 titles now pre-compile on first boot with a progress bar. A 10-minute upfront compile is boring but legible. Hidden hitches feel like broken hardware. Which is better design?

Will Frame Generation hide the problem until path tracing makes it worse? DLSS Multi Frame Generation can generate up to five frames per rendered frame on RTX 50-series. That is spectacular for benchmarks. But if base simulation still hitches on traversal, we get beautifully interpolated hitches. At what point does smoothing become misdirection?

If you test this guide, compare the same 60-second run twice — once with only DLSS Quality, once with DLSS Quality plus Frame Generation plus Reflex — and watch 1 percent lows, not just the big number. I suspect many DLSS fixed my stutter posts actually fixed GPU load and left shader hitches untouched. Prove me wrong with data.

FAQ

Does Wukong use Unreal Engine 5? Yes. Game Science built Black Myth: Wukong on Unreal Engine 5, which provides Nanite virtualized geometry and Lumen dynamic global illumination, among other systems.

Should I use DLSS or FSR in Wukong? On RTX GPUs, start with DLSS Super Resolution because NVIDIA trains its Transformer model specifically for temporal stability. On non-RTX GPUs, use FSR. Do not enable both upscalers at once.

Does Frame Generation reduce input lag? No. It increases displayed smoothness. Pair it with Reflex Low Latency and only when base fps is already solid, otherwise latency gets worse.

Will lowering resolution fix traversal stutter? Only if you are GPU-bound. If hitches happen at the same world positions regardless of resolution, suspect shader compilation or SSD streaming, not pixel count.

Sources

Game background, engine, release date, and sales context verified against encyclopedic summary with primary citations; engine and release facts cross-checked on August 20, 2024 Windows and PS5 launch and Unreal Engine 5 basis. UE5 Nanite, Lumen, World Partition, and Virtual Shadow Maps behavior summarized from engine overview. DLSS Super Resolution, Frame Generation, Ray Reconstruction, and Reflex behavior from official NVIDIA pages. FSR 3 upscaling modes, frame interpolation, and UE5 support range from official AMD GPUOpen docs.