---
title: "Choosing Sensitivity and DPI for CS 1.6"
excerpt: "How mouse DPI, the in-game sensitivity cvar, raw input and Windows pointer settings combine in CS 1.6, and how to pick a value you can actually aim with."
category: "client"
tags: "mouse, sensitivity"
image: ""
read_time: "7 min read"
---
<p>Aim in CS 1.6 is the product of three numbers that most players never separate: your mouse DPI, the in-game <code>sensitivity</code> 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.</p>

<h2>1. Understand the two multipliers</h2>
<p>Your effective turn speed is roughly <strong>DPI &times; sensitivity</strong>. DPI (counts per inch) is set in your mouse driver or on the mouse itself; <code>sensitivity</code> is the engine multiplier. 400 DPI at <code>sensitivity 2.5</code> and 800 DPI at <code>sensitivity 1.25</code> feel almost identical because the product is the same. Most CS players sit at 400 or 800 DPI and adjust <code>sensitivity</code> from there rather than chasing a high DPI number:</p>
<pre>sensitivity 2.5</pre>
<p>Type <code>sensitivity</code> 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.</p>

<h2>2. Kill Windows and driver acceleration</h2>
<p>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 <strong>Enhance pointer precision</strong> in Windows (Control Panel &rarr; Mouse &rarr; Pointer Options) and set the pointer speed slider to the middle (6th notch). In your mouse driver, disable any acceleration or angle-snapping feature.</p>
<p>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:</p>
<pre>-noforcemparms -noforcemaccel -noforcemspd</pre>
<p>These tell the engine not to override your OS mouse settings, which is what you want once you have set them deliberately.</p>

<h2>3. Prefer raw input</h2>
<p>Updated CS 1.6 builds expose raw input, which reads the mouse directly and bypasses the Windows pointer pipeline entirely:</p>
<pre>m_rawinput 1
m_filter 0</pre>
<p><code>m_rawinput 1</code> is the single best setting for consistency — with it on, the Windows slider and acceleration no longer affect the game at all. Keep <code>m_filter 0</code>; filtering averages recent mouse samples and adds a smeared, floaty feel. Leave <code>m_customaccel 0</code> (in-engine acceleration off).</p>

<h2>4. Set your zoom ratio for the AWP</h2>
<p>Scoped weapons use a separate multiplier so that a scoped flick is not wildly faster than a hip-fire one:</p>
<pre>zoom_sensitivity_ratio 1.0</pre>
<p>At <code>1.0</code> the zoomed sensitivity is scaled to feel proportional to your normal sensitivity. Lower it (for example <code>0.8</code>) if scoped aim feels twitchy. This does not change your normal <code>sensitivity</code>, only how the scope behaves.</p>

<h2>5. Pick a value with the 360 test</h2>
<p>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&ndash;45 cm per 360 for aim-heavy play. Adjust <code>sensitivity</code> until the distance feels natural, then <strong>stop changing it</strong> — consistency beats the perfect number.</p>

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

<h2>Make it persist</h2>
<p>Put your mouse block in <code>userconfig.cfg</code> in the <code>cstrike/</code> folder so a game update or a server's forced cvars cannot lose it permanently:</p>
<pre>// cstrike/userconfig.cfg
sensitivity 2.5
zoom_sensitivity_ratio 1.0
m_rawinput 1
m_filter 0</pre>
<p>Then bind a key or type <code>exec userconfig.cfg</code> to reload it. If your whole config keeps resetting, that is a separate issue covered in <a href="/tutorials/cs16-verify-game-files">verifying game files</a>, since a corrupt install can refuse to save settings.</p>

<h2>Verification</h2>
<p>Open the console (<code>~</code>) and read the values back:</p>
<pre>sensitivity
m_rawinput
zoom_sensitivity_ratio</pre>
<p>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 <a href="/tutorials/cs16-static-crosshair">the static crosshair guide</a>.</p>