To measure your cm/360, place a ruler beside your mouse, aim at a fixed point in a game, and move the mouse horizontally until your camera completes one full turn. The distance the mouse travels in centimeters is your cm/360. Repeat the measurement to check that the result is consistent.
For example, if one complete turn requires 32.5 centimeters of mouse movement, your sensitivity is approximately 32.5 cm/360.
You do not need to know the game’s sensitivity formula to measure this distance. You do need a repeatable starting point, a clear endpoint, and unchanged settings.
This guide covers horizontal mouse-driven camera rotation in a 3D game, not desktop cursor movement or controller sensitivity.
What Does cm/360 Mean?
cm/360 means centimeters of mouse movement per 360-degree camera rotation. It describes the physical distance required to turn all the way around and face the same direction again.
A lower number means less mouse travel for the same turn. A higher number means more travel.
| Sensitivity measurement | Mouse travel for one full turn | Interpretation |
|---|---|---|
| 20 cm/360 | 20 centimeters | Less travel; higher turning sensitivity |
| 40 cm/360 | 40 centimeters | Twice the travel of 20 cm/360 |
| 60 cm/360 | 60 centimeters | Three times the travel of 20 cm/360 |
These are illustrative distances, not recommended sensitivity ranges.
Ubisoft uses the same physical-distance definition in its technical explanation of 360 distance and ADS sensitivity. That source also explains why matching turn distance does not necessarily preserve the same visual experience at different zoom levels.
The practical benefit is straightforward: you can compare how far your hand moves instead of comparing sensitivity numbers that may mean different things in different games.
What You Need Before Starting
Use a ruler or measuring tape with clear markings, your usual mousepad, and a practice area where you can stand still and rotate the camera freely.
A small removable marker beside the mouse’s path can help you record its starting position. Keep it away from the sensor and sliding surface.
Before measuring, note your game, active DPI if known, sensitivity, and aiming mode. Start with ordinary hip-fire, meaning you are not aiming down sights.
Keep the same mouse profile, surface, and settings throughout the test. Logitech’s G HUB DPI documentation confirms that DPI settings can differ between profiles, so the profile active inside your game matters.
You can still measure cm/360 without knowing your DPI. Recording it simply makes the result easier to reproduce later.
How to Measure cm/360: The Full-Turn Method
1. Choose a stationary reference point
Enter a practice range or private environment and stop moving your character.
Aim at something easy to identify precisely: a vertical wall edge, a narrow line, or a small stationary detail. Avoid a moving character, swaying object, or wide surface with no clear center.
The endpoint should be obvious when you return to it. A fixed reference and a repeatable full rotation are also used in KovaaK’s sensitivity-matching procedure, although its software-based method differs from the manual ruler method here.
2. Position the ruler beside the mouse
Lay the ruler parallel to the direction you will move the mouse. Keep the mouse on its normal surface rather than moving it onto the ruler.
Choose one consistent reference point on the mouse body, such as a clearly defined corner. Use that same point for both the starting and ending readings.
You do not have to line up the optical sensor with zero. A fixed point on the shell can track displacement, provided you slide the mouse straight without rotating it.
3. Record the starting position
Leave enough room for the sweep and write down the starting reading.
Starting at zero is convenient, but it is not required. For example, you could begin with your chosen mouse reference point aligned at 5.0 cm.
Do not move the mouse between aligning the crosshair and recording the starting position.
4. Complete one horizontal turn
Slide the mouse steadily in one direction until the camera rotates through one complete turn and the crosshair returns to the original reference.
Keep the mouse flat and maintain its orientation. Avoid lifting, twisting, or following an arc.
Do not walk your character or change aiming modes during the measurement. If you clearly overshoot, restart the trial rather than making several corrections and treating the result as precise.
Count the rotation carefully. Returning to a similar-looking part of the map is not necessarily the same as completing exactly 360 degrees.
5. Subtract the starting reading from the ending reading
Once the crosshair is back on the reference, stop moving and read the ruler.
Mouse travel = Ending position − Starting position
For example:
37.4 cm − 5.0 cm = 32.4 cm
Because that movement produced one complete camera rotation, the result is approximately:
32.4 cm/360
Measure the movement of the same point on the mouse—not the gap between different edges of its body.
6. Repeat before recording your final result
Three clean trials are a practical starting point. Keep the settings and measurement technique unchanged.
If the readings are close together, calculate their average. If they differ noticeably, troubleshoot the setup before averaging them.
Do not discard a reading simply because it disagrees with a calculator. Repeat trials when you can identify a procedural problem, such as an accidental lift or a missed endpoint.
Worked Example: Averaging Three Measurements
The following readings are illustrative examples, not hardware test results.
| Trial | Measured travel for 360° |
|---|---|
| First | 32.4 cm |
| Second | 32.6 cm |
| Third | 32.5 cm |
Calculate:
Average cm/360 = Sum of the measured distances ÷ Number of trials
(32.4 + 32.6 + 32.5) ÷ 3 = 32.5 cm/360
A useful note would be:
Hip-fire sensitivity: approximately 32.5 cm/360. Three trials measured 32.4–32.6 cm using the same mouse, profile, and surface.
The average is a summary of your measurements, not proof of laboratory accuracy. Keep the precision realistic: a ruler test does not justify reporting a result such as 32.500000 cm/360.
How to Measure cm/360 on a Small Mousepad
You do not need to change sensitivity just because a full turn exceeds the space available. Use one of these alternatives.
Option 1: Measure a known 180-degree turn
If you can identify an accurate half-turn, measure the distance required and multiply it by two:
Estimated cm/360 = Distance for 180° × 2
For example:
16.25 cm × 2 = 32.5 cm/360
The important word is known. Use an adequately precise heading display or reference directions that are genuinely opposite each other. Two arbitrary objects on the map do not establish a 180-degree angle.
Under a constant movement-to-rotation relationship, the more general calculation is:
Estimated cm/360 = Measured distance × 360 ÷ Measured angle
Guessing the angle introduces error into the result. When you cannot establish a reliable half-turn, use the segmented method instead.
Option 2: Measure one full turn in separate strokes
You can also divide the movement into multiple measured strokes.
Move in one direction, record the distance, then lift and reposition the mouse without changing the camera direction. Continue turning in the same direction until you complete one full rotation and return to the original reference.
Add only the movement that occurred while the mouse was tracking:
20 cm + 20 cm + 5 cm = 45 cm/360
Do not include the distance traveled while lifting and repositioning the mouse.
Watch the camera during each reset. If it moves while you lift or put the mouse down, repeat the trial. This method adds more opportunities for measurement error, so compare several attempts.
The advertised width of your mousepad is not the same as your usable swipe distance. Your starting position, mouse footprint, keyboard, and other obstacles reduce the space available.
Measuring in Inches Instead of Centimeters
An inch-marked ruler works too. Measure the distance for a full turn, then convert it:
cm/360 = Inches per 360 × 2.54
For example:
12 inches × 2.54 = 30.48 cm/360
To convert the other way:
Inches per 360 = cm/360 ÷ 2.54
The conversion is exact: one inch equals 2.54 centimeters, as documented in NIST’s unit-conversion tables. Your physical measurement still has the limitations of the ruler and method you used.
Why Your cm/360 Readings May Be Inconsistent
Before changing your sensitivity, check how you performed the measurement.
| Possible issue | What to check |
|---|---|
| The endpoint changes between trials | Use a narrow stationary detail and return to the same alignment. |
| The mouse turns or follows a curved path | Keep its orientation fixed and slide straight beside the ruler. |
| You use different points on the mouse | Read the same reference point at the start and end. |
| The mouse lifts during a continuous trial | Restart, or deliberately use the segmented method. |
| A different DPI profile becomes active | Confirm the profile and DPI stage used while the game is running. |
| Hip-fire and scoped measurements are mixed | Test each aiming mode separately and label the results. |
Mouse acceleration can make the result speed-dependent
A single, repeatable cm/360 value assumes a consistent relationship between mouse travel and camera rotation.
With acceleration, movement speed or input magnitude can change the response. A slow sweep and a fast sweep may therefore produce different turn distances.
Valve’s public mouse-input implementation provides an example of separate acceleration calculations and ordinary sensitivity scaling. It is evidence of how such behavior can be implemented—not a description of every game.
For a non-accelerated baseline, use the appropriate settings for your game and input software. To document an accelerated setup, record that acceleration is enabled and compare movement speeds separately.
Do not combine slow and fast accelerated trials into one supposedly universal measurement.
Windows cursor movement is not an in-game measurement
Moving your desktop pointer from one side of the screen to the other does not tell you how far your game camera rotates.
Microsoft’s RAWMOUSE documentation states that Raw Input mouse events are not affected by the Windows Control Panel mouse-speed setting. For a game using that input path for aiming, desktop pointer speed is not a reliable proxy for camera sensitivity.
Perform the test inside the game, not in its menu or on the desktop.
Measured cm/360 vs. a Calculator Result
A calculator predicts turn distance from its inputs and the game model it implements. A ruler measurement checks what happens when you move your mouse in the actual setup.
Those are related checks, but they are not identical.
A difference does not automatically prove that the calculator is wrong, the mouse is defective, or your measurement is accurate. Check the entered DPI, sensitivity format, aiming mode, rounding, and supported game settings first.
Game-specific rotation factors also matter. KovaaK’s explanation of yaw and sensitivity describes why the same sensitivity number can produce different turning behavior in different games.
For supported game conversions, use GamingStation’s mouse sensitivity converter as a starting point, then verify the result with the same measurement procedure.
Keep the result tied to its context: game, mode, DPI profile, sensitivity, and any relevant modifiers.
Does the Same cm/360 Feel Identical in Every Game?
No. Matching cm/360 matches physical mouse travel for a camera rotation. It does not guarantee identical screen-space movement or aiming feel.
Zoom is an important example. The same angular rotation can look much larger through a magnified view. Ubisoft’s discussion of 360 distance and visuomotor gain explains this distinction. Its 2020 guide is referenced here for the concept, not as a current settings prescription.
Keep FOV and aiming mode unchanged when comparing measurements inside one game. Some implementations also connect input scaling to FOV, so avoid assuming that changing FOV can never affect turn distance.
Measure hip-fire and scoped settings separately when you need both.
How to Use Your Measurement
Keep the same turn distance after changing DPI
Measure your current setup before changing DPI. Apply the appropriate sensitivity adjustment, then measure again under the same conditions.
GamingStation’s guide to changing DPI without changing in-game sensitivity explains that calculation and its limitations.
Your before-and-after readings should be reasonably consistent when the supported linear model and relevant settings remain the same.
Adjust toward a different turn distance
Within the same game and aiming mode, with a linear sensitivity setting, unchanged DPI, and other modifiers fixed:
New sensitivity = Current sensitivity × Current cm/360 ÷ Target cm/360
Suppose your current sensitivity is 0.4, your measurement is 40 cm/360, and you want 32 cm/360:
0.4 × 40 ÷ 32 = 0.5
The calculated starting point is 0.5 sensitivity.
That direction makes sense: reducing the required travel from 40 cm to 32 cm requires higher sensitivity.
This calculation inherits any error in your original measurement. Apply the closest supported value and measure again. Do not use the displayed-number ratio blindly with a nonlinear slider.
Save a baseline you can reproduce
Record the result alongside your settings rather than saving only a sensitivity number.
A useful record includes the game, aiming mode, mouse profile, DPI if known, sensitivity, measured distances, and any acceleration or scope settings.
That gives you a meaningful comparison point after a settings reset or configuration change.
Frequently Asked Questions
Can I measure cm/360 without knowing my DPI?
Yes. The manual method measures mouse travel and camera rotation directly. You do not need a DPI value to read that distance.
However, cm/360 alone does not identify your mouse’s hardware DPI. It reflects the combined response of the mouse and game configuration.
Is higher or lower cm/360 better?
Neither number proves that a setup is better.
A higher value requires more movement for the same turn; a lower value requires less. Use the measurement to describe and compare settings, then assess whether the setup is comfortable and practical for your play.
Can I measure cm/360 without a ruler?
You need a known physical distance for a result in centimeters. A measuring tape or another reliably measured reference can substitute for a ruler.
Without a physical scale, you may compare two settings approximately, but you cannot establish a dependable distance in centimeters simply by watching the screen.
Should I measure while aiming down sights?
Measure hip-fire first for a clearly labeled baseline. Then measure the scoped mode separately when needed.
Keep the same optic and zoom level throughout a scoped test. Do not mix scoped and hip-fire readings into one average.
Do I have to complete the full turn in one swipe?
No. A known 180-degree measurement can be doubled, or measured tracking strokes can be added until they complete one full turn.
For segmented measurements, exclude airborne repositioning and make sure the camera does not move during the reset.
The Bottom Line
Measure the mouse movement—not the desktop cursor—and use a fixed in-game reference.
Complete one horizontal turn, subtract the starting ruler reading from the ending reading, and repeat the test. On a small mousepad, use an accurately identified half-turn or carefully measured segments.
A useful result is not the number with the most decimal places. It is the one you can reproduce under the same settings and measurement conditions.
References
| Source | Relevance to this guide |
|---|---|
| Ubisoft — Guide to ADS Sensitivity in Y5S3 | Defines 360 distance and explains its distinction from visual consistency across zoom levels. Historical conceptual reference. |
| KovaaK — Sensitivity Matcher | Explains game-specific yaw factors and verification using a fixed reference and full camera rotation. |
| Logitech — G HUB: Remove and Create DPI Speeds | Documents profile-specific DPI settings. |
| Valve — Source SDK Mouse-Input Implementation | Provides an implementation example of sensitivity scaling and acceleration. |
| Microsoft — RAWMOUSE Documentation | Explains the distinction between Raw Input and Windows pointer-speed settings. |
| NIST — Unit Conversion Factors | Supports the inch-to-centimeter conversion factor. |
Method note: This is a research-based measurement guide. The numerical examples are illustrative calculations, not independent mouse tests or current-build calibration results. Manual readings depend on the equipment, input behavior, and measurement technique.
