Choosing Sensitivity and DPI for CS 1.6

Aim in CS 1.6 is the product of three numbers that most players never separate: your mouse DPI, the in-game sensitivity cvar, and whatever Windows pointer acceleration is doing behind your back. Get the interaction wrong and the same flick lands differently every round. This walks through what each layer actually does and how to lock down a consistent, repeatable setup.

1. Understand the two multipliers

Your effective turn speed is roughly DPI × sensitivity. DPI (counts per inch) is set in your mouse driver or on the mouse itself; sensitivity is the engine multiplier. 400 DPI at sensitivity 2.5 and 800 DPI at sensitivity 1.25 feel almost identical because the product is the same. Most CS players sit at 400 or 800 DPI and adjust sensitivity from there rather than chasing a high DPI number:

sensitivity 2.5

Type sensitivity in the console with no value to read your current setting. Change it in the console, not just the menu slider, so you get the exact decimal you want.

2. Kill Windows and driver acceleration

Pointer acceleration means the same physical distance produces a different in-game angle depending on how fast you move — fatal for muscle memory. Turn off Enhance pointer precision in Windows (Control Panel → Mouse → Pointer Options) and set the pointer speed slider to the middle (6th notch). In your mouse driver, disable any acceleration or angle-snapping feature.

CS 1.6 also has its own launch options that stop the engine forcing Windows mouse parameters. Add them to the game's launch options in Steam:

-noforcemparms -noforcemaccel -noforcemspd

These tell the engine not to override your OS mouse settings, which is what you want once you have set them deliberately.

3. Prefer raw input

Updated CS 1.6 builds expose raw input, which reads the mouse directly and bypasses the Windows pointer pipeline entirely:

m_rawinput 1
m_filter 0

m_rawinput 1 is the single best setting for consistency — with it on, the Windows slider and acceleration no longer affect the game at all. Keep m_filter 0; filtering averages recent mouse samples and adds a smeared, floaty feel. Leave m_customaccel 0 (in-engine acceleration off).

4. Set your zoom ratio for the AWP

Scoped weapons use a separate multiplier so that a scoped flick is not wildly faster than a hip-fire one:

zoom_sensitivity_ratio 1.0

At 1.0 the zoomed sensitivity is scaled to feel proportional to your normal sensitivity. Lower it (for example 0.8) if scoped aim feels twitchy. This does not change your normal sensitivity, only how the scope behaves.

5. Pick a value with the 360 test

Rather than copy a pro's number, measure your own. Clear space on the desk, put the crosshair on a fixed point, and see how many centimetres of mouse movement it takes to spin a full 360 degrees. Lower sensitivity = more centimetres = more arm aim and precision; higher = less desk space but harder to hold steady. A common range is 25–45 cm per 360 for aim-heavy play. Adjust sensitivity until the distance feels natural, then stop changing it — consistency beats the perfect number.

Troubleshooting

• Aim feels different after an update or on a new PC — Windows acceleration came back on, or m_rawinput reset to 0. Re-check both. A migrated config does not carry your Windows settings.
• Cursor is fine in menus but aim is inconsistent in-game — acceleration is active. Confirm m_rawinput 1 and the three launch options above.
• Sensitivity slider snaps to a rounded value — the menu rounds; set the exact decimal in the console instead and it sticks.
• Scoped aim is way too fast or slow — that is zoom_sensitivity_ratio, not sensitivity. Tune it separately.
• Settings reset every launch — your config.cfg is read-only or being overwritten. See the note below on making settings persist.

Make it persist

Put your mouse block in userconfig.cfg in the cstrike/ folder so a game update or a server's forced cvars cannot lose it permanently:

// cstrike/userconfig.cfg
sensitivity 2.5
zoom_sensitivity_ratio 1.0
m_rawinput 1
m_filter 0

Then bind a key or type exec userconfig.cfg to reload it. If your whole config keeps resetting, that is a separate issue covered in verifying game files, since a corrupt install can refuse to save settings.

Verification

Open the console (~) and read the values back:

sensitivity
m_rawinput
zoom_sensitivity_ratio

Each should echo exactly what you set. Then do the 360 test twice with a fixed desk mark — if both spins land on the same spot, acceleration is truly off and your aim will be repeatable. Once the mouse is dialled in, a matching static crosshair helps you see exactly where shots land; see the static crosshair guide.