Counter-Strike 2: Performance and Settings Guide

Quick summary

A five-minute setup for those short on time:

1. Simplify your video settings. V-Sync off, 2x MSAA, Medium shadows, everything else Low — see the table.
2. Clean up your launch options. Remove any lists left over from the CS:GO era; -fullscreen -console +fps_max 0 is enough.
3. Lock in your eDPI. DPI × in-game sensitivity = eDPI. Most pros sit in the 600–1200 range — try it with the calculator.
4. Set up your crosshair. Classic static (style 4), small and outlined — try it in the preview.
5. Turn on the radar. Use cl_radar_scale 0.4 to see the whole map — see the difference.

Video settings: where does FPS come from?

In CS2, high and stable frame rate matters more than pretty visuals: frame-time fluctuation directly affects your aim. The table below is a balanced, competitive-leaning setup; the "Impact" column shows the setting's approximate effect on frame rate.

Launch options: less is more

Most of the long launch-option lists floating around online are leftovers from the CS:GO era and do nothing in CS2. In Steam › CS2 › Properties › Launch Options, this is enough:

-fullscreen -console +fps_max 0

Sensitivity and eDPI: boil it down to one number

The product of your mouse's DPI and your in-game sensitivity is called eDPI (effective DPI); it's the only number that lets you truly compare two players' sensitivity. cm/360 shows how many centimeters a full 360° mouse turn takes:

eDPI = DPI × sensitivity   ·   cm/360 = (360 × 2.54) / (0.022 × DPI × sensitivity)

Crosshair: try it right here

A good crosshair is one that doesn't cover the target and stays visible on every background. For a start, a classic static (style 4) with an outline is recommended. Play with the settings in the preview below; once you like it, copy and paste the console commands.

Radar: see the whole map

The default radar zoom crops out most of the map; you can't see where the bomb or your teammates are. Two commands make the radar show the full map:

cl_radar_scale 0.4
cl_hud_radar_scale 1.15
cl_radar_always_centered 0
cl_radar_rotate 1

Audio: use it as a source of information

In CS2, footstep sound and bullet direction are the biggest source of information after the radar. Three rules:

• Headset + stereo: Turn off virtual surround software; the game's own sound engine gives the most accurate directional information over stereo.
• Master volume 30–50%: Instead of "boosting" the volume to hear footsteps, find a level where explosion sounds don't overwhelm your ears while keeping the volume low.
• Turn off menu music, turn on the 10-second warning: Reset everything in the music settings but leave Bomb 10 Second Warning on — the music tells you how long is left before the bomb explodes, so you don't have to count.

Console and autoexec: make your settings stick

Instead of typing out the console settings you've made so far on every fresh install, collect them in an autoexec.cfg file:

1. Enable the console. Settings › Game › "Enable Developer Console" → Yes. The console opens with the ` (tilde) key.
2. Create the file. Add a text file named autoexec.cfg in the Steam\steamapps\common\Counter-Strike Global Offensive\game\csgo\cfg folder (make sure the extension isn't still .txt).
3. Paste the commands. Use the example below as a base; also add the lines you copied in the crosshair section.
4. Attach it to your launch option. Add +exec autoexec.cfg to your Steam launch options. The game loads your settings on every launch.

// OpenMoon örnek autoexec
fps_max 0
cl_radar_scale 0.4
cl_hud_radar_scale 1.15
cl_radar_always_centered 0
cl_radar_rotate 1
snd_tensecondwarning_volume 1
echo "autoexec yuklendi"