Why CS:GO sensitivity works in CS2 unchanged
Valve kept the sensitivity scale when CS2 replaced CS:GO: both games turn the camera 0.022° per count at sensitivity 1. Your old CS:GO value goes into CS2 as it is. At 400 DPI, sensitivity 2.0 needs 51.95 cm for a full turn in either game.
The converter above is set to CS:GO → CS2. It matters when you change DPI on the way over: CS:GO 2.0 at 400 DPI becomes CS2 1.000 at 800 DPI and 0.500 at 1600 DPI. You’ll also see cm/360°, in/360° and eDPI for your setup.
CS:GO to CS2 formula
CS2 sens = CS:GO sens × CS:GO DPI ÷ CS2 DPI. With equal DPI the multiplier is 1. The sensitivity command from your CS:GO autoexec works the same way in the CS2 console.
CS:GO to CS2 sensitivity table
CS:GO sensitivity (800 DPI) | eDPI | cm/360° | CS2 sens (800 DPI) | CS2 sens (1600 DPI) |
|---|---|---|---|---|
1 | 800 | 51.95 | 1.000 | 0.500 |
1.25 | 1000 | 41.56 | 1.250 | 0.625 |
1.5 | 1200 | 34.64 | 1.500 | 0.750 |
2 | 1600 | 25.98 | 2.000 | 1.000 |
2.5 | 2000 | 20.78 | 2.500 | 1.250 |
What did change
Raw input is the main difference. CS:GO had m_rawinput, and with it set to 0, Windows pointer speed and Enhance pointer precision could change your aim. CS2 removed the command and always reads raw input.
If your CS:GO setup depended on Windows settings, the same number won’t feel the same in CS2. The cm/360° in the converter shows the distance you actually get now, which is the figure to compare.