Warhammer 40K Space Marine 2 PC Stutter and Low FPS Explained: Fix the Swarm Horde Load First, Then Use DLSS and FSR Correctly

Space Marine 2 does not stutter because your GPU is weak. It stutters because the Swarm Engine is doing what it was built to do: throw hundreds of Tyranids at three Space Marines at once, then ask your CPU to pathfind, animate, and sync every one of them.

Fix the horde load first — lighter Operations lobby, SSD headroom without the optional 4K pack unless you have VRAM to spare, FPS cap, then cut volumetrics, shadows, and effects — and only then pick DLSS or FSR by GPU. That order matters more than any single Ultra-to-Low toggle.

Scope: PC Windows version released 9 September 2024, Swarm Engine, through October 2026 patches. This is not PS5, Xbox Series X/S, or the announced Switch 2 path.

What Space Marine 2 actually is on PC

Space Marine 2 was developed by Saber St. Petersburg (Saber Interactive) and published by Focus Entertainment as a third-person shooter with hack-and-slash melee, released for PS5, Windows, and Xbox Series X/S on 9 September 2024. You play Lieutenant Titus of the Ultramarines with Chairon and Gadriel as AI or co-op partners.

The structure is three games in one client:

• 3-player campaign co-op as Titus, Chairon, and Gadriel
• Operations, a parallel 3-player PvE campaign, plus Stratagems variants and endless Siege defense
• 6v6 PvP for 12 players with seven classes from Tactical to Techmarine

Focus Entertainment sells the same point directly: this is the sequel by the creators of World War Z, a game that reached 15 million players on horde tech. That lineage is the performance clue.

Why a good PC still hitches: the Swarm Tollbooth

Most stutter guides treat Space Marine 2 like another Unreal Engine 5 Lumen game. It is not. Its Swarm Engine comes from World War Z, where Saber built a proprietary engine to render huge hordes. That game supports up to 1,000 enemies on screen, with the engine purposefully built to handle around 500 zombies at once, climbing over each other to reach high ground.

Space Marine 2 swaps zombies for Tyranids and Chaos cultists, but keeps the design: dense melee funnels, ranged lanes, executions, and co-op revives. Every horde push is a tollbooth:

1. AI spawns dozens of pathfinding bodies
2. Melee contacts trigger parry, dodge, gun-strike, and execution checks
3. Armor-break versus health-loss versus revive timers must stay in sync across three clients
4. In Operations and Siege, the director keeps spawning while you are already locked in melee

Your FPS counter can read 90 while the 1% lows collapse, because one client spamming executions during a Hormagaunt flood delays everyone. That is why “high FPS but not smooth” is common here, and why lowering resolution alone rarely fixes it.

My take: the Execution Economy (opinion)

Here is where I break from generic “lower everything” lists.

Space Marine 2 ties survival to aggression: armor regenerates by performing executions, health only comes from stimpaks or high-level abilities. In other words, the game pays you to dive into the worst frame-pacing moment on purpose.

I call this the Execution Economy. In a cover shooter you can wait out a hitch behind a wall. In Space Marine 2 waiting means no armor. So micro-stutter is not cosmetic — it directly taxes your parry and dodge window, especially against unblockable attacks you must dodge rather than parry.

The contrarian implication: prioritize stable frame pacing over peak FPS. A locked 60 fps that lets you read red unblockable tells beats a swinging 90-130 fps that drops to 45 every time a Carnifex plus two waves arrive. If you love high refresh, earn it after the base is stable, not before.

A second unique lens: the Parade-Ground Paradox. Space Marine 2 sells power fantasy — huge pauldrons, chainsword roars — but the engine treats you like a traffic cop. You are not rendering one beautiful Space Marine; you are conducting 200 ugly Tyranids. Settings that reduce crowd cost (effects density, shadows, volumetrics) help more than settings that make Titus shinier.

Three open questions I cannot resolve from public docs, so treat them as limits:

• What is the exact per-wave entity budget on each difficulty in Operations versus Siege?
• How much of Operations stutter is host-simulation versus client-render?
• Does the 4K Texture Pack change streaming hitches on SATA SSDs versus NVMe?

What DLSS and FSR actually do here

PCGamingWiki lists Space Marine 2 with TAA that cannot be disabled, plus DLAA, FSR Native AA, DLSS 4 (release build actually DLSS 3.7 despite menu text saying DLSS 2), FSR 2.2, and FSR 3.1. Ultrawide up to 21:9 was added 26 September 2024, with 32:9 Vert- limits, and a 1.0-1.45 FOV scaler was added in Patch 6. Note its warning: DLSS set to Dynamic can stretch the 16:9 viewport horizontally.

Use that correctly:

• DLSS Super Resolution reconstructs a higher-resolution frame from lower-resolution input using motion data and prior frames, with a transformer model for stability and clarity. DLAA is the same tech at native resolution for anti-aliasing without upscaling.
• DLSS Frame Generation generates AI frames to boost FPS, best paired with low-latency handling. Multi Frame Generation on RTX 50-series can generate up to five frames per rendered frame.
• FSR 3 combines temporal upscaling with Frame Generation via interpolation and optical flow from Fluid Motion Frames. Quality, Balanced, Performance, and optional Ultra Performance trade scaling amount for speed, while Native AA is pure anti-aliasing with no upscaling. Frame Generation helps in both GPU- and CPU-limited cases, but still needs a stable base to avoid amplifying hitches.

Translation for Space Marine 2: upscaling fixes pixel cost. It does not fix Swarm AI cost or 3-player sync. Turn on Frame Generation on an unstable 45 fps horde fight and you get smoother-looking slides with worse parry timing.

The correct fix order on PC

Do this in order. Stop when smooth, then push visuals back up.

1. Lighten the simulation before pixels

• Prefer a wired connection and a 3-player lobby in your region for Operations and Siege. If one friend is on Wi-Fi with packet loss, you will feel it as shared stutter.
• Avoid endless Siege marathons as your test case. Use a short campaign or Operations mission to isolate settings.
• Close browsers, Discord overlays, and recording while testing. Swarm plus capture is a classic double-tax.
• Config lives at %LOCALAPPDATA%\Saber\Space Marine 2\storage\steam\user\<user-id>\Main\config\ per PCGamingWiki. Back it up before hand-editing.

2. Give streaming headroom

• Keep the game on an SSD with 20%+ free. Do not install the free 4K Texture Pack on 8GB VRAM cards or SATA SSDs unless you have tested it — high-res packs raise streaming pressure during Zone jumps and horde spawns.
• If you just patched, play one full mission before judging. Post-patch shader and cache rebuilds masquerade as permanent stutter.

3. Cap FPS first, then cut crowd costs

• Cap FPS to your monitor minus a margin (for example 57-58 for 60Hz, 116 for 120Hz) or use half-refresh while testing. A cap stabilizes the Execution Economy timing.
• Cut in this order: Volumetrics / Fog, Shadows, Effects / Particles, Texture Filtering from Ultra to High, then FOV from 1.45 back toward 1.0. FOV widens rendered bodies and hurts more here than in corridor shooters.
• Leave TAA on (you cannot disable it anyway). Try DLAA only if you are already at native resolution and stable; otherwise use upscaling below.

4. Pick upscaling by GPU and resolution

• RTX card at 1440p or 4K: DLSS Quality at 1440p, Balanced or Performance at 4K. Avoid DLSS Dynamic while on 16:9 until the stretch bug is confirmed fixed for your build.
• AMD or Intel card, or any card at 1080p where DLSS looks soft: FSR 3.1 Quality, then Balanced. Use FSR Native AA only if you dislike upscaling softness and already hold 60 fps+ in hordes.
• Enable Frame Generation only after you hold a stable 60 fps in a real Tyranid flood without it. If 1% lows still dip under 50, fix steps 1-3 first.

5. Fix the two Space Marine 2-specific traps

• Ultrawide: if UI looks stretched on 16:9 after using DLSS Dynamic, switch to a fixed Quality preset. That PCGamingWiki Dynamic-stretch warning is not generic advice — it is this game’s bug.
• FOV 1.45: max FOV feels great for chainsword swings but costs CPU and GPU during 6v6 Annihilation and Siege waves. Treat 1.2-1.3 as the sweet spot for low-end PCs.

Which mode to tune for

• Campaign: easiest to stabilize. Tune here first.
• Operations and Stratagems: add co-op sync plus modifiers. Expect 10-20% lower stable FPS than solo campaign in dense waves.
• Siege: endless scaling means no single “safe” setting. Cap FPS conservatively and keep effects down.
• 6v6 PvP (Annihilation, Seize Ground, Capture and Control, Helbrute Onslaught): prioritizes latency and readability over beauty. Lower effects and shadows even if campaign looks fine.

Stay sharp while you test: low-spec drills that actually transfer

You do not need to keep throwing your PC at endless Siege to practice the two skills Space Marine 2 checks: ranged lane tracking and melee parry/dodge timing. These browser games run without install and isolate each skill:

• For bolt-rifle tracking and choke-point timing, run Hazmob FPS: Online Shooter. It is a free browser FPS with seven modes including Team Deathmatch and Free for All, 55+ customizable weapons, and Quick Battle versus Custom Match lobbies. Use Free for All for pure aim practice — keep moving, take cover after each fight — then Domination to practice the same objective rotation you need in Seize Ground.
• For execution rhythm and not panicking when surrounded, play Iron Snout. You are a pig fighting wolves from both sides with arrow-key punches, kicks, jumps, and weapon catches across Classic endless waves and Sudden Death one-hit mode. Stay centered, catch thrown axes, and avoid spamming — the same discipline as waiting for the gun-strike window instead of mashing chainsword.
• For loadout thinking, try Stick Merge. You drag two identical guns to merge up a 50-tier chain from pistols to laser rifles and miniguns, managing coins-per-second and shop tier. It is a good reminder not to hoard low-tier habits: one clear tier jump in Space Marine 2 — for example swapping a struggling perk for team ammo economy — beats fiddling with three minor sliders.

Use them as warm-ups between setting changes, not as replacements for the fix order above.

Quick checklist

• Wired, same-region 3-player lobby for test
• SSD with headroom; 4K pack only if VRAM allows
• FPS cap on before judging
• Volumetrics, shadows, effects cut before resolution
• FOV 1.0-1.3 while testing; 1.45 last
• DLSS Quality (RTX) or FSR 3.1 Quality (others); avoid DLSS Dynamic on 16:9
• Frame Generation only on stable 60 fps horde base
• Re-test in Operations or Siege, not just campaign

FAQ

Why does Space Marine 2 stutter with high FPS? Because average FPS hides horde spikes. Swarm can push 500 pathfinding bodies at once, plus 3-player sync. Cap FPS and cut crowd costs to fix 1% lows, not just the counter.

DLSS or FSR for Space Marine 2? RTX at 1440p/4K: DLSS Quality/Balanced. Others or 1080p: FSR 3.1 Quality/Balanced. Both need a stable base before Frame Generation.

Does the 4K Texture Pack hurt performance? It can on low VRAM or slower SSDs because streaming load rises during horde spawns. Untick it while troubleshooting, then re-add only if stable.

Is this a UE5 Lumen problem? No. This is Swarm horde simulation plus co-op sync, not Lumen global illumination. Treat it as a CPU event-queue problem first.