// LOADING CSMAUK
// LOADING CSMAUK
eDPI and cm/360 explained, the 4:3 stretched vs native debate settled, the video settings that actually matter, and a launch-options list that won’t break in Source 2.
By CSMAUK Staff
There is no single “best” CS2 settings file — pros disagree about resolution, sensitivity and even refresh-rate targets — but there are clear principles, sane ranges and a few outright mistakes to avoid. This guide walks through sensitivity and eDPI, the resolution debate, the video settings that move frames and clarity, the launch options that still work in Source 2, and the GPU-side tweaks worth doing. Where numbers shift between patches we flag it, but the framework holds.
Your true sensitivity is a product of two numbers: your mouse DPI (set in the mouse driver) and the in-game sensitivity slider. Multiply them and you get eDPI (effective DPI), the only figure that lets you compare two players who use different DPI. eDPI = DPI × in-game sensitivity. Most professionals sit between roughly 700 and 1000 eDPI, with the bulk of the field at 400 DPI and an in-game sensitivity around 1.5–2.5.
A complementary way to think about it is cm/360 — how many centimetres of mousepad you need to spin a full circle. Lower eDPI means more cm/360 (a bigger, slower, more precise arm-aim sweep); higher eDPI means less. Most CS2 pros land somewhere in the 25–50 cm/360 band. If you have the desk space, erring toward lower eDPI rewards consistent aim; cramped setups push you higher.
Windows “Enhance pointer precision” is mouse acceleration in disguise. With it on, the same physical flick travels a different distance depending on how fast you move — fatal for muscle memory. Turn it off in Control Panel → Mouse → Pointer Options, and keep m_rawinput 1 so CS2 bypasses the Windows pointer pipeline entirely.
These figures are documented from public pro-settings trackers and represent recent (2026) configurations. Players occasionally tweak between events, so treat them as a sane range to copy from rather than gospel.
| Player | DPI | In-game sens | eDPI |
|---|---|---|---|
| s1mple | 400 | 3.09 | 1236 |
| ZywOo | 400 | 2.00 | 800 |
| NiKo | 800 | 0.90 | 720 |
| m0NESY | 400 | 2.30 | 920 |
Note s1mple sits well above the field average — a reminder that there is no magic number, only what you have trained on. Pick a value in the common band, then change it at most once and only after weeks of practice.
This is the most religious debate in CS. The two camps are 1280×960 in 4:3 stretched and native 1920×1080 in 16:9. Plenty of legends run 4:3 stretched — s1mple, ZywOo, NiKo, coldzera and Twistzz among them — because the stretch makes player models wider and, some argue, easier to hit, and because lower resolution can lift frame rate on weaker hardware. The downside is a narrower field of view: you see less to your sides.
Native 16:9 gives you the full, undistorted field of view and the crispest image, which helps at long range and for spotting wide info. CS2’s newer engine and sub-tick model also run comfortably at high resolution on modern GPUs, so the FPS argument for 4:3 is weaker than it was in CS:GO. The honest answer: there is no measurable aim advantage either way, so try both for a week each and keep whichever your aim prefers. Whatever you pick, set the black-bars/stretch option to match (stretched fills the screen; black bars keep 4:3 centred).
A high-refresh monitor is the single biggest hardware upgrade for a competitive shooter. 144 Hz is the practical floor; 240 Hz and 360 Hz are common at the top level. The benefit only materialises if your frame rate keeps up — running 240 Hz at 120 FPS wastes the panel. Set the monitor to its highest refresh in Windows Display settings, and make sure CS2 is running at that refresh (not capped lower by V-Sync or a stale setting).
CS2 is more GPU-bound than CS:GO was, but it still rewards a clean, low-clutter image. The goal is a stable, high frame rate with no settings that hide enemies. Multisample anti-aliasing helps edges read clearly; shadow and detail settings are where you claw back frames.
| Setting | Recommended | Why |
|---|---|---|
| Display mode | Fullscreen | Lowest input lag; avoids compositor overhead |
| V-Sync | Disabled | Adds input latency; use the in-engine fps cap instead |
| Multisample AA | 4x MSAA | Clean edges without a heavy cost on modern GPUs |
| Global Shadow Quality | High | Shadows reveal enemy positions — do not gut this |
| Model / Texture Detail | Low–Medium | Cheap frames; little competitive downside |
| Shader / Particle Detail | Low | Reduces visual clutter and lifts FPS |
| Ambient Occlusion | Medium/Off | Minor visual; off if you need frames |
| Boost Player Contrast | Enabled | Makes enemy models pop against backgrounds |
The one setting people get wrong is shadows — turning them down to chase FPS removes a genuine information source, because a shadow stretching across a doorway tells you someone is there. Keep Global Shadow Quality at least High. Conversely, model/shader/particle detail can go low with almost no downside and good frame gains.
Set these in Steam: right-click Counter-Strike 2 → Properties → General → Launch Options. The Source 2 engine ignores or breaks on many old CS:GO launch options (resolution flags, -tickrate, threading flags), so keep the list short. A safe, modern set:
-novid -nojoy +fps_max 0Skip -high. It tells Windows to give CS2 high CPU priority, which sounds good but can starve background processes (Discord, audio, the OS scheduler) and cause stutter on a meaningful minority of machines. The gain is marginal and the risk is real — most pro configs leave it out. Also avoid cargo-culting long option lists from CS:GO-era guides; many of those flags do nothing in Source 2.
A few quality-of-life and clarity cvars worth setting once (enable the developer console first under Settings → Game). These tune networking feel and input, not gameplay advantage.
fps_max 400 // cap to a stable value (or your refresh rate)
fps_max_ui 240 // separate cap for menus to save power
cl_join_advertise 2 // let friends join your community games
m_rawinput 1 // raw mouse input, bypass Windows pointer
cl_disablehtmlmotd 1 // skip server MOTD pagesDriver-side settings can shave input latency. On NVIDIA, open the NVIDIA app / Control Panel, find CS2, and set Low Latency Mode to Ultra (or enable NVIDIA Reflex in-game if exposed), Power Management to “Prefer Maximum Performance”, and leave V-Sync off there too. On AMD, the equivalents in the Adrenalin software are Anti-Lag (enable it) and a high-performance power profile. On both, keep the GPU driver current — CS2 has received numerous post-launch optimisation patches and old drivers can leave frames on the table.
Tie it together like this: lock a DPI, set eDPI in the 700–1000 band, turn off every form of acceleration, pick one resolution and commit, keep shadows high while cutting cheap detail, run the three-flag launch line, and let your GPU driver run at full tilt. None of it is exotic — it is just the absence of mistakes, which is most of what separates a clean config from a janky one. Re-check the time-sensitive numbers (pro sens, fps targets) after big patches, but the framework above will keep serving you.