Sensitivity Converter

What This Tool Measures: Yaw-Multiplier Translation

Every game engine uses a sensitivity "yaw" multiplier — a value that converts each raw mouse sensor count into degrees of in-game view rotation. Games have wildly different yaw values: CS2 uses 0.022 degrees/count, Valorant uses approximately 0.07 degrees/count, and Overwatch 2 uses a value many times higher. This means that "sensitivity 1.0" in CS2 and "sensitivity 1.0" in Valorant produce completely different physical cursor speeds. To ensure your physical DPI matches your calculated sensitivity multiplier, we suggest you run the full mouse testing suite. Before scaling your sensitivity across different games, run a DPI check to verify your mouse hardware and baseline sensor resolution.

This converter uses each game's known yaw multiplier to calculate the sensitivity value in your target game that produces the identical degrees/count ratio — and therefore the identical physical cm/360° sweep — as your source setting. This is the only mathematically correct way to transfer muscle memory across games. No estimation — the conversion formula is: Target Sensitivity = (Source Sensitivity × Source Yaw) / Target Yaw.

Your DPI is a hardware attribute — verify it with the DPI Test before calculating conversions, since an incorrect DPI assumption makes all derived sensitivity values wrong.

How to Verify Your Conversion Is Correct

After entering your converted sensitivity, verify it physically:

1. Put a piece of tape at the edge of your mousepad.
2. In your source game, memorize how many mousepad-lengths it takes to rotate exactly 360°.
3. In your target game with the converted sensitivity, perform the same rotation — it should take the same physical distance.
4. If it doesn't match, check that your DPI is the same in both games and that Raw Input is enabled in both games (bypassing OS pointer speed).

What Causes Sensitivity to Feel Different After Conversion

1. OS pointer acceleration: If "Enhance Pointer Precision" is enabled in one game but not another, the OS adds a variable speed multiplier on top. Raw Input must be enabled in both games to isolate game sensitivity from OS scaling.
2. Different FoV settings: Horizontal field of view affects how much of the game world a sensitivity unit moves your view across. Same sensitivity but different FoV = different perceived speed. Normalize FoV settings when comparing.
3. Game zoom sensitivity: When aiming down sights (ADS), many games apply an additional sensitivity multiplier. Converted sensitivities only apply to hip-fire — ADS requires a separate conversion if your game supports scoped sensitivity settings.

Preserving Muscle Memory Across Games

The goal of sensitivity conversion is preserving muscle memory — the involuntary motor program your brain has built for a specific physical range of motion producing a specific in-game rotation. After converting:

• Give yourself at least 2–3 days of practice before judging the new sensitivity. Muscle memory partially transfers but needs recalibration time.
• Do not fine-tune by feel in the first session — trust the math and measure cm/360° to confirm.
• Pair with the eDPI Calculator to track your effective sensitivity across any hardware configuration change.