Pick your main game & DPI
Select the FPS where your aim already feels dialed in, then enter your in-game hipfire sensitivity and mouse hardware DPI.
FPS Aim Math & Muscle Memory
Convert hipfire sensitivity accurately across CS2, Valorant, Apex Legends, Overwatch 2, Rainbow Six Siege, Fortnite and Marvel Rivals with transparent engine yaw constants, DPI scaling and physical cm/360° distance.
Choose your source and target games. Different mouse DPI settings between games are scaled automatically.
2 × (0.022° ÷ 0.07°) × (400 ÷ 400) = 0.6286
Exact 6-decimal value: 0.628571
| Game / Engine | Hipfire Yaw | Converted Sens (at Target DPI) | Game eDPI | Copy |
|---|
Exact 360° hipfire yaw conversion — perceived on-screen cursor speed still varies with Field of View (FOV), 4:3 stretched aspect ratios, ADS/scope zoom multipliers, raw input settings and OS pointer acceleration ("Enhance pointer precision").
Three simple steps
Select the FPS where your aim already feels dialed in, then enter your in-game hipfire sensitivity and mouse hardware DPI.
Choose the game you are switching to. If you also changed mouse DPI (for example 400 to 1600 DPI), enter the new Target DPI.
Copy the rounded or 6-decimal sensitivity into your game settings, check your cm/360° desk space, and warm up in Aim Trainer.
Why transparent yaw math
Every game engine translates raw USB mouse counts into camera rotation degrees using a documented yaw constant.
Displays exact deg/count constants (0.022° Source/Apex, 0.07° Valorant, 0.0066° OW2/CoD) so you can verify every calculation by hand.
Upgrading from 400 DPI to 1600 DPI for lower input latency? Convert both game engine and hardware DPI in one step while keeping identical cm/360°.
Any Unreal, Unity, Source or custom shooter works via Custom Yaw mode without waiting for database updates.
Competitive setup tips
Mathematical conversion only matches in-game turns when the OS and game read raw sensor counts without curve distortion.
FAQ
CS2 uses a Source engine hipfire yaw of 0.022 degrees per mouse count, while Valorant uses 0.07 degrees per count. At the same mouse DPI, multiply your CS2 sensitivity by 0.022 / 0.07 (or divide by 3.181818). For example, CS2 sensitivity 2.0 at 400 DPI equals 0.629 in Valorant (51.95 cm/360°).
eDPI (effective Dots Per Inch) equals Mouse DPI multiplied by In-Game Sensitivity. It lets two players in the SAME game compare true aim speed regardless of whether one uses 400 DPI and the other uses 1600 DPI. Because different engines use different yaw constants, eDPI values cannot be compared across different games — use cm/360° for cross-game comparison.
cm/360° is the exact physical horizontal distance in centimeters your mouse must travel across the mousepad to rotate your character a full 360 degrees in hipfire. Competitive tactical shooter players typically play between 35 cm/360° and 65 cm/360° (arm/hybrid aim), whereas fast tracking shooters like Overwatch 2 or Apex often sit between 24 cm/360° and 42 cm/360°.
cm/360° matches physical 360-degree turn distance, not visual pixel velocity near the crosshair. Differences in Field of View (such as Valorant's locked 103° horizontal FOV versus CS2's 106.26° on 16:9), aspect-ratio stretching (4:3 stretched), ADS zoom multipliers, and Windows pointer acceleration ('Enhance pointer precision') change perceived screen speed.
Choose 'Custom Yaw (deg/count)' in either the Source or Target selector and enter the engine's degrees-per-count constant (for example 0.022 for Source/id Tech derivatives). All cm/360°, in/360° and DPI conversions will compute with full floating-point precision locally.
Continue with a related tool or explore the matching guide.