DPI Wizard

Basically yes, but I have to analyze this further to see how quickly ~37 gives you a disadvantage over 50.

It's 37.something if I recall correctly. The reason is that with different FOVs it's impossible to match the exact movement in terms of "2d distance" (that is moving the crosshair to an object on the monitor) over the entire monitor. You have to match it to a fixed point, and before or beyond this point it will not match. I'll try to explain this better in a video at a later point

Not exactly, 50 zoom sensitivity matches moving the mouse to the object at the edge of the screen perfectly, while 37 matches moving only an inch or so on the monitor.

It should be 50 when your FOV is 103.

The calculator is located on the front page (http://www.mouse-sensitivity.com/), but if you mean the ratio one it is not done yet.

I'll start working on a new mode for the calculator now, a ratio conversion. A mode that keeps the "distance" your crosshair moves constant. The crosshair never really moves, but you get the idea Four years back when I started this, converting 360 degree turn seemed to be the most universal standard for sensitivity conversion. Later the desktop-to-game conversion came, which in a sense keeps the ratio constant. There are however two problems with this conversion: The distance covered by the mouse pointer in Windows (let's call it X) can never be perfectly matched to moving the crosshair to an object X pixels away all over the screen. This is because the view in an FPS or 3rd person game is spherical, while the view in Windows is obviously two dimensional. The best you can do is match it for one fixed parameter, and I chose moving the cursor from the center of the screen to the edge to match turning to an object at the edge of the screen in-game. This makes short crosshair movement around the center a little bit off, while larger movements towards the edge of the screen match good. The second problem is that you can't convert from one game to another with this mode, you need to base them all off of the Windows / Desktop input. Now with a ratio conversion (ratio being the correlation between how far you physically have to move the mouse to aim at an object in-game, regardless of FOV), the second problem will be solved. But the first problem is still there to a certain degree, as you have to match the ratio at a fixed point. And I plan to add this as an option if possible, so you choose where you want the ratio to match. For instance a percentage between the crosshair and the edge of the screen. No promises of what will come yet as I haven't started coding, but something like this is the plan.

It has not, I'll get it done.

I just added support for zoom sensitivity for all CSGO scopes

Actually, let me moderate my answer a little; 50 is correct for edge-to-edge screen movement, while 37 is correct for moving 1 count. The more you move with 37, the more it (quickly) deviates from the hipfire distance, and with 50 it's opposite; it gets more correct the more you move. I'll see if I can get a video up showing this

Getting around 30 when the calculation says 28.8 is normal. The calculations are correct, but the deviation is in the sensor and obviously human error. But 33-34 is a little too much, that's really strange considering you only got about 7% deviation in the analyzer. Did you test with another mouse of the same brand? It might be something in the driver/settings.

Ok, that's within the normal range. Have you tried converting to another game and checked if you still have 34-35 cm 360?

Definitely, the formula is a lot simpler than that. The sensitivity scales linearly with FOV (for scoped, not for regular FOV), so it is simply 51/103=49.51. So by setting the relative aim to 50, you are effectively doubling the 360 distance, but since the FOV is half, the crosshair will cover the same 2D distance

If you check the game notes you'll see why: Affected by: FOV: Yes FOV affects sensitivity in some games, others not

Have you tested your mouse sensor accuracy with the DPI Analyzer? If not, do that and tell me what result you get

Just verified that nothing changed between beta and release, so this should be correct. It will be off by about 6% though, since the Overwatch sensitivity is limited to whole numbers. But other than that it shouldn't feel too slow.

What values are you using?

I've added the sniper scope calculations, but couldn't really find an adjustable modifier. Did I miss anything?

I'll do this later today!

Select Hipfire (simple) for Rainbow Six if you have not changed the settings in the config file.

Glad you figured it out

Added

Done!

The zoom leves are almost identical when it comes to the distance the crosshair moves. I've added all scopes and zoom-levels now, and notice that if you convert from Windows to any of them you will get almost the same sensitivity back