How to Convert Mouse Sensitivity Between Games

A sensitivity of 2.0 in one game and 2.0 in another almost never turn your view the same amount, because each engine multiplies your mouse counts by its own internal constant (the 'yaw'). Valorant's per-unit turn is much larger than CS2's, so Valorant 0.4 is roughly CS2 2.0. The number on the settings screen is meaningless across games — what matters is how far your view actually rotates for a given hand movement.

That's why pros obsess over keeping aim consistent when they switch titles. Muscle memory is built on physical distance — how many centimeters of mouse travel it takes to flick 180°. If that distance changes when you swap games, every shot is recalibrating, and your aim regresses until you re-learn it. Matching the underlying movement, not the on-screen number, is the whole game.

The universal, engine-independent measure is cm/360: the number of centimeters you must move the mouse to turn a full 360°. It's derived from your DPI and the game's sensitivity and yaw, and it's the same physical reality in any game. Two setups with identical cm/360 feel identical, whatever the in-game numbers say. Common values run from ~20 cm/360 (very fast, wrist-heavy) to ~50+ cm/360 (slow, arm-heavy, favored by many pros for precision).

eDPI (DPI × in-game sensitivity) is a related shortcut, but it only compares fairly within the same game, because it ignores the engine's yaw constant. cm/360 folds in DPI, sensitivity, and yaw, so it's the honest cross-game number. Lower your DPI or sensitivity and cm/360 rises (slower, more precise); raise them and it falls (faster, twitchier).

A few games resist clean conversion. Some scale aim with field of view or use a separate ADS (aim-down-sights) multiplier, so hipfire can match perfectly while scoped aim doesn't. Rainbow Six Siege is a well-known example where a config multiplier and FOV scaling make a single converted number insufficient. When a game exposes those extra knobs, convert the base sensitivity first, then fine-tune ADS separately.

Also confirm both games are reading the same raw input — raw input on, mouse acceleration off, and the OS pointer speed at default. Acceleration means the same physical flick travels different distances depending on speed, which quietly destroys the consistency you're trying to build. Get raw input clean first, then the converted number will hold.