Mouse Settings and Sensitivity for Rust: DPI, Sens, FOV, and Binds

Introduction

Mouse sensitivity is the setting most Rust players tweak the most and understand the least. You lose a fight, go into options, move the slider, lose the next fight, move it back. Over a month, you end up playing on ten different sensitivities and build muscle memory on none of them.

The truth is, there's no "best" sensitivity — but there is a range of sensible values and an objective way to measure yours: cm/360. Once you translate the setting from abstract "0.3" into physical "32 centimeters per full turn," everything becomes testable: you can compare yourself across games, switch mice without losing skill, and stop touching the slider on impulse.

This guide covers how sensitivity works in Rust, how to measure and transfer it from CS2 or Valorant, what to do with DPI, why the ADS multiplier matters, how FOV affects aiming, and which binds are worth setting once. Recoil itself has its own guide — here, it's all about settings for your fingers.

DPI, Sens, and the Key Number: cm/360

Turn speed in-game is determined by the product of two numbers: mouse DPI × in-game sensitivity. Neither one means anything on its own.

Hence the simple rule: halve your DPI — double your in-game sens; the resulting speed stays the same. 400 DPI × 0.6 and 800 DPI × 0.3 are the same thing.

cm/360 — how many centimeters the mouse must travel across the pad for your character to turn 360°. This is the universal unit: it doesn't depend on the game, the mouse, or the resolution.

How to measure your cm/360 without a calculator: place the mouse at the left edge of your pad, aim at a noticeable object in-game, slowly drag the mouse right until you complete a full turn, and measure the distance with a ruler. If you had to lift and reposition, add the segments together.

Reference points for Rust:

Most of the Rust community lives in the 400-800 DPI and 0.2-0.5 in-game sens range, which gives roughly 25-40 cm per turn. That's no accident: Rust demands both controlling a long spray (needs precision) and whipping around to a sound behind you (needs speed). Extremes work poorly in both directions.

Polling rate: 1000 Hz is the standard and safe choice. Mice at 4000/8000 Hz noticeably load the CPU, and Rust is already CPU-bound. If FPS drops, go back to 1000 Hz.

Acceleration and smoothing should be disabled everywhere: in Windows ("Enhance pointer precision"), in your mouse software, and in-game. In the Rust console, raw input is controlled by:

input.rawinput true

Without this, the same hand movement will produce different turn distances depending on speed — muscle memory cannot be built in such a system at all.

How to Transfer Sens from Another Game

If you came from CS2, Valorant, or Apex and were comfortable there — don't pick a new sens from scratch, transfer it.

A method without calculators and without errors:

1. Measure your cm/360 in the source game (same ruler method).
2. Launch Rust, set a starting value — for example, 800 DPI × 0.3.
3. Measure cm/360 in Rust.
4. Adjust the in-game sens proportionally: if Rust gives 40 cm and you need 30, multiply sens by 40/30 ≈ 1.33.

One nuance: 1:1 cm/360 is the right baseline, but not dogma. In CS2, fights happen more often at fixed distances in corridors; in Rust, it's open terrain with a wide spread of distances and the need to spin quickly during a raid. Many people transfer sens 1:1 and then make it 10-15% faster.

If you want precision, there are ready-made converters (mouse-sensitivity.com, aiming.pro, 3daimtrainer.com) with Rust profiles. But verify the result with a ruler: converters sometimes lag behind patches.

ADS Multiplier, FOV, and Crosshair

ADS Sensitivity — a separate sensitivity multiplier when aiming down sights. A value of 1.0 means "same as hipfire," 0.5 means half as fast. It's set in the controls options or via console:

input.ads_sensitivity 0.5

What to choose. A low multiplier (0.4-0.6) gives precision at long range and makes spray control easier, but hurts when you need to flick onto a close target. A high one (0.8-1.0) suits an aggressive style and strafe-spraying. General advice: start around 0.5-0.6, and only change it if you clearly understand what you're missing — flick speed or stability.

FOV (field of view) is changed with a slider in options or via command:

graphics.fov 90

The slider caps at 90, and the vast majority of PvP players set it to max: wider view, you spot flanks earlier. The cost — targets appear visually smaller, and hitting at 100+ meters feels harder. If you play mostly long-range with a bolt, try a value below max and compare honestly, not based on the first evening's impression.

Another command worth setting right away:

graphics.vm_fov_scale false

It removes the "blow-up" of the weapon model when aiming — the gun stops taking up half the screen and blocking your target.

About the crosshair. The key fact in Rust: the bullet flies to the geometric center of the screen, not where the iron sight points. That's why many play with a center dot — a Steam overlay, a dot on the monitor, or an in-game crosshair if the server allows it. This isn't cheating and is standard among strong players, but check the rules of your specific server if you use third-party software.

Binds Worth Setting Once

Binds in Rust are set in the console (F1) and saved to the config — they survive wipes, and you only need to enter them once.

bind z duck                       // toggle crouch
bind x forward;sprint             // auto-run
bind f1 consoletoggle;combatlog   // console opens straight to combat log

• Toggle crouch takes the strain off your pinky during long firefights and is useful for holding an angle: you can sit indefinitely, finger free.
• Auto-run saves your finger on long treks across the map — and you run a lot in Rust.
• Combatlog on console — the most underrated bind. After every fight, you see how many bullets hit, where, and how many missed. That's objective data instead of "he was cheating."

Useful extras:

• Gestures (`bind <key> gestures.wave` and others) — a quick way to signal "I'm not an enemy" at a neutral encounter.
• Voice on hold by default (`+voice`). Binding it to a toggle is dangerous: an enemy nearby will hear your conversation through proxy chat.
• Don't bind chains of five commands to one key. The less magic in your config, the fewer reasons to wonder why your character is doing the wrong thing.

How to Test New Settings

Changing sens always makes your game worse at first — that's normal, muscle memory is rebuilding. To avoid flailing:

1. Pick a value by cm/360, not "by eye." Verify: a 180° turn should be one motion, no mouse lift needed.
2. Play on it for at least a week, without touching the slider at all.
3. Change no more than one variable at a time: first sens, then ADS multiplier, then FOV.
4. Write down what you changed and when — otherwise, a month later, you won't know what helped.

A player who's been on "average" settings for six months consistently beats a player with theoretically perfect numbers that change every week. Consistency beats optimality.

FAQ on Mouse Settings

What's the best sensitivity for Rust?

A universal starting point — 800 DPI × 0.3 or 400 DPI × 0.5-0.6, which gives roughly 25-35 cm per full turn. This range lets you both control a long spray and spin around on sound. The exact number is secondary: what matters is that you don't change it for weeks and build muscle memory.

Should I lower DPI and raise sens, or the opposite?

In terms of turn speed, it's the same — only the product of DPI and sens matters. The difference is elsewhere: at very low DPI, the sensor gives coarser steps; at very high DPI, the risk of jitter rises. A safe compromise for most mice is 400-1600 DPI, and fine-tune with the in-game slider.

How do I transfer sensitivity from CS2 or Valorant?

Measure cm/360 in the source game with a ruler, then adjust the in-game sens in Rust to match that distance. Converters like mouse-sensitivity.com give a quick start, but verify the result manually. Many people, after a 1:1 transfer, make Rust sens slightly faster — there are more open spaces and turns here.

What ADS multiplier should I set?

Start with 0.5-0.6: it's a compromise between long-range precision and the ability to flick in close combat. Lower it if you're overshooting targets while aiming; raise it if you're losing close fights due to slow flicks. Change only one parameter per session, or you won't know what worked.

Conclusion

Setting up your mouse in Rust comes down to three decisions: pick a cm/360 in a sensible range (25-35 cm is a working baseline), disable all acceleration and enable `input.rawinput true`, and set FOV and ADS multiplier to your style. Everything else is binds — entered once and working for the life of your account.

After that comes the only thing that actually raises your level: not changing settings. Stable fingers beat perfect numbers. Lock in your config, save it somewhere, and return to it after every reinstall — and spend your free time training recoil, not the slider.

Sources: Rust Wiki (wiki.facepunch.com), corrosionhour.com (RUST Settings Guide), rustly.com (Aim & Sensitivity Guide), mouse-sensitivity.com and aiming.pro (Rust converters), rustmates.com (Keybinds & Console Commands 2026), r/playrust.