From Overwatch 2 to Valorant
Overwatch uses a small turn per sensitivity point, 0.0066° per mouse count, so its settings run in whole numbers like 4, 5 or 7, while Valorant’s turn per point is about ten times bigger and its settings sit between 0.2 and 1. The example above, Overwatch 5 at 800 DPI, needs 34.6 cm for a full circle and becomes Valorant 0.471.
Hitscan players and projectile players
Tracking heroes such as Soldier: 76 or Tracer usually play faster settings than snipers, because they follow a moving target the whole fight. Valorant fights are short and start from a held angle, which suits slower settings. If you main a tracking hero and the converted Valorant value feels shaky when you hold an angle, try a few percent lower and see whether your first shots get more consistent.
Steps to switch
- Open Overwatch 2’s controls and note the general mouse sensitivity (not a hero’s own value).
- Enter it with your DPI above, then copy the Valorant value.
- In Valorant, type it into Sensitivity: Aim and leave the scoped multiplier at 1 for now.
Going back and forth
Many players keep both games. Note your cm/360 from the result: as long as both games give the same distance, switching between them costs little. Use the swap button to convert from Valorant back to Overwatch, which multiplies by 10.6, and check that you get back to where you started.
Game values and sources
Each game turns the view by a fixed angle for every count the mouse sends (its yaw). These are the hip-fire values the converter uses, checked as of October 2026. The Source and Quake engines' 0.022 is in code Valve and id Software published, and Minecraft's curve is in its decompiled mouse code; the other publishers don't publish theirs, so those values come from the community tables that aim trainers and converters use.
| Game | Turn per mouse count | Sources |
|---|---|---|
| Counter-Strike 2 | 0.022° at 1 | Valve Source SDK, KovaaK's table (mirror) |
| Valorant | 0.07° at 1 | csdb.gg, KovaaK's table (mirror) |
| Overwatch 2 | 0.0066° at 1 | KovaaK's table (mirror), csdb.gg |
| Apex Legends | 0.022° at 1 | KovaaK's table (mirror), csdb.gg |
| Fortnite | 0.005555° per 1% | KovaaK's table (mirror), csdb.gg |
| Call of Duty (MW3, BO6, Warzone) | 0.0066° at 1 | KovaaK's table (mirror), csdb.gg |
| Rainbow Six Siege | 0.005730° per point (0.018 ÷ π) at multiplier unit 0.02 | KovaaK's table (mirror), Ubisoft |
| Rust | 0.1125° at 1 | KovaaK's table (mirror), csdb.gg |
| Minecraft (Java Edition) | 1.2 × (0.6 × setting ÷ 200% + 0.2)³ degrees | Minecraft code |
| Deadlock | 0.044° at 1 | KovaaK's table (mirror), skin.club |
| Team Fortress 2 | 0.022° at 1 | Valve Source SDK |
| Quake Champions | 0.022° at 1 | KovaaK's table (mirror), Quake III source |
- CS2: The same scale as CS:GO: the "sensitivity" setting, at the default m_yaw 0.022.
- Valorant: Valorant turns 3.18 times as far per count as CS2 at the same number (KovaaK's uses 0.06996, 0.06% apart).
- Overwatch 2: Hip-fire sensitivity; per-hero and relative aim sensitivity while zoomed are separate settings.
- Apex: Hip-fire mouse sensitivity, on the same scale as CS2. ADS multipliers are separate.
- Fortnite: The X-axis sensitivity in percent, as the menu shows it (6.5%, not 0.065). Set Y to the same value for the same feel up and down.
- Call of Duty: Hip-fire mouse sensitivity; Legacy or Relative only change aiming down sights.
- Siege: Horizontal mouse sensitivity, a whole number from 1 to 100, scaled by MouseSensitivityMultiplierUnit in GameSettings.ini (default 0.02).
- Rust: The look sensitivity in Options; aim sensitivity is separate.
- Minecraft: The slider is not linear: the turn grows with the cube of the setting. Bedrock Edition uses another scale.
- Deadlock: KovaaK's table and skin.club give 0.044°, twice CS2's turn at the same number; csdb.gg lists 0.022 instead, so check a full turn in game.
- TF2: Source engine: the same scale as CS2 and Apex.
- Quake Champions: The same 0.022 yaw as Quake III, Quake Live and Source games.