Wipe-day Rust is not a normal performance benchmark. Large player-built bases, entity load, and server-side work create frame-time spikes that a hideout test will never show.
Fixing Wipe-Day Stutter and Low 1% FPS
Verified field fixThe shortest safe order for this issue:
- Remove old client.cfg overrides and measure the default build first.
- Lower shadow distance and disable depth of field before reducing global quality.
- Use an FPS cap with headroom and test the same monument route after wipe.
The GPU is not always the limiter
If GPU utilisation drops while the frame time spikes near a clan base, the CPU is waiting on entity and network work. Lowering resolution will not fix that. Conversely, a steady GPU load with low VRAM headroom points to texture or shadow pressure.
graphics.shadowdistance 100
graphics.dof false
graphics.quality 2
fps.max 144
// Back up the file. The game may rewrite or clamp values. Change one graphics command group
Start with shadows and depth of field. These are visible, reversible, and often large enough to measure on a 1440p display. Keep a copy of the original client.cfg and avoid stacking every “performance” command you have seen.
Field notes before you change the build
Frame time is the evidence for Rust. 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 Unity 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
Test a monument and a clan-base route separately
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 wipe is a new workload. Keep the baseline small, verify it on a real server, and revisit your settings after the population changes.
Did this fix work on Patch November 2026 forced wipe?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against November 2026 forced wipe. Votes are local-only telemetry.
Rust: bench questions
2 answersWhy is Rust smooth on an empty server but terrible after wipe?
Should I set graphics.quality to zero?
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.
Rust: Shader Stutter, Frame Pacing & Unity Config Tuning
A measured stutter-hunting routine for Rust: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Unity settings file to edit.
Rust: Safe Mod Install, Load Order & Post-Patch Conflict Recovery
Install mods on Rust without breaking the build: framework order, script conflicts after a patch, and a clean rollback path that keeps your saves intact.
Rust: Controller, DualSense & Raw Mouse Input Latency Fixes
Fix Rust input lag, deadzones, DualSense/FFB detection, and raw mouse polling for a clean competitive or simulation control path on Unity.