What you need
- A mousepad with enough room for repeatable 360-degree turns.
- A ruler or marked distance reference.
- A fixed hip-fire test scene with a stable starting camera position.
- A way to record your mouse model, DPI, polling rate and input settings.
- A notebook, spreadsheet or video capture for raw observations.
Record the environment first
Write down the game and patch release, operating system, mouse model, firmware, driver, active DPI, polling rate, Windows pointer speed and any acceleration or smoothing options. Record the in-game sensitivity and input settings. Without this context, a measured distance is difficult to reproduce or interpret.
If the active DPI is unknown, check your mouse DPI before running the trials. Record the measured value alongside the rest of the environment notes.
Measure a full turn
- Mark the starting mouse position on the pad.
- Place the camera at a fixed starting point and avoid moving the character.
- Turn exactly 360 degrees using hip-fire mouse movement.
- Mark the ending mouse position and measure the distance in centimeters.
- Repeat the turn in the opposite direction.
- Run several trials at each sensitivity value and record every valid result.
Discard a trial only for a recorded reason, such as slipping off the pad, hitting an obstacle or accidentally moving the camera vertically beyond the test setup.
Calculate the result
To calculate the implied base yaw from the measured distance:
Repeat the test at several sensitivity values. If the game is linear and the yaw is stable, the implied base yaw should remain within your measurement tolerance. A large spread suggests a measurement problem, acceleration, non-linear behavior or a varying input path.
Test a converted sensitivity
Apply the converted value in the target game, then repeat the 360-degree test. Compare the measured distance with the source game’s distance. Do not adjust the value just because the first flick feels different; check whether the physical turn distance is actually different.
If the distance is consistently off, check DPI, input settings, FOV, ADS state and game version before changing the conversion. The cm/360 guide explains the formula, and the conversion guide explains the assumptions.
Report uncertainty honestly
A single trial is not strong evidence. Record the number of valid trials, the mean distance, the spread and your measurement uncertainty. A result from one tester is useful research; independent replication is stronger. Do not present a rough measurement as an established game constant.
Try the converter
The converter uses the loaded game records. Treat every result as an estimate, because FOV and input behavior are not modeled.
Open the sensitivity converterRelated guides
Related resources
Last reviewed: 2 November 2026