FPS sensitivity workflow
FPS sensitivity conversion guide.
The safest way to convert sensitivity is to preserve your physical turn distance first, then test the result in the new game's training range.
The Practical Workflow
- Write down your source game, in-game sensitivity, and mouse DPI.
- Convert that setting into cm/360 so you know the physical distance you are trying to preserve.
- Use a game-aware converter for the target game because each game can use a different yaw value.
- Keep the same DPI if possible during the first test. Change one variable at a time.
- Play a short routine and adjust in small steps if tracking or micro-corrections feel off.
Which Metric Should You Use?
| Metric | Use it for | Main limit |
|---|---|---|
| In-game sensitivity | Changing settings inside one game. | Not comparable across most games. |
| eDPI | Comparing DPI and sensitivity pairs inside the same game. | Does not account for different yaw scales. |
| cm/360 | Comparing physical turn distance across games. | Does not fully describe ADS, scoped modes, or FOV feel. |
For cross-game conversion, cm/360 is the clearest baseline. eDPI is still useful, but mostly inside one game or one sensitivity scale.
Example: CS2 To Valorant
CS2 and Valorant use different yaw values, so copying the same sensitivity number will not preserve the same turn distance. At the same DPI, a common starting formula is:
Valorant sensitivity = CS2 sensitivity x 0.3142857
That means CS2 sensitivity 1.00 at 800 DPI becomes about Valorant 0.314 at 800 DPI. If the target DPI changes, the converter also needs to account for the source DPI and target DPI.
Common Conversion Mistakes
- Copying another player's sensitivity without checking DPI or cm/360.
- Using eDPI alone to compare games with different yaw values.
- Changing DPI, sensitivity, FOV, and ADS multipliers at the same time.
- Expecting scoped sensitivity to match just because hip-fire cm/360 matches.
- Judging a new setting after one bad round instead of testing a repeatable routine.
A Simple 10-Minute Test
- Spend two minutes on slow target tracking.
- Spend two minutes on small flicks and corrections.
- Spend two minutes clearing wide angles or doing large turns.
- Play one short deathmatch or practice round.
- If the setting feels wrong, adjust by 2 to 5 percent and repeat the same test.
If small corrections overshoot, lower sensitivity slightly. If wide turns feel heavy or you run out of mousepad, raise it slightly.
Common Questions
Should every game use the same cm/360?
Not necessarily. The same cm/360 is a useful starting point, but some games may feel better slightly faster or slower because of pacing, FOV, and weapon behavior.
Should I change DPI or in-game sensitivity?
If your desktop DPI already feels comfortable, change in-game sensitivity first. If you change DPI, use a DPI converter to preserve the same effective result.
Why does the converted setting still feel different?
Hip-fire turn distance is only one part of aiming feel. ADS multipliers, scopes, FOV, recoil, movement speed, and input processing can all change the final feel.
Last reviewed: June 1, 2026.