Mouse sensitivity converter that keeps the same 360

Because the number is a multiplier, not a unit, and each engine multiplies it by a constant of its own choosing. Your view turns by that constant times your sensitivity for every count the mouse reports, so two games only agree when they inherited the same constant — which is why Counter-Strike 2, Apex Legends and Team Fortress 2 do convert one to one and nothing else does. Typing your Counter-Strike figure straight into Overwatch 2 leaves you turning 3.33 times slower, and typing it into Valorant leaves you turning 3.18 times faster, from settings screens that look interchangeable.

eDPI is DPI multiplied by in-game sensitivity, and it is a fair comparison only between players of one game. It works inside a title because everyone there shares the same yaw constant, so the constant cancels out of the comparison and 800 DPI at 1.6 really is the same speed as 1600 DPI at 0.8. Put two games side by side and the constant no longer cancels: a Valorant player on 280 eDPI turns in 46.7 cm, a Counter-Strike player on the same 280 eDPI turns in 148.4 cm, and neither of them would recognize the other setup.

Overwatch 2 stores sensitivity as a whole number from 1 to 100, so decimals are not being rejected by mistake — there is nowhere to put them. That granularity is coarse in a way people underestimate: one step at a sensitivity of 30 shifts the turn distance by 3.3 percent, and one step at a sensitivity of 5 shifts it by 20 percent. The way round it is the DPI field, which most mice change in increments of 50 or 100, so moving the sensor is how Overwatch players tune what the slider cannot.

Leave the DPI alone unless you have a reason to move it, because only the product of the two matters for turn distance. There are two reasons to touch it. A sensitivity that lands below about 0.5 in a game with three decimal places is being quantized more coarsely than you would like, and raising DPI while lowering sensitivity gives the same speed with finer steps. In the other direction, sensors above roughly 3200 DPI on cheaper mice apply smoothing or angle snapping that shows up as a curved line on a slow drag, so more DPI is not free precision.

It changes what a game sees only when the game reads the cursor instead of the mouse, which is what raw input exists to avoid. Anything using raw input takes counts straight from the device and the slider is irrelevant to it. Anything that does not — older titles, some launchers, most menus — receives counts already multiplied by the notch: 1/32 at the far left, 1 at notch 6, and 3.5 at the far right. Enhance pointer precision, the checkbox below it, is worse than the slider because its multiplier changes with how fast you move, so the same physical swipe covers a different angle each time and no conversion can survive it.

Yes, if you can find its degrees-per-count figure, which the last entry in each dropdown accepts directly. Some games publish it, most do not, and for those the community measures it by turning a known number of degrees against a landmark and counting the mouse travel. Watch out for the titles where no single constant exists: Minecraft cubes its slider before using it, so its default of 100 percent works out at exactly 0.15 degrees per count while 200 percent is eight times that, and Rainbow Six Siege ties its own conversion to the field of view you have set.

Almost always the field of view, which changes how far a target appears to move for the same angle of turn. A 360 degree turn takes the same distance whatever the field of view, but tracking something at the crosshair does not: widen the view and the world crosses the screen more slowly for the same mouse movement, so a correct conversion into a game with a different default can still feel sluggish. Work out what the two games are actually showing you on the FOV calculator before you start nudging the sensitivity you just calculated.