Hello DPI Wizard, I found through some testing that the calculator is wrong somehow.
Game -> Counter-Strike: Global Offensive
According to the math, these two should be the same overall sensitivity (distance travelled with the mouse to achieve same rotation)
1600 DPI + 1 in-game sensitivity
400 DPI + 4 in-game sensitivity
But in fact, they are not the same. The math is wrong. The same distance travelled with the mouse does not equate to the same rotation, you can try it out yourself. 1600 dpi + 1 in-game is effectively a lower sensitivity than 400 dpi + 4 in-game. It's somewhat close, but it's definetly not accurate.
Perhaps that's why pro players stick to 400 DPI. If they tried to switch to a higher DPI / lower in-game sens, the sensitivity feels "wrong" because it is actually different.
Extra notes;
- m_rawinput 1 or 0 doesn't change anything (using 6/11 windows sens and markv fix)
- the mouse sensor isn't the issue
- getting way above 300 FPS
- test was done by 2 friends and confirmed by both
- other dpi / in-game sens settings were tested
- test was done by swiping mouse from left to right from one end of the mouse pad to the other (fast, medium and slow speed). I got consistent results using the Logitech G402 and the razer abyssus.
I ordered a Logitech g303 (best sensor money can buy), it's coming monday. I'll do a new test with the mouse to confirm that the sensor really isn't the issue here.