Exact Physical 360° Rotational Distance & Verified Scope Multipliers. Zero bloat, zero paywalls.
When porting your aim from Quake Champions to Rust, direct 1:1 number copying fails because of differences between the Saber3D / id Tech and Unity camera rotation pipelines.
Quake Champions operates at an angular yaw multiplier of 0.022 per mouse count, whereas Rust registers 0.022 per tick.
Mathematical Conversion Ratio: To maintain an identical physical mousepad distance for 360° rotational clearing, multiply your current Quake Champions sensitivity by exactly 1.0000.
input.sensitivity {VAL}
Steam\steamapps\common\Rust\cfg\client.cfg
4 decimal places
Rust emulates Source engine yaw rates in Unity. Can be updated directly via the F1 console.
| Mouse DPI | Target Game Sens | cm / 360° | Feel Bracket |
|---|---|---|---|
| 400 DPI | 1.0000 | 103.9 cm | Ultra-Low (Full Arm) |
| 800 DPI | 1.0000 | 52.0 cm | Ultra-Low (Full Arm) |
| 1200 DPI | 1.0000 | 34.6 cm | Medium (Arm/Wrist) |
| 1600 DPI | 1.0000 | 26.0 cm | Medium (Arm/Wrist) |
| 3200 DPI | 1.0000 | 13.0 cm | High (Wrist / Speed) |
Each game engine defines its own angular displacement per mouse count (yaw). For example, Valorant uses Riot's
calibrated standard of 0.07° per tick, while Source/Source 2 engines (CS2) default to
m_yaw 0.022. AimSync bridges these differing rotational coefficients so your physical mouse
displacement on the desk remains exactly identical.
This calculator preserves hipfire 360° rotational distance, ensuring muscle memory for turning and clearing corners stays intact regardless of FOV.
Engine multipliers are extracted directly from official developer SDKs, engine source repositories (Valve
Source/Source 2 m_yaw 0.022, Riot ShooterEngine 0.07), and verified community
telemetry. Unverified proprietary titles feature the Raw Yaw Override input for direct
empirical adjustment.