Rust sensitivity converter

1. In the other game, use your usual mouse DPI and hipfire settings. Stand still, face an easy-to-recognise landmark and mark the mouse sensor's starting position on your desk.
2. Move the mouse horizontally until you turn exactly once and face the same landmark again. Keep it flat and pointing in the same direction; do not lift or rotate the mouse during the sweep. Measure the distance the sensor travelled. This is your cm/360, or inches/360.
3. Repeat at least three times and average readings that agree closely. If they vary, check your setup and repeat before calculating. If a full turn does not fit, measure a half turn and double the distance. Keep acceleration off; similar slow and fast movements should give the same turn distance.
4. In Rust, choose the DPI and FOV you intend to play at. Press F1 and enter input.sensitivity to read your current setting. Measure a full turn without aiming down sights or holding freelook.
5. Enter both distances and your current Rust sensitivity above. Apply the suggested setting, then measure again to check that the turn distance matches your target.

Use the same mouse, Rust DPI, FOV and input settings for calibration and the final check. Remeasure if these change. Your other game's DPI can differ: its measured distance already includes that setting.

It matches the physical mouse distance needed for one 360° hipfire turn. It does not promise identical on-screen feel, recoil, aiming-down-sights sensitivity or scope behaviour. Controller input is outside this tool's scope.

The calculation assumes sensitivity scales turning speed proportionally while your Rust setup stays fixed:

new sensitivity = current sensitivity × Rust turn distance ÷ target turn distance

For example, 0.4 sensitivity with a 30 cm turn becomes 0.3 to target a 40 cm turn. The output has six significant digits for entry, but its accuracy depends on your measurements. Always verify it in game.

RustFront has not verified a current universal Rust sensitivity multiplier. We use your measured setup instead of presenting an unverified coefficient as an exact conversion. This also works for games that do not publish their sensitivity scale.

Facepunch's 2019 FOV explanation describes sensitivity scaling with field of view, and its 2021 update introduces a separate ADS multiplier. These explain the limits; they do not certify a current conversion constant.

The physical turn-distance method is described in Mouse Sensitivity in First-person Targeting Tasks (IEEE CoG, 2022, section II.C).