CS 1.6 Choke Fix – Counter-Strike Network 1.6 Choke Problem

Last updated: August 2, 2026

Shots not registering, movement feels delayed, game freezes for a split second and snaps forward – that is cs 1.6 choke. Counter-strike 1.6 choke fix starts with understanding what choke actually is: the server is dropping your packets because you are sending more than it can handle, or because your rate is mismatched with the server.

Every dropped packet is a command – a shot, a step, a grenade throw – that the server never executed. Below is a step by step process to confirm choke, find the exact cause, and reduce choke in cs 1.6 permanently. If you don’t have the game yet, download CS 1.6 from csdownload.net.

Confirm you have cs 1.6 network choke

Before changing anything, confirm choke is the actual problem. Open the console with ~ and type:

net_graph 3

Look at the choke value in the network readout:

Choke value	What it means
0	No choke – packets are reaching the server. Choke is not your problem – check loss instead
1-10	Minor choke – slightly affects hit registration
10-30	Noticeable choke – shots miss, movement stutters
30+	Severe choke – game is nearly unplayable

If choke is 0 your problem is something else. If choke is above 0 – continue.

Check the counter-strike 1.6 server rate first

Before setting your rates, you need to know what rate the server uses. A mismatch between your rate and the server’s rate is one of the most common causes of counter-strike 1.6 choke that players miss – they try lowering cl_cmdrate for hours but the real problem is their rate is set to 25000 while the server uses 100000, or vice versa.

Type in console:

cvarlist sv_maxrate

sv_maxrate value	Server type	Use this rate
0	No cap – most common on modern servers	rate 100000
100000	Modern ReHLDS server with explicit cap	rate 100000
25000	Standard older server	rate 25000
20000 or lower	Restricted or older server	Match exactly – e.g. rate 20000

The rule is simple: set your rate to match or be lower than sv_maxrate. If sv_maxrate is 0 – no limit, use rate 100000. If sv_maxrate is 20000 – use rate 20000. Setting rate higher than the server cap causes a bottleneck that shows up as choke during heavy action. Setting it lower than necessary means you’re not using all available bandwidth.

Set the correct cs 1.6 rates to fix choke

Based on what you found in Step 2, enter the matching settings in console:

For standard servers (sv_maxrate 25000)

rate 25000
cl_cmdrate 101
cl_updaterate 101
ex_interp 0.01
fps_max 100

For modern ReHLDS servers (sv_maxrate 100000)

rate 100000
cl_cmdrate 101
cl_updaterate 101
ex_interp 0.01
fps_max 100

ex_interp note: always keep ex_interp equal to 1 / cl_updaterate. For updaterate 101 the correct value is 0.01. Wrong ex_interp causes hit registration problems even when choke is 0.

Verify counter-strike 1.6 choke is gone

Wait 20-30 seconds then check net_graph 3 again. If choke = 0 – cs 1.6 choke fixed. Save the working settings to cstrike\autoexec.cfg so they apply every session automatically. If choke is still above 0 – continue.

Counter-strike 1.6 choke persists – lower cl_cmdrate

If the rate is correct but choke persists, the server’s sv_maxcmdrate is lower than your cl_cmdrate. Lower cl_cmdrate and cl_updaterate by 10-20 at a time, wait 20-30 seconds, check choke again. Repeat until choke = 0:

rate 25000
cl_cmdrate 60
cl_updaterate 60
ex_interp 0.016
fps_max 60

The goal is the highest cl_cmdrate value where choke stays at 0 on that server. Different servers have different caps – settings that work on one server may cause choke on another.

When the cs 1.6 choke is caused by the server

If you’ve matched the rate, lowered cl_cmdrate to 40 and choke is still above 0 – the server itself is overloaded. Signs it’s server-side:

• Choke only on this server, not on others
• Choke increases as more players join
• Other players report the same problem simultaneously
• Lowering your rates has no effect

Server-side choke cannot be fixed from your client. Switch to a less loaded server.

CS 1.6 choke vs loss – the difference

	Choke	Loss
What it is	Server drops your packets	Packets lost between you and the server
Cause	Rate mismatch or cl_cmdrate above server cap	Bad internet connection, Wi-Fi, ISP issues
Fix	Match rate to server, lower cl_cmdrate	Use wired connection, contact ISP
Symptoms	Shots not registering, movement delayed	Teleporting, rubber-banding, random freezes

For complete lag and performance settings, see the full cs 1.6 lag fix guide. For ping spikes and cs 1.6 choke and loss combined, see the cs 1.6 lag spikes fix.