Why does THE FINALS feel stuttery even when the FPS counter looks fine?

Getting 140+ FPS on the counter but the game feels way choppier than that — smooth for a stretch, then short hitches when I whip the camera around or when a building comes down. Other shooters run fine on the same rig (5600X / 3070, 1440p).

What’s the cleanest way to narrow down whether this is shader compilation, CPU, VRAM, or an overlay problem? Ideally a test order that doesn’t start with “reinstall the whole game.”

Your FPS counter isn’t lying, it’s averaging. Stutter lives in frame times, not frame rates — 140 fps with a 35 ms spike every few seconds still feels like garbage, and the counter will happily say 140 the whole time. So before touching a single setting, get a frametime graph: MSI Afterburner + RivaTuner, enable the frametime graph and 1% lows in the overlay. Everything below is just reading that graph.

1) Watch GPU usage during a hitch. This one number splits the problem in half. Frametime spikes while GPU usage dips → the GPU is waiting on something (CPU, shader compile, streaming). Spikes while GPU stays pinned at 99% → VRAM pressure or plain overload.

2) Kill overlays first, it’s free. Discord overlay, NVIDIA App overlay, Steam overlay, Xbox Game Bar. Run one full match with all of them off. Overlays hook into the game’s presentation and cause exactly this “fine average, random hitches” pattern.

3) Shader compile check. Did this start after a GPU driver update? Driver updates invalidate the shader cache, and UE5 games rebuild a lot of it mid-match — first explosion of each type, first time each gadget fires. Signature: hitches fade the longer the session goes, then come back after the next driver update. Fix is patience (a match or two), or clear %localappdata%\NVIDIA\DXCache for a clean rebuild if it’s been weird ever since a driver swap.

4) VRAM / texture streaming. 8 GB at 1440p is genuinely tight in this game. Add per-process VRAM to the Afterburner overlay — if you’re brushing the cap, fast camera turns force texture streaming and that’s your hitch on look-flicks. Test by dropping texture quality only one notch and playing the same map. Stutter gone → found it, leave everything else high.

5) Destruction = CPU spikes. The servers decide what collapses, but your CPU still draws every chunk of debris. If hitches cluster around buildings coming down and GPU usage dips at the same moment, you’re CPU-bound in those moments. Turn Reflex on and cap your framerate slightly below your dip floor — a locked 120 feels dramatically smoother than 130–160 bouncing around. That cap alone fixes “choppy despite good FPS” for a lot of people.

Reinstalling does nothing for any of these, you were right to skip it. For your exact pattern — fine for a stretch, hitches on camera turns and busy areas — my money’s on VRAM streaming or a post-driver shader rebuild, with overlays as the sneaky third option.