FPS & Stuttering / Rust / Unity

Rust: Fixing Wipe-Day Stutter and Low 1% FPS

Stabilise Rust after a forced wipe with a short client.cfg baseline, shader warm-up, and a realistic frame-time test.

Official Steam Store header artwork for Rust.

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 fix

The shortest safe order for this issue:

  1. Remove old client.cfg overrides and measure the default build first.
  2. Lower shadow distance and disable depth of field before reducing global quality.
  3. 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.

<Steam>/steamapps/common/Rust/cfg/client.cfg
graphics.shadowdistance 100
graphics.dof false
graphics.quality 2
fps.max 144
// Back up the file. The game may rewrite or clamp values.
Use F1 console commands to verify the effective values. A high FPS cap is not useful if the 1% low is 65.

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 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 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 answers
Why is Rust smooth on an empty server but terrible after wipe?
Entity count, player-built structures, and server load change the scene dramatically. That is why wipe-day performance must be tested on a populated server.
Should I set graphics.quality to zero?
That often creates an ugly baseline without solving a CPU bottleneck. Reduce shadows and post-processing first, then measure.
Filed under

FPS & Stuttering

Patch tested: November 2026 forced wipe

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.