Best CS 1.6 Launch Options (-novid, -freq, -nofbo)

Launch options are arguments passed to the CS 1.6 executable before the engine boots, so they set things the in-game menu cannot — the renderer, the refresh rate, mouse-input handling. Most "best settings" lists online are copy-pasted junk full of flags that do nothing or actively hurt. This is the short, accurate list, with what each one does and when to use it. Set them in Steam via right-click Counter-Strike, Properties → Launch Options.

1. The options worth setting for almost everyone

-novid -console -freq 144 -noforcemparms -noforcemaccel -noforcemspd

• -novid — skips the Valve intro movie. Pure convenience, zero downside.
• -console — enables the developer console immediately. You want this; half of troubleshooting happens there.
• -freq 144 — sets the display refresh rate in Hz. Replace 144 with your monitor's actual rate (60, 75, 120, 144, 165, 240). If your game feels capped at 60 Hz on a high-refresh monitor, this is the fix. -refresh is a synonym on some builds.
• -noforcemparms -noforcemaccel -noforcemspd — tell the engine to leave your Windows mouse settings alone instead of forcing its own acceleration curve. Essential for consistent aim; without them the engine can re-apply acceleration you disabled in Windows.

2. Fixing a black screen or bad performance: -nofbo and the renderer

GoldSrc can render through an OpenGL Frame Buffer Object, and on some drivers that path produces a black screen, a black scope, or broken post-processing. Disable it:

-nofbo

Also choose your renderer explicitly. OpenGL is the right default on modern hardware:

-gl        (OpenGL, recommended)
-d3d       (Direct3D, try only if OpenGL misbehaves)
-soft      (software renderer, last resort for ancient/virtual GPUs)

Do not stack all three — pick one. If you get a black screen after alt-tabbing, add -nofbo and, if it persists, run windowed (below).

3. Resolution and window mode

-w 1280 -h 960          (force a resolution)
-window  /  -windowed   (windowed mode)
-full                   (fullscreen)

Windowed mode alt-tabs instantly and avoids most black-screen bugs at the cost of a little input latency. -w/-h are useful when a bad resolution has left you unable to see the menu to change it.

4. Options that are situational

-high         (higher process priority; minor, can help on busy systems)
-num_edicts   (server-side only — does nothing for a client)
-heapsize     (obsolete on modern builds; the engine sizes its own heap)
-32bpp        (force 32-bit colour; already the default)

-high is the only one here worth trying, and only if you see stutter under load. -heapsize and friends are cargo-cult leftovers from the 2000s — modern GoldSrc ignores or auto-sizes them.

5. FPS is a cvar, not a launch option

The single most requested "launch option", the FPS cap, is set in the console or config, not on the command line:

fps_max 144
fps_override 1     // required to exceed 100 on some builds

Match fps_max to your refresh rate (or a clean multiple of it). Uncapped FPS in GoldSrc can introduce movement quirks tied to the physics tick, so a sensible cap is better than "as high as possible".

6. A clean, complete example

For a 144 Hz monitor on a modern GPU, a sane full launch-options line is simply:

-novid -console -freq 144 -noforcemparms -noforcemaccel -noforcemspd -gl

Add -nofbo only if you hit a black screen or black scope, and add -window only if you want instant alt-tab. That is the entire list a normal player needs — everything else is either a cvar, a situational fix, or noise. Resist the urge to append flags you cannot explain; in GoldSrc, a shorter, understood launch line beats a long copied one every time.

Common mistakes

• Copying a 20-flag string from a forum — most of it is dead options. Every flag above has a reason; if you cannot say what one does, drop it.
• Setting -freq higher than the monitor supports — the display falls back to a safe rate or shows nothing. Use the real panel rate.
• Leaving -nosound in from a past test — silent game. See no sound on Windows.
• Using -soft "for FPS" — the software renderer is slower and uglier on any GPU made this century. Use -gl.

Verification

Launch the game and open the console. Confirm the refresh rate took by checking your monitor's on-screen display, or run:

gl_vsync 0
net_graph 3

net_graph 3 shows a live FPS counter bottom-right; it should sit at your fps_max. If it is pinned at 60 on a 144 Hz monitor, your -freq did not apply — recheck the value and that V-Sync is off. With input, renderer and refresh sorted, tune the rest of your connection with proper cl_cmdrate/cl_updaterate and rate settings for the servers you play.