CS2 Sub-Tick Jumpthrow Timing & Smoke Trajectory Matrix
Simulate Counter-Strike 2 sub-tick release windows, forward momentum velocity vectors, volumetric smoke coverage, and generate an autoexec.cfg alias bind for 100% consistent lineup execution.
โ๏ธ Throw Mechanics & Sub-TickMirage Window
Frequently Asked Questions
How does the CS2 sub-tick engine affect grenade jumpthrows?
In CS:GO, jumpthrows were tied to discrete 64 or 128 tick boundaries. In CS2, actions are timestamped between ticks at exact sub-tick millisecond timestamps. If you release mouse1 even 10 milliseconds earlier or later in your jump arc, the grenade inherits a different vertical velocity vector, causing manual jumpthrows without an autoexec alias bind to land inconsistently.
Do I still need a jumpthrow bind in Counter-Strike 2?
While Valve added an audio 'grunt' queue when releasing near the jump apex, competitive players still use a sub-tick alias jumpthrow bind in their autoexec.cfg. The bind guarantees that the '-attack' and '+jump' inputs share the exact same sub-tick timestamp every single round.
What is the difference between a W-Run Jumpthrow and a Walk Jumpthrow?
A regular jumpthrow inherits ~300 units/s upward jump velocity. A W-Run Jumpthrow adds 250 units/s horizontal forward momentum from running, extending flight distance by up to 40 meters. Walk Jumpthrows (holding Shift while moving) grant ~130 units/s forward momentum for mid-distance smokes like Ancient B-Site or Anubis Connector.
How does the CS2 volumetric smoke interact with HE grenades and bullets?
CS2 smokes are fully dynamic volumetric 3D meshes. An HE grenade exploding inside the smoke clears the entire cloud for exactly 3.5 seconds. Bullets punch temporary see-through vision holes through the smoke based on caliber and shot velocity.