A Competitive Video Config for CS 1.6 (Gamma, r_ Cvars, Visibility)

A good competitive video setup in CS 1.6 does one thing: it makes enemies easy to see without breaking the rules or the game's feel. There is a lot of folklore attached to this — half the cvars people share are cheat-protected and will not take on a real server, and a few are placebos. This is a lean config of the settings that genuinely help, with an honest note on which ones the server has to allow.

1. Set gamma and brightness for readable shadows

The single biggest visibility win is lifting the darks so a player crouched in a shadow is not invisible. These are not cheats and work on any server:

gamma 3
brightness 2
texgamma 2
lightgamma 2.5

gamma ranges roughly 1–3; 3 is the practical maximum before the image washes out. brightness lifts the black point. texgamma and lightgamma shape how textures and lightmaps are toned. Push these until dark corners read clearly but bright areas do not bloom into a white smear — that balance point is personal, so tune on a dark map like de_nuke.

2. The r_ cvars worth setting

Most r_ cvars people paste around either do nothing useful or require sv_cheats 1. The ones that are legitimately worth setting:

r_detailtextures 0     // no detail-texture overlay; cleaner surfaces
r_decals 100           // cap decals so blood/bullet spam does not pile up
gl_max_size 512        // texture upload size; keep default unless low VRAM
gl_texturemode GL_LINEAR_MIPMAP_LINEAR   // trilinear, smooth distant textures

Lowering r_decals keeps the screen from filling with blood and bullet holes in a long round, which is a real clarity gain, not a placebo.

3. Cvars that need sv_cheats — do not rely on them

Be clear-eyed about this: the dramatic "see through walls" brightness cvars are cheat-protected. They will only take effect when the server has sv_cheats 1, which no real public or match server runs:

gl_monolights 1     // sv_cheats only — flat fullbright lighting
r_fullbright 1      // sv_cheats only
r_lightmap 0        // sv_cheats only

On a normal server these silently revert to their locked values. If a config promises wall-hack-like vision from these, it only works offline or on a misconfigured server — see the server cvars for why sv_cheats stays 0 in public.

4. Resolution, refresh and FPS

Pick your monitor's native or preferred mode in the video options, and drive FPS from launch options and a cap:

fps_max 100
cl_showfps 1

Whether you can exceed 100 FPS, and the physics reasons you might want a specific number, are covered in fps_max and fps_override. Set your refresh rate with the -freq launch option (for example -freq 144) so the game does not default to 60 Hz on a high-refresh panel.

5. Keep the HUD out of the way

A smaller, dimmer HUD leaves more of the screen for reading the map:

hud_fastswitch 1
cl_radartype 1
developer 0

hud_fastswitch 1 also makes weapon binds instant, which pairs with your buy binds.

6. Save it so it survives restarts

Do not put these in config.cfg — the game rewrites that file on exit. Create cstrike/autoexec.cfg (it runs at launch) or a named config you exec, and keep your video block there:

// autoexec.cfg
gamma 3
brightness 2
texgamma 2
lightgamma 2.5
r_detailtextures 0
r_decals 100
fps_max 100
hud_fastswitch 1
echo "autoexec loaded"

The trailing echo prints to console at startup so you know the file actually ran.

Common errors

• Brightness cvars "do nothing" — you tried gl_monolights or r_fullbright on a real server. Those need sv_cheats 1; use gamma, brightness, texgamma and lightgamma instead.
• Settings reset every launch — you edited config.cfg, which the game overwrites. Move them to autoexec.cfg.
• Image is washed out and hard to read — gamma and brightness pushed too far. Back them down until bright areas stop blooming.
• Game runs at 60 Hz on a 144 Hz monitor — no -freq launch option. Add -freq 144.
• Texture mode reverts — you typed the enum wrong; it must be one of the GL_*_MIPMAP_* strings exactly.

Verification

Load a dark map offline and read your values back in console by typing each cvar with no argument:

gamma
brightness
r_decals

The console echoes the current value of each. Then join a real server and confirm gamma and brightness still apply while the cheat cvars do not — that split is exactly what you want, because a config that only looks good offline is worthless in a match. If autoexec.cfg printed its echo line at startup, your settings loaded cleanly.