Fix CS 1.6 Jump Physics – Delayed, Slow & Inconsistent Jumps

Last updated: May 11, 2026

CS 1.6 jump physics problems fall into three categories: delayed jumps where pressing Space does not register instantly, slowdown after landing where your character stops dead after every jump, and inconsistent bhop where chaining jumps does not work. All three have different causes. This guide covers every fix in order.

CS 1.6 delayed jump fix

A delayed jump in CS 1.6 means pressing your jump key does not produce an instant jump – there is a visible pause before your character leaves the ground. The GoldSrc engine samples input once per frame, so when FPS is low, keypresses registered between frames are delayed until the next frame.

Fix FPS – the primary cause of delayed jumps

fps_max 101
gl_vsync 0

Add to userconfig.cfg. At 101 FPS input is sampled every ~10ms. With V-Sync on, input latency adds a full frame delay making jumps feel sluggish. Both must be set.

Fix jump keybind

If jump is bound to a key with a conflicting command or a script, the jump may not fire correctly. Restore the default bind:

bind "SPACE" "+jump"

Fix network rates contributing to delayed input

cl_cmdrate 101
cl_updaterate 101
rate 25000
ex_interp 0.01

Fix Windows keyboard repeat delay

Windows keyboard repeat delay set to Long causes brief stutter on first keypress. Fix: Win+R > control keyboard > Speed tab > set Repeat delay to Short, Repeat rate to Fast > Apply.

Counter-Strike 1.6 post-jump slowdown fix

The CS 1.6 jump slowdown after landing is a documented GoldSrc engine behavior where the “jump-lag” – the brief slowdown when touching the ground – is directly tied to FPS. This was documented on Valve’s GitHub (halflife issue #81): at very high FPS the jump-lag becomes severe and stops the player almost dead for nearly a second. At normal FPS (101) it is barely noticeable.

Set correct FPS cap

fps_max 101

If FPS is running at 200, 300, or uncapped, the post-jump slowdown becomes very severe. 101 is the optimal value for counter-strike 1.6 jump physics. Never set fps_max above 101 for competitive play.

Check movement speed settings

If cl_forwardspeed, cl_sidespeed, or cl_backspeed were changed, movement after landing feels abnormally slow. Restore defaults:

cl_forwardspeed 400
cl_sidespeed 400
cl_backspeed 400

CS 1.6 bunny hop inconsistency fix

CS 1.6 bunny hop (bhop) requires jumping at the exact moment of landing. The spacebar makes this nearly impossible because it has a mechanical repeat delay and Windows processes it with a slight buffer. Mouse wheel eliminates this problem entirely.

Bind jump to mouse wheel

bind "MWHEELDOWN" "+jump"
bind "MWHEELUP" "+jump"

Scrolling the wheel sends multiple jump inputs per scroll, making it much easier to hit the exact landing frame. Add to userconfig.cfg. Keep spacebar bound too for regular jumps:

bind "SPACE" "+jump"
bind "MWHEELDOWN" "+jump"
bind "MWHEELUP" "+jump"

Strafe technique for consistent bhop

Bhop in counter-strike 1.6 requires simultaneous strafing and mouse movement. When pressing A mid-air, move mouse left. When pressing D, move mouse right. Without strafing, momentum does not build and bhop feels inconsistent regardless of jump timing.

Enable client prediction for accurate bhop

Without client-side prediction enabled, your movement on screen is delayed relative to what the server calculates, making bhop timing feel inconsistent even when you hit the correct frames:

cl_predict 1
cl_lc 1
cl_lw 1

Check server bhop restrictions

Some servers set sv_maxspeed low or use AMXX plugins that cap player speed, making bhop feel like it does nothing. If bhop works in offline mode but not on a specific server, the server is restricting it. Nothing can be done client-side.

CS 1.6 jump height wrong fix

Standard counter-strike 1.6 jump height is determined by sv_gravity (default 800) and sv_maxspeed (default 270). If jumps feel lower or higher than normal:

Check gravity – offline or your own server only

sv_gravity 800
sv_maxspeed 270
sv_airaccelerate 10

These are server-side commands – they only work if you are the server host or playing offline. On public servers, only the admin can change these. If jump height is wrong only on one server, the server has modified sv_gravity.

Duck-jump for extra height

CS 1.6 has a duck-jump mechanic where crouching while jumping gives additional height – used to reach positions unreachable by normal jumping. Press and hold CTRL while pressing Space. This is not a bug, it is intended GoldSrc engine behavior.

Server-side CS 1.6 jump physics problems

If CS 1.6 jump physics feel wrong only on specific servers and work correctly offline or on other servers, the problem is server-side. Common server-side causes:

To check what a server has set, type the variable name in your console while connected – for example type sv_gravity and it will show the current server value. If the value differs from default, the server is intentionally running non-standard physics.

CS 1.6 jump physics config reset

If counter-strike 1.6 jump physics feel completely wrong and none of the above fixes work, a corrupted config is setting wrong movement values on every launch. Delete cstrike/config.cfg and let the game regenerate it, then add this to a fresh userconfig.cfg:

fps_max 101
gl_vsync 0
cl_cmdrate 101
cl_updaterate 101
rate 25000
ex_interp 0.01
cl_forwardspeed 400
cl_sidespeed 400
cl_backspeed 400
bind "SPACE" "+jump"
bind "MWHEELDOWN" "+jump"
bind "MWHEELUP" "+jump"

If jump physics are still wrong after a config reset, corrupted game files may be the cause. On Steam: right-click CS 1.6 > Properties > Local Files > Verify Integrity of Game Files. On Non-Steam: download a clean Counter-Strike 1.6 build and reinstall. For other movement problems beyond jumping, see the CS 1.6 lag spikes fix guide.