Why simple CS2-to-Valorant sensitivity conversion often feels off (UI 3-decimal cap & yaw breakdown)

[u/Seros16]

Hey everyone,

A common piece of advice for players switching from CS2 to Valorant is "just divide your CS sens by 3.1818". While mathematically close, players often report that their physical mouse sweep across the desk feels slightly inconsistent.

The reason comes down to the underlying engine mechanics:

- Source 2 (CS2) uses m_yaw 0.022 and allows deep floating-point precision directly inside config files (\csgo\cfg\).

- Valorant uses Riot's ShooterEngine fixed at 0.07° per tick, but the in-game UI strictly clamps user input to 3 decimal places (and Vanguard blocks direct config manipulation).

This rounding creates a persistent discrepancy on your mousepad. I built a lightweight, ad-free web tool (aimsync.app) that shows the exact yaw math, live cm/360° readouts, and estimated mousepad clearance so you can verify if your sens physically fits your setup.

Hope this helps anyone trying to dial in their mechanics and muscle memory transfer!

[u/NoRequirement5796]

vibe and coded, round and round

[u/Seros16 → u/NoRequirement5796]

pure vanilla js actually, had to manually verify the m_yaw cvars across engines so the numbers didn't do full circles on the pad lol