To keep the same physical mouse movement when switching shooting games, match your cm/360, not just your eDPI. Muscle memory is the learned feel of repeating a movement, so keeping the physical turn distance steady gives your aim a stable baseline. eDPI equals mouse DPI multiplied by in-game sensitivity, so it is useful for comparing settings inside one compatible game scale. Across different titles, use a yaw-aware cm/360 calculation or a verified game-specific converter, then test one full rotation in the target game.
This method gives you a repeatable physical baseline. It does not promise identical visual feel, because field of view, aspect ratio, movement, animations, and input behavior can still differ between games.
Use eDPI Within a Game; Use cm/360 Across Games
Use eDPI for same-game arithmetic, but use cm/360 for a cross-game transfer. Do not copy a reference game's eDPI into another title unless its sensitivity scale and input assumptions are verified as compatible.
For Same-Game Comparisons
eDPI = mouse DPI × in-game sensitivity. If your mouse DPI stays fixed, raising the in-game sensitivity raises the eDPI by the same relationship. If you change DPI while leaving the slider untouched, the eDPI changes as well.
That product is a convenient shorthand when the game's scale remains the same. It does not tell you that an eDPI value has the same physical meaning in another game.
For Cross-Game Transfers
The cross-game target is a physical distance: how far the mouse must travel for a nominal 360-degree turn. That is what cm/360 represents. To calculate eDPI across different games in a meaningful way, first convert each title to a comparable physical distance using its own sensitivity interpretation and yaw value.
Use a verified converter or documented game data when the receiving game's scale is unclear.
Transfer calculation checklist:
- Keep the DPI you plan to use active.
- Carry your reference cm/360 into the target game.
- Verify the target game's yaw or use a converter that documents its scale.
- Solve for the target sensitivity, or keep the result symbolic if the required value is not verified.
Separate Mouse DPI From In-Game Sensitivity
DPI and in-game sensitivity are related, but they are not the same setting. Record both from your reference setup before you measure or convert anything.
DPI Is the Mouse-Side Input
DPI describes the mouse's counts per inch setting. For this calculation, the practical value is the active DPI reported by the mouse, software, or hardware profile. Write down the value that is actually active before changing profiles or starting a test.
DPI is one of the inputs in both eDPI arithmetic and the cm/360 formula. If you change it later, the old calculation no longer describes the same setup unless you recalculate the in-game sensitivity.
Sensitivity Is the Game-Side Input
In-game sensitivity is the value the title applies to mouse input. A slider value belongs to that game's scale, so 0.5 in one game is not automatically equivalent to 0.5 in another.
For a reference setup, record the active DPI and the reference sensitivity together. eDPI combines them for a same-game comparison. cm/360 adds the title-specific yaw information needed to connect those settings to a physical turning distance.
Calculate a Reference cm/360
Calculate your reference distance from the active DPI, reference sensitivity, and verified yaw value. The yaw-based method is cm/360 = (360 × 2.54) / (DPI × sensitivity × yaw), as shown in the yaw-based cm/360 formula.
The 2.54 factor converts inches to centimeters.
Gather the Four Inputs
Use these inputs before running the calculation:
- Active mouse DPI: Record the DPI currently used by the mouse.
- Reference-game sensitivity: Record the exact in-game value from the setup you want to preserve.
- Reference-game yaw: Obtain the title's yaw from a verified technical reference or game-specific converter. It is not a universal value.
- Centimeter conversion: Use 2.54 centimeters per inch in the formula.
If the yaw value is unknown or unverified, stop the numeric calculation rather than guessing. Use a verified game-specific converter or technical reference instead.
Run One Labeled Example
Illustrative calculation only: assume 800 DPI, a sensitivity of 0.5, and a hypothetical yaw of 0.022. These values are supplied to demonstrate the arithmetic, not to represent a typical setting or a game-specific preset.
cm/360 = (360 × 2.54) / (800 × 0.5 × 0.022)
cm/360 = 914.4 / 8.8 ≈ 103.9 cm/360
Under those illustrative inputs, the reference distance is approximately 103.9 centimeters for a nominal 360-degree turn. For your real setup, replace every value with the verified inputs from your reference game.
Transfer the Same cm/360 to Another Game
Transfer the physical distance, not the raw sensitivity number. Keep the chosen DPI active during the transfer unless you intentionally change it and recalculate with the new value.
Solve for the Target Game's Sensitivity
Use your reference cm/360 as the target physical distance. Then use the receiving game's verified yaw and the DPI that will remain active. Rearrange the relationship as follows:
target sensitivity = (360 × 2.54) / (DPI × target yaw × reference cm/360)
This formula gives a target sensitivity only when the target yaw and sensitivity scale are known. It does not make an undocumented slider scale interchangeable with the reference game's scale.
For example, do not insert an assumed yaw simply to obtain a precise-looking number. If the target game's yaw is not verified, keep the relationship symbolic and find a converter or technical reference that identifies both the source and target games and explains its assumptions.
Use a Converter When the Scale Is Unclear
A game-specific converter is the better path when the target title does not document the required yaw or uses an unfamiliar sensitivity scale. Our sensitivity tool can serve as a navigation starting point for comparing game settings, but the output still needs an in-game full-turn test.
The gaming sensitivity converter research explains why titles can scale sensitivity differently and why field of view, aspect ratio, animations, and movement can change perceived feel even when the physical 360-degree distance matches.
Verify the Rotation and Lock the Setup
Validate the converted setting with one controlled full-turn test before making repeated changes. Keep the recorded DPI and target sensitivity unchanged during that first test.
Run a Controlled Full-Turn Test
- Confirm the active mouse DPI and the target game's sensitivity.
- Start from a repeatable position in a controlled practice area and move the mouse through one deliberate 360-degree turn.
- Compare the nominal turn distance and starting-to-ending orientation instead of judging only by visual feel.
If the rotation behaves unexpectedly, check the target game's input and acceleration settings. When a game supports it and registers for it, Microsoft's raw-input capability lets an application receive low-level HID data directly rather than relying only on traditional Windows mouse messages. That capability does not prove that every game processes mouse input in the same way.
Change One Variable Only
If the test shows that a small correction is needed, change only the in-game sensitivity and record the new value. Do not change DPI, sensitivity, and hardware at the same time, or you will not know which change affected the result.
If you change the mouse, its active DPI profile, or another relevant input setting, treat the old cm/360 record as stale and verify again. For background on checking whether a mouse's reported CPI matches its intended setting, see our sensor deviation guide. If hardware is part of the change, use gaming mice for setup options as a navigation starting point and confirm that the mouse can retain the DPI setting you need.
Once the full-turn test is repeatable, record the game's DPI, sensitivity, yaw or converter method, and resulting cm/360. That record gives you a stable baseline for future transfers without relying on arbitrary slider changes.
Keep eDPI for same-game checks, transfer with a verified cm/360 baseline, and confirm one full turn before locking the setting. This process gives your muscle memory a repeatable physical reference and makes later changes easier to trace. When you calculate eDPI across different games, use it only as a comparison aid, not as the transfer result.
FAQ
Does DPI Affect Sensitivity?
Yes. Changing DPI changes the mouse-side input relationship even when the in-game sensitivity slider stays the same. To preserve the same physical turn, recalculate or adjust the in-game sensitivity using the new active DPI, then verify the result.
Why Is cm/360 Better Than eDPI for Cross-Game Matching?
cm/360 measures the physical mouse distance required for a nominal full turn, while eDPI is only the product of DPI and a game's sensitivity value. Because different games can interpret their sensitivity scales differently, cm/360 is the more useful cross-game baseline.
How Often Should I Adjust My Sensitivity?
Adjust it after an intentional change, such as a new DPI setting, mouse, game input option, or controlled validation result. Avoid repeated arbitrary changes while building a baseline, because each change makes it harder to tell whether the conversion or the test caused the difference.
What If the Same cm/360 Still Feels Different in Another Game?
Check the target game's input and acceleration settings first. Then separate the measured physical rotation from field of view, aspect ratio, movement, animations, and other presentation factors before changing sensitivity again.
