Battlefield 2042 stutters in 128-player Conquest even with high FPS

FPS counter sits around 100-110 but the game hitches constantly, and it’s clearly worse the bigger the fight — massive flag battles on Conquest 128 are the worst, quiet moments feel fine. Same rig runs other shooters smooth (Ryzen 5 3600 / RTX 3070, 1440p).

Is there a sensible test order for shader cache vs CPU vs overlays before I nuke and reinstall the whole 100 GB?

2042’s “high FPS but choppy” complaint has a different #1 suspect than most shooters: half the time it’s not your PC at all, and the other half it’s your CPU. Order that wastes the least time:

1) Rule out the server first — free, takes 2 minutes. Turn on the network performance overlay in the options. If the packet loss / latency icons flash exactly when the game hitches, that’s server-side rubber banding, and packed 128 servers are infamous for it. It reads exactly like local stutter but no setting on your end will ever fix it — switch servers or drop to a smaller mode. Don’t burn an evening tweaking graphics for a server problem.

2) The 64 vs 128 test. Play a full match in a 64-player mode, then Conquest 128. Smooth at 64 but hitchy at 128 → you’re CPU-bound, which on a 3600 in this game is expected — 127 other players, vehicles and collapsing buildings all land on the CPU, and no graphics preset changes that. Damage control: cap FPS below your dip floor (try 90), Reflex on, kill background apps. A locked 90 feels way smoother than 100-140 bouncing around.

3) Updated GPU drivers recently? New driver invalidates the shader cache and the first match stutters on every fresh effect. If it never settled down after a driver swap, clear %localappdata%\NVIDIA\DXCache and give it one full match to rebuild before judging.

4) Overlays — EA App’s especially. EA App overlay plus Discord plus GeForce overlay stacked together is a classic hitch source in this game. All off, one match, compare.

5) Still ambiguous → measure it. Afterburner + RTSS frametime graph: spikes while GPU usage dips = CPU or streaming; spikes with GPU pinned at 99% = GPU side. On a 3070 at 1440p, GPU-side is honestly the least likely of the bunch here.

Reinstalling rebuilds exactly one thing — the shader cache — and you can do that by deleting one folder. Skip it.