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 fixThe shortest safe order for this issue:
- Repeat a fixed route twice before judging a shader-cache change.
- Cap the streaming pool below the GPU’s VRAM limit instead of maxing it out.
- 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.
[SystemSettings]
r.Streaming.PoolSize=6144
r.Streaming.LimitPoolSizeToVRAM=1
r.Streaming.MaxTempMemoryAllowed=256
r.PSOPrecaching=1
t.MaxFPS=141 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 completeIf 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 answersDoes clearing the shader cache help ARC Raiders?
Is a larger streaming pool always better?
FPS & Stuttering
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.
ARC Raiders: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise ARC Raiders on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Unreal Engine 5.
ARC Raiders: Shader Stutter, Frame Pacing & Unreal Engine 5 Config Tuning
A measured stutter-hunting routine for ARC Raiders: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unreal Engine 5 settings file to edit.
ARC Raiders: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on ARC Raiders without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.