CS 1.6 lag: how to fix high ping, loss and choke

Updated 2026-09-26

"Lag" can mean four different problems, and each one has its own fix. Changing random settings rarely helps - first find out what exactly lags. It takes one command.

Step 1: turn on net_graph

Open the console (~) and type net_graph 3. In the bottom right corner you will see:

• fps - frames per second on your PC;
• ping - time for data to go to the server and back, in milliseconds;
• loss - lost packets (should be 0);
• choke - updates the server could not send you (should be 0).

Play a minute and watch the numbers when the lag happens. net_graph 0 hides the graph.

Step 2: find your problem

Low FPS (stutter)

• Set fps_max 100 and gl_vsync 0, video mode OpenGL.
• Laptop: charger plugged in, "High performance" power plan, the game on the dedicated graphics card.
• Close programs that load the PC: browser with video, streaming, recording, downloads, antivirus scans.
• All settings are in the guide best CS 1.6 settings and config.

High ping

Below 50 ms is excellent, 50-100 ms is fine, above 150 ms is hard to play.

• Use a cable instead of Wi-Fi. Wi-Fi adds ping and, worse, ping spikes.
• Stop downloads: torrents, game and Windows updates, cloud sync, video in another tab or on another device at home.
• Pause Steam downloads while you play.
• Choose a closer server. Ping depends on distance: the server browser shows the ping of every server before you join.
• If the ping is high on all servers, restart the router; if it does not help, call your internet provider.

Loss

Loss means packets are lost between you and the server. Game settings cannot fix it - the connection must be fixed.

1. Check if loss happens on other servers too. If yes - the problem is on your side.
2. Open the Windows command line (Win+R → cmd) and run ping -n 100 8.8.8.8. At the end look at "Lost". Anything above 0% means your connection loses packets.
3. Switch from Wi-Fi to a cable, restart the router, check the cable.
4. If loss stays, show the ping result to your internet provider - it is their job to fix it.

Choke

Choke means the server wanted to send you an update but had to skip it. The most common reason is a too low rate.

1. Set rate 100000, cl_updaterate 101, cl_cmdrate 101.
2. On a slow or mobile connection choke can come from the line itself - try rate 25000 and cl_updaterate 60.
3. If choke appears only on one server and everyone there complains - the server is overloaded (see below).

Shots do not register

• Check that cl_lc 1 and cl_lw 1 are on (lag compensation and weapon prediction).
• ex_interp 0.01 with cl_updaterate 101 - a too high interp makes hitboxes lag behind the models.
• Get rid of loss and choke first - with them no settings will give good hit registration.

When the server is to blame

If all players lag at the same time, the problem is the server, not you. Good servers keep a high server FPS and allow high rates. Balagun runs on ReHLDS with a high tickrate and allows rate up to 100000 and cl_updaterate up to 102, so with the settings above you get the smoothest possible game. If you notice lag on our server, write about it on the forum - with the map, the time and a net_graph screenshot.

Check your connection on our server: 57.131.192.149:27015 - open the console (~) and type connect 57.131.192.149:27015.

Frequently asked questions