Rust input lag

That "the mouse is swimming" feeling at a perfectly fine framerate is not about frames. Between your hand and the screen sits a chain of seven links, and most of them can be shortened by settings alone.

What the delay is made of · 1. Exclusive fullscreen · 2. The right FPS cap · 3. V-Sync · 4. NVIDIA Reflex or AMD Anti-Lag · 5. Mouse · 6. Overlays and background · 7. Monitor · How to verify

What the delay is made of

The free items add up to 30–60 ms — more than you gain moving from 60 Hz to 144 Hz. So do not start by buying a monitor.

1. Exclusive fullscreen

In Rust this is a launch option, because the menu only offers "Fullscreen" without saying which kind:

-window-mode exclusive

In windowed and borderless modes every frame passes through the Windows compositor — 5–15 ms and a distinctly floaty feel. Exclusive mode hands output straight to the game. The only downside is slower alt-tab.

2. The right FPS cap

The counter-intuitive part: an uncapped framerate often increases latency. Uncapped, the render queue fills up, and the frame you are looking at was ready several frames ago.

fps.limit 141

• 60 Hz monitor → fps.limit 58
• 144 Hz monitor → fps.limit 141
• 240 Hz monitor → fps.limit 237
• If your system cannot hold the refresh rate, cap 5–10% below your stable minimum instead.

Put the value in client.cfg or it resets on the next launch.

3. V-Sync

Off, both in the game and in the driver panel. V-Sync holds a finished frame until the next display refresh, which is a guaranteed extra frame of latency.

The exception is a G-Sync or FreeSync monitor. Then: V-Sync on in the driver panel, off in the game, and an fps.limit three frames below your refresh rate. That combination has no tearing and no added latency.

4. NVIDIA Reflex or AMD Anti-Lag

Reflex removes the queue of pre-rendered frames by pacing the CPU against the GPU. Worth 10–20 ms, which is noticeable while tracking a target. Look for it in Rust’s graphics settings; it needs Hardware-Accelerated GPU Scheduling enabled in Windows.

With Reflex on in-game, set "Low Latency Mode" in the NVIDIA panel to Off — they do the same job and interfere. On AMD the equivalent is Radeon Anti-Lag in Adrenalin.

5. Mouse

• 1000 Hz polling rate in your vendor software. 125 Hz is 8 ms of delay for free.
• Turn off mouse acceleration in Windows ("Enhance pointer precision") and in the game.
• Windows pointer speed at exactly 6/11 — the position with no software scaling.
• Wired, or a 2.4 GHz dongle placed near the mouse. Bluetooth is not suitable for play.
• Plug the dongle straight into a port, not through a hub and not next to a USB 3.0 drive — those interfere on the same band.
• Use one native sensor DPI (typically 400/800/1600); without interpolation the movement is cleaner.

6. Overlays and background

Every overlay intercepts the frame before output. Discord, Steam, GeForce Experience, MSI Afterburner with RTSS, Razer Synapse, Xbox Game Bar — keep the one you need and turn the rest off. Also make sure background recording is not running: Game DVR keeps a rolling buffer at all times.

7. Monitor

In the monitor’s own menu enable game mode and disable every "picture enhancement": dynamic contrast, noise reduction, motion interpolation, HDR processing. Each one buffers a frame inside the display. Set Overdrive to medium — maximum produces inverse ghosting.

And check the obvious: that the monitor is actually running at its rated refresh rate. Settings → Display → Advanced display. After a driver change it sometimes silently drops to 60 Hz.

How to verify

Objectively: film your mouse and the screen with a 240 fps phone camera and count frames between the movement and the response. Practically: take the same target on a training server before and after. The floatiness while tracking disappears noticeably.

And honestly: if "I shoot and nothing registers" persists at zero display latency, the cause is the network, not the mouse. Ping and packet loss produce similar symptoms for a different reason.

FAQ

Why does the mouse feel floaty at 200 FPS in Rust?

FPS says how often frames are drawn, not how fast your movement reaches the screen. Latency comes from the frame queue, windowed mode, V-Sync, overlays and low mouse polling rate. None of those affect FPS, but together they add 30–60 ms.

Is it true that removing the FPS cap increases latency?

Yes, in most cases. Uncapped, the render queue fills and the displayed frame lags behind the current game state. A cap slightly below your stable minimum evens out frame times and lowers response time.

Do I need a 144 Hz monitor to fix input lag in Rust?

It helps, but it is the most expensive link in the chain. First remove the free delays: exclusive fullscreen, V-Sync off, a proper FPS cap, Reflex, fewer overlays. 60 Hz configured properly feels better than 144 Hz with V-Sync and borderless windowed.

Does draw distance affect mouse latency?

Indirectly. Heavy settings lower FPS and lengthen frame preparation, which shows up as response time. But if your FPS is CPU-bound, lowering draw distance changes little — check first: GPU usage below 90% means the CPU is the limit.