SensScale.
ENGINE ARCHITECTURE 7 min read • 2026-10-06

The Mathematics of Mouse Sensitivity: Engine Camera Yaw & cm/360 Explained

Why copying raw sensitivity between games breaks muscle memory, and how 3D engines scale hardware counts into angular rotation using hardcoded yaw multipliers.

S
SensScale Engineering Sub-Pixel Parity & Yaw Verification Desk

When competitive players migrate from Valorant to Counter-Strike 2 or Apex Legends, the most common mistake is assuming that an in-game sensitivity slider value of 0.35 represents a universal unit of measurement. It does not. An in-game sensitivity value is merely an arbitrary multiplier applied to your mouse's hardware count stream before passing it through an engine-specific camera yaw constant.

1. The Raw Input Pipeline: From Sensor to Screen

Every modern optical gaming mouse communicates with your operating system by sending rapid coordinate updates (often 1000Hz, 4000Hz, or 8000Hz polling rate). Each unit of physical movement detected by the sensor is registered as a single discrete count (commonly referred to as a 'dot' in DPI).

When raw mouse input is enabled in a modern FPS engine, the game bypasses Windows Pointer Ballistics (Enhanced Pointer Precision) and captures raw count deltas:

// 3D Camera Rotation FormulaΔAngle (Degrees) = Mouse Counts × In-Game Sensitivity × Engine Yaw Constant

2. Hardcoded Engine Yaw Constants

Different game engines scale camera rotation using vastly different internal yaw values. Valve's Source and Source 2 engines have historically used 0.022° per count, whereas Riot Games configured Valorant's Unreal Engine 4 implementation to use 0.070° per count.

Game EngineFlagship TitlesCamera Yaw (Degrees/Count)Ratio to Source (CS2)
Source 2 / GoldSrcCS2, CS:GO, Team Fortress 20.022000°1.000x
Unreal Engine 4 (Riot)Valorant0.070000°3.1818x
Respawn Source ForkApex Legends, Titanfall 20.022000°1.000x
Tank EngineOverwatch 20.006600°0.300x
IW Engine (Modern)Call of Duty: Warzone, MW30.006600°0.300x
AnvilNext 2.0Rainbow Six Siege0.005729578°0.2604x

3. The Conversion Formula

To preserve exact 1:1 camera rotation between two games without altering your mouse's hardware DPI, the target in-game sensitivity must be scaled by the ratio of the two engine yaw constants:

// SensScale True Yaw Equivalence
Target Sens = Source Sens × (Source Yaw / Target Yaw) × (Source DPI / Target DPI)

Example: Converting 0.35 Valorant Sens (@ 800 DPI) to CS2 (@ 800 DPI):
CS2 Sens = 0.35 × (0.070 / 0.022) × (800 / 800) = 0.35 × 3.181818 = 1.1136

4. The Physical Metric: cm/360° Physical Distance

While sensitivity numbers and eDPI fluctuate wildly between titles, physical distance is immutable. cm/360° measures the precise distance in centimeters your mouse must travel across your mousepad to execute a complete 360-degree rotation of the in-game camera.

cm/360° Formula:
cm/360° = (360 × 2.54) / (Sensitivity × Yaw Constant × DPI)
= 914.4 / (Sens × Yaw × DPI)

For instance, a Valorant player using 0.35 @ 800 DPI requires exactly 46.65 cm to turn 360 degrees. Applying 1.1136 in CS2 yields the exact same 46.65 cm/360°, locking muscle memory and arm motor unit recruitment into permanent parity.

ZERO GUESSWORK • SUB-PIXEL CALIBRATION

Ready to convert?

Put this mathematical model into practice. Match your exact cm/360° distance and camera yaw rotation across 120+ competitive shooters in under 5 seconds.

[CONTINUE EXPLORING GUIDES]

View All →