Mouse cm per 360 Calculator
A mouse cm per 360 calculator estimates how far you need to move your mouse across your desk to turn a full circle in a game. The measurement, often called cm/360, gives PC gamers a useful way to describe horizontal sensitivity in physical terms.
Two games can use very different sensitivity scales, so entering the same number in both does not necessarily produce the same turning speed. By combining your mouse DPI, in-game sensitivity multiplier, and the game’s yaw coefficient, this calculator estimates the physical distance behind a complete 360-degree turn.
What the Mouse cm per 360 Calculator does
The Mouse cm per 360 Calculator converts your mouse and game settings into an estimated Distance per 360°, displayed in centimeters. A lower result means less physical mouse movement is needed to turn around. A higher result means you need to move the mouse farther for the same rotation.
For example, a result of 25 cm means that, under the calculator’s assumptions, moving your mouse 25 centimeters horizontally would rotate your view by 360 degrees. A result of 50 cm means the same full turn would require twice as much physical movement.
The calculation assumes raw mouse input, a constant horizontal sensitivity, and no mouse acceleration. It also assumes the yaw coefficient you enter accurately describes how your game converts mouse counts into horizontal rotation. The default yaw value is an illustrative Source-engine value, so check your own game’s settings or documentation before relying on it.
How to use the Mouse cm per 360 Calculator
Enter the three values used by your mouse and game:
- Mouse DPI: Enter your mouse’s dots per inch setting. The calculator treats DPI as mouse counts per inch. For example, enter 800 if your mouse is configured to use 800 DPI.
- In-game sensitivity multiplier: Enter the horizontal sensitivity multiplier used by your game. The default is 1, but the appropriate value depends on your settings and how the game applies sensitivity.
- Yaw coefficient: Enter the number of degrees the game rotates horizontally per mouse count at a sensitivity of 1. The default of 0.022 is an illustrative assumption, not a universal value for every game.
Read the result labeled Distance per 360°. It is shown in centimeters and rounded to two decimal places. You can then change an input to see how a different DPI, sensitivity, or yaw coefficient affects the estimated distance.
If you are unsure of your mouse DPI, check its configuration software, onboard profile, or product documentation. For the yaw coefficient, consult the game’s settings or documentation. If you cannot verify the coefficient, treat the result as an estimate based on the value you entered.
How the Mouse cm per 360 Calculator formula works
The formula combines the number of mouse counts generated per inch with the amount of rotation produced by each count:
Distance per 360° in cm = (360 × 2.54) ÷ (mouse DPI × in-game sensitivity multiplier × yaw coefficient)
First, multiplying DPI by the sensitivity multiplier and yaw coefficient gives the estimated degrees of horizontal rotation per inch of mouse movement. Dividing 360 by that number gives the distance in inches. Multiplying by 2.54 converts inches to centimeters.
Worked example using the default settings
Assume a mouse DPI of 800, an in-game sensitivity multiplier of 1, and a yaw coefficient of 0.022 degrees per mouse count at sensitivity 1. The yaw value is an illustrative assumption for this example.
- Calculate degrees per inch: 800 × 1 × 0.022 = 17.6 degrees per inch.
- Calculate the distance for a full turn: 360 ÷ 17.6 = approximately 20.45 inches.
- Convert to centimeters: 20.45 × 2.54 = approximately 51.95 cm.
The calculator therefore displays 51.95 cm for Distance per 360°. The actual calculation retains the unrounded values before displaying the result to two decimal places.
Each input has an inverse relationship with the result. If you double the DPI while keeping the other two values unchanged, the estimated cm/360 is halved. The same relationship applies if you double the sensitivity multiplier or the yaw coefficient, provided the game follows the linear model used by the calculator.
Use cases for the Mouse cm per 360 Calculator
Compare sensitivity between games
Games often present sensitivity settings on different scales. Calculating cm/360 can help you compare the physical distance needed for a full horizontal turn. Use the correct yaw coefficient and sensitivity multiplier for each game, then compare the results. Matching the estimates can be a useful starting point, although game-specific input behavior may still produce differences.
Adjust a new mouse
If you change to a mouse with a different DPI setting, the calculator can help you understand how that change affects turning distance. For instance, doubling DPI without changing the in-game multiplier halves the estimated distance. You can then adjust the multiplier and recalculate until you reach a distance close to your preferred setting.
Plan your mousepad space
Your estimated cm/360 can help you judge how much horizontal room a particular sensitivity may require. You do not always need to perform a full turn in one uninterrupted movement, but knowing the distance can help you compare a sensitivity with the usable width of your mousepad.
Experiment with aiming preferences
Some players prefer shorter mouse movements, while others prefer more physical travel for a given turn. Recording your settings and estimated cm/360 can make those experiments easier to compare. The calculator describes the movement distance; it does not determine which sensitivity will feel best for you.
Other factors to consider when calculating Distance per 360°
Mouse acceleration can change the relationship between physical movement and on-screen rotation depending on how quickly you move the mouse. The calculator assumes acceleration is absent, so its result may differ from your experience if acceleration is enabled.
Input handling also matters. The formula assumes raw mouse input. Operating system settings, software processing, or non-raw input may alter the movement information a game receives.
Game-specific sensitivity transformations can affect the estimate. Some games may apply their displayed sensitivity through a different scale or use separate settings in different situations. Make sure the multiplier and yaw coefficient you enter describe the horizontal movement you want to calculate.
Actual mouse movement can vary from the estimate. The configured DPI may not perfectly match the effective movement registered by a particular mouse and surface. You can compare the result with a practical measurement by moving the mouse horizontally while observing the in-game turn, allowing for the difficulty of stopping at exactly 360 degrees.
Finally, remember that cm/360 describes horizontal rotation. It does not by itself describe vertical sensitivity, field of view, scoped aiming behavior, or how comfortable a setting feels during play.
Mouse cm per 360 Calculator FAQ
What does cm per 360 mean?
It is the physical distance, measured in centimeters, that you move your mouse to rotate your view horizontally by 360 degrees. A lower number indicates a faster turn for the same physical mouse movement.
Does a higher DPI lower my cm/360?
Yes, if the in-game sensitivity multiplier and yaw coefficient remain unchanged. In this calculator’s linear model, doubling DPI cuts the estimated cm/360 in half.
Can I use the default yaw coefficient for every game?
No. The default value of 0.022 is illustrative. Games can use different yaw coefficients or sensitivity calculations, so use a value supported by your game’s settings or documentation whenever possible.
Will matching cm/360 make two games feel identical?
Not necessarily. Matching the estimated horizontal turning distance is a useful starting point, but input processing, field of view, acceleration, and game-specific sensitivity behavior can still affect how aiming feels.
Why is my measured distance different from the calculator result?
The entered yaw coefficient or sensitivity multiplier may not match the game’s actual behavior. Mouse acceleration, non-raw input, DPI variation, and measurement error can also cause differences. Check the inputs and assumptions, then compare the estimate with an in-game measurement.