The First Descendant Stuttering Fix: Stop Hitches and FPS Drops
Published
On this page
Most The First Descendant stuttering is Unreal Engine 5 shader compilation and its Frame Generation hitching on zone loads — not a broken PC — so the biggest wins are the latest driver, ray tracing off, a fixed Frame Generation setting, and a CPU-safe FPS cap. This guide works through the causes in order of impact, starting with the changes that fix the most hitching for the least effort.
Average FPS hides stutter. Watch the frame-time graph — a flat line at 60 feels better than a spiky average of 90.
Step 1 — Diagnose with frame time, not FPS
The FPS counter barely reacts to a single long frame, but your eyes catch it instantly. Turn on a frame-time graph and watch when the spikes land:
- Spikes when new effects, bosses or areas first appear → shader compilation. Go to Step 2.
- A hitch every time you load into a new zone or fast-travel → Frame Generation reset. Go to Step 3.
- Spikes that build the longer you play, worst at high Textures or with ray tracing → GPU/VRAM pressure. Go to Step 4.
- A jolt whenever you flick the mouse quickly → mouse polling rate. Go to Step 6.
Set up a graph with the RivaTuner Statistics Server guide or an in-game FPS overlay.
Step 2 — Update the driver and let shaders build
The First Descendant has the usual UE5 first-run hitching, and NVIDIA, AMD and Intel all ship Game Ready drivers for it. Do this before changing any in-game setting:
- Update to the latest GPU driver. If stutter started after an older driver, a clean install is safest — see how to clean install GPU drivers with DDU.
- On NVIDIA, set Shader Cache Size to 100 GB or Unlimited in NVIDIA Control Panel → Manage 3D Settings. A too-small cache re-compiles the same shaders repeatedly, which you feel as endless hitching.
- After changing any graphics setting, play 15 minutes before judging — UE5 recompiles shaders in the background whenever settings change, so the first few minutes always look worse than the real result.
If hitching persists after a driver or game update, clear the stale cache and rebuild it in one clean session — see clear shader cache to fix stuttering and the background in shader compilation stutter explained.
Step 3 — Fix the Frame Generation zone-load hitch
This is the stutter most specific to The First Descendant. Frame Generation raises the number on your counter, but the game frequently hitches whenever you load into a new area with it on, and some players have to toggle it off and back on after every zone change to keep it smooth.
- The reliable fix is to leave Frame Generation off and get your real frame rate up with upscaling instead (Step 4).
- If you want it on for high-refresh play, only enable it once you already hold 60+ real FPS — below that it makes stutter feel worse, not better.
- If a hitch lands on every zone transition and disappears the moment you disable Frame Generation, that is your cause. The latency trade-off is covered in frame generation input lag explained.
Step 4 — Turn off ray tracing and size settings to your GPU
The First Descendant is mostly GPU-bound at 1440p and 4K, and two settings dominate the load. In Settings → Graphics:
| Setting | Change | Why |
|---|---|---|
| Ray Tracing | Off | Only affects ambient occlusion; costs ~30% FPS — the biggest single win |
| Upscaling (DLSS / FSR / XeSS) | Quality | Large GPU saving; DLSS looks best on NVIDIA, FSR can look blurry |
| Textures | One tier below where VRAM fills | Prevents the slow-building spike pattern |
| Shadows / Effects | Medium | Meaningful cost, little visual loss |
| Visibility / Object Quality | Higher | Little FPS impact but big visual gain — spend budget here |
| Motion Blur | Off | Hides detail and adds perceived latency |
Watch VRAM in your overlay during real play, not in a menu. If it sits at 95-100% of your card’s capacity, drop Textures one tier and the spikes usually go with it. On NVIDIA GPUs stick to DLSS; on Radeon, FSR works but can look softer — which to pick is covered in DLSS vs FSR vs XeSS for gaming.
Step 5 — Cap FPS to what your CPU can always hold
The First Descendant’s frame rate swings between open zones and dense boss fights, and those swings are the stutter you feel. Capping removes them:
- Play through a busy fight and note the lowest stable FPS.
- Cap a few frames below that number with RTSS or your driver’s frame limiter.
- Keep V-Sync off and use the cap instead; with G-Sync or FreeSync, cap 3-4 FPS below your refresh rate.
A locked 60 genuinely feels smoother than an average of 90 that keeps dropping to 45. The reasoning and exact values are in the best FPS cap for low latency.
Step 6 — Fix mouse polling rate and RAM speed
Two system-side causes trip up otherwise-smooth setups:
- Mouse polling rate. A very high rate (8000 Hz) can cause CPU-side stutter in The First Descendant. If your FPS dips whenever you move the mouse fast, drop the polling rate to 1000 Hz (or even 125 Hz to test) in your mouse software. See mouse polling rate explained.
- Enable XMP/EXPO so RAM runs at its rated speed — JEDEC defaults starve a streaming shooter. See how to enable XMP or EXPO. 16 GB is the practical floor; 32 GB helps with Discord and a browser open.
Step 7 — Clear the usual Windows-side culprits
If the frame time is still spiky:
- Run in exclusive Fullscreen, not borderless — see fullscreen vs borderless vs windowed.
- Disable MPO if you get flickering plus stutter on NVIDIA — disable MPO to fix stutter and flickering.
- Install on an SSD with 15-20% free so the UE5 streaming keeps up — NVMe vs SATA SSD for gaming.
- Check DPC latency if the spikes are periodic and happen outside the game too — how to fix high DPC latency.
What to expect honestly
The First Descendant is a large UE5 game, so some first-visit hitching while the engine builds its cache is normal and no configuration removes it completely. What the steps above remove is the repeatable stutter: the shader-cache thrash, the Frame Generation zone-load hitch, the ray-tracing frame drops, and the frame-rate swings in boss fights. After the latest driver, ray tracing off, a fixed Frame Generation choice and a CPU-safe FPS cap, the frame-time line should be flat enough that the remaining hitches are rare and short.
For the system-side layer underneath all of this — a steady timer, a clean power plan and a tuned frame pipeline — start with how to minimize input delay for competitive gaming and the timer resolution pillar guide.
Related guides
Frequently asked questions
Why does The First Descendant stutter so much on PC?
The First Descendant runs on Unreal Engine 5, so most of its stutter comes from two things: shader compilation the first time new effects, enemies or areas appear, and the way Frame Generation hitches when a new zone loads. On top of that, ray tracing and high textures push weaker GPUs into VRAM pressure. Updating your GPU driver, letting shaders build for 15 minutes, turning ray tracing off, and capping FPS removes the bulk of the hitching.
How do I fix Frame Generation stuttering in The First Descendant?
The First Descendant's Frame Generation can stutter every time you load into a new area, and many players fix it by toggling Frame Generation off and back on after each zone change — or by simply leaving it off. Only use Frame Generation once you already hold 60+ real FPS; below that it makes hitching feel worse. If the stutter only appears with Frame Generation enabled, that is your cause, so disable it and raise your real frame rate with upscaling instead.
Does ray tracing cause stuttering in The First Descendant?
Ray tracing in The First Descendant only affects ambient occlusion but costs at least 30% FPS on most systems, and that lower, less stable frame rate reads as stutter. Turn ray tracing off first — even RTX 40-series owners see smoother frame time without it. Once ray tracing is off and you have enabled DLSS or FSR, most of the GPU-side hitching in busy areas disappears.
Why does my FPS drop when I set my mouse polling rate high?
Some The First Descendant players report that a very high mouse polling rate (like 8000 Hz) causes CPU-side stutter and FPS drops, and that dropping to 1000 Hz or even 125 Hz smooths it out. If your frame rate dips whenever you move the mouse quickly, lower the polling rate in your mouse software and retest. This is a CPU-contention issue, not a graphics one, so it survives every graphics change until you fix the polling rate.
What are the best settings to reduce The First Descendant stutter?
Turn ray tracing off, enable DLSS or FSR at Quality, cap your FPS a few frames below the lowest value you hold in a firefight, and set an NVIDIA Shader Cache Size of 100 GB so shaders stop re-compiling. Keep textures one tier below where your VRAM fills. These flatten the frame-time line rather than just raising the average, which is what actually feels smooth in a horde shooter like The First Descendant.