Frame rate in CS 1.6 is tangled up with movement physics, which is why the community obsesses over specific numbers like 100 or 250 FPS. There is a lot of half-true advice floating around. This lays out what fps_max actually does, why fps_override exists, how the frame rate feeds into movement, and how to pick and lock a value that is stable.
1. What fps_max does
fps_max is your client's frame-rate ceiling — the game will not render more frames per second than this value:
fps_max 100
By default the engine will not let fps_max take effect above 100. Set fps_max 300 on a stock client and you are still capped at 100. That cap is the source of most confusion: people set a big number, see 100 in the FPS meter, and assume their hardware is the limit when it is the engine.
2. What fps_override unlocks
To raise the ceiling past 100 you must first flip the override:
fps_override 1 fps_max 300
With fps_override 1 the engine honours higher fps_max values (up to the engine's own hard ceiling, 1000). Without it, the second line is ignored. So the true unlock is two cvars, in this order: override on, then the cap. If your FPS refuses to go above 100 no matter what you type, you forgot fps_override 1.
3. Why the number affects movement
This is the part that makes FPS more than a smoothness setting. The Half-Life engine ties some movement mechanics to the frame rate, so different fps_max values produce subtly different physics. The practical upshots players care about:
- Certain FPS values make bunnyhopping and strafe acceleration easier or more consistent, which is why some players lock to specific numbers.
- Very high, unstable frame rates can make movement feel less consistent than a rock-steady lower number.
The lesson is that a stable frame rate matters more than a big one. A steady 100 beats a jittery 300 that dips constantly.
4. Pick a value your hardware holds
Choose the highest number your machine can sustain without dipping, not the highest it can momentarily touch. If your FPS bounces around, cap it below your worst-case rather than at your peak:
fps_override 1 fps_max 144 // or match your monitor's refresh
Matching fps_max to your monitor's refresh (set with the -freq launch option, covered in the video config) keeps tearing down and frame delivery even. Chasing four-digit frame rates for their own sake is mostly pointless on this engine — past the point where your monitor and your movement feel smooth, extra frames buy you nothing but heat and noise, and if they come at the cost of stability they actively hurt.
5. Measure it, do not guess
Turn on a live readout so you are tuning against real numbers:
cl_showfps 1 // simple FPS counter net_graph 3 // FPS plus choke, loss and ping
net_graph 3 is the better tool because it also shows choke and loss — if those spike, your problem is the network or your rates, not frame rate. Rates are covered in the server cvars reference. Save your FPS cvars in autoexec.cfg so they load every launch.
Common errors
- FPS stuck at 100 no matter the value — you set
fps_maxhigh but notfps_override 1. Set the override first. - Movement feels inconsistent at high FPS — the frame rate is unstable and dipping. Cap at a number you can hold steadily instead of your peak.
- Screen tearing —
fps_maxfar above your refresh rate. Match it to the monitor and set-freq. - High FPS but the game still stutters — that is choke/loss, not frame rate. Check
net_graph 3and fix your rates. - Settings reset each launch — you typed them in console or put them in
config.cfg. Move them toautoexec.cfg.
Verification
Turn on the counter and confirm your cap holds under load — join a busy server, not an empty one, because that is where FPS actually drops:
cl_showfps 1 fps_max
Typing fps_max with no value echoes the current cap; the on-screen counter should sit at or just under it with only small dips. If it is pinned at 100 despite a higher cap, fps_override is still 0 — set it to 1 and re-check. Once the number is high and, more importantly, steady, your movement will feel consistent, which is the real point of tuning FPS at all.
