FPS & Stuttering / ARC Raiders / Unreal Engine 5

ARC Raiders: UE5 Shader Warm-Up and Traversal Stutter Fix

Separate first-run shader compilation from repeatable ARC Raiders traversal hitching and build a stable 1440p baseline.

Official Steam Store header artwork for ARC Raiders.

ARC Raiders uses Unreal Engine 5, so “stutter” can mean pipeline compilation, asset streaming, or a GPU memory spike. They respond to different changes.

UE5 Shader Warm-Up and Traversal Stutter Fix

Verified field fix

The shortest safe order for this issue:

  1. Repeat a fixed route twice before judging a shader-cache change.
  2. Cap the streaming pool below the GPU’s VRAM limit instead of maxing it out.
  3. Remove injected overlays and test with the latest patch before editing Engine.ini.

First run versus second run

A hitch that vanishes on the second identical route is cache warming. A hitch that repeats at the same door or extraction point is streaming or CPU work. Record the exact location and time before touching a config.

%LOCALAPPDATA%/ArcRaiders/Saved/Config/WindowsClient/Engine.ini
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
r.PSOPrecaching=1
t.MaxFPS=141
Back up the original file. A value that does not survive a restart is not in the effective config chain.

A conservative streaming cap

Large streaming pools can improve texture residency while increasing VRAM pressure. On a 12 GB card, a pool near 6–7 GB leaves room for render targets and shader data. The correct value is the one that survives your busiest map, not the largest number in a copied .ini.

Field notes before you change the build

Frame time is the evidence for ARC Raiders. Record the average, the 1% low, and the location of the worst spike on the same save or route. A higher average built on a 30 FPS low is not an upgrade, especially in a Unreal Engine 5 scene with heavy streaming.

Test at the same resolution, preset, upscaler, and refresh cap. If GPU utilisation falls while frame time rises, investigate CPU or streaming pressure; if memory is pinned, reduce the working set rather than adding more speculative config lines.

  • Do not compare a menu screenshot with a combat or traversal route.
  • Do not enable frame generation while measuring the native baseline.
  • Do not clear the shader cache before every session.

Check it before you keep it

Capture the first and second runs on the same route

0 / 5 complete

If the low returns

Re-test the patch and driver first, then the last two changes. Restore the stable profile rather than layering more tweaks on top of an unknown regression.

The line to keep

A patch-scoped baseline and a repeatable route are more valuable than any single Engine.ini line.

Did this fix work on Patch 1.9 — traversal stutter and shader preload?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 1.9 — traversal stutter and shader preload. Votes are local-only telemetry.

ARC Raiders: bench questions

2 answers
Does clearing the shader cache help ARC Raiders?
Only once after a driver or game patch that invalidated it. Repeating the deletion forces compilation every session.
Is a larger streaming pool always better?
No. It can crowd out other VRAM allocations and produce a new kind of stutter. Keep it below the card limit.
Filed under

FPS & Stuttering

Patch tested: 1.9 — traversal stutter and shader preload

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.