Rust has heavy recoil patterns that you learn with muscle memory. That only works if your sensitivity is consistent and your mouse is not adding its own movement on top of yours.
Mouse acceleration means the same physical movement gives different in-game distances depending on how fast you move. That makes recoil control impossible to learn. Turn it off in three places:
What matters is not DPI alone but eDPI — DPI multiplied by in-game sensitivity. Two players with different DPI and matching eDPI aim identically.
| Style | eDPI range | Typical setup |
|---|---|---|
| Low / precise | 20–35 | 800 DPI × 0.03 |
| Balanced | 35–60 | 800 DPI × 0.06 |
| High / fast | 60–100 | 1600 DPI × 0.05 |
Most competitive Rust players sit in the balanced band. Pick one, then leave it alone for a few weeks — changing sensitivity constantly is what stops recoil control from ever becoming automatic.
Polling rate is how often the mouse reports its position. 1000 Hz is the sensible standard. Modern mice support 4000 or 8000 Hz, which slightly reduces input delay but costs measurable CPU — on a weaker CPU that trade can lose you more in frames than it gains in latency.
Rust scales your sensitivity when aiming down sights. If scoped aiming feels wrong compared to hipfire, adjust the ADS sensitivity slider rather than your main sensitivity — that keeps your muscle memory for spraying intact.
Face a wall, place your crosshair on a mark, swipe your mouse left across the pad and back to the exact same physical spot. If the crosshair does not land back on the mark, you still have acceleration or smoothing somewhere.
Most sit at 800 or 1600 DPI with a low in-game sensitivity, landing at an eDPI around 35–60. The exact DPI matters less than keeping eDPI consistent.
Marginally lower input delay, but noticeably more CPU usage. On a mid or low end CPU, 1000 Hz is the better trade because Rust is CPU-bound.
Usually acceleration still enabled somewhere, or changing sensitivity too often. Fix both, pick one eDPI, and give it a couple of weeks.