The same turn, in Rust
cm/360 is the only sensitivity number that means the same thing in every game. Measure one turn in Rust, and every conversion after it — a new DPI, a sensitivity from another game, a different field of view — is arithmetic rather than a guess.
Every converter needs one number per game: the yaw, meaning how far the view turns per mouse count at sensitivity 1. Facepunch does not publish Rust's, and the public converters that do publish one do not agree with each other — 0.11247, 0.003939 and 0.00222 all appear on different sites for the same game. Unity upgrades have moved it before.
So this page ships no game constants at all. Thirty seconds on your own mousepad gives you a figure that is exactly right for the build you are playing, and it cannot go stale the way a hardcoded constant does.
The feel you want to keep
The game you are coming from — or Rust itself, if you are only changing DPI. Either measure a 360 there too, or type in a yaw you already trust.
Mouse against one edge of the pad, turn exactly one full circle, measure how far the mouse travelled.
Fill in the three boxes
DPI, sensitivity and either a measured 360 or a yaw. All three have to be above zero before anything below can be worked out.
Field of view
Optional. Skip it unless the two games run different fields of view and you care about matching what the screen does rather than what the world does.
One full turn takes the same mouse travel in both games. The world moves identically; the screen does not, because a wider view fits more of that world into the same pixels.
No adjustment: your cm/360 carries over unchanged.
Calibrate Rust
One measured 360 in Rust, at any sensitivity you like. This is what replaces the constant we refuse to invent.
Any value. It does not have to be the one you end up using.
Measured in Rust, at the sensitivity on the left.
- 1. Stand still, pick a landmark, and put the mouse against one edge of the pad.
- 2. Drag across in one continuous movement until you are facing the landmark again — exactly one turn, no lifting.
- 3. Measure the distance the mouse travelled and type it in. Two or three attempts averaged beats one careful one.
Your Rust sensitivity
Type this into the in-game sensitivity setting. Everything above it is your own measurement, so it is right for your build, not for an average of ten websites.
One measurement short
The answer needs both halves: the feel you are carrying over, and a measured 360 in Rust to convert it into a sensitivity value.
This matches hipfire. Scopes and iron sights apply their own multiplier on top, and it is not the same one in every game, so a matched hipfire does not guarantee a matched scope. Measure a 360 while aimed down sights if that is what you care about, and run it through the same three steps.