You've practiced that default smoke a hundred times, then one day it leaks a sliver. You blame your aim, your resolution, your monitor—but the truth is colder: grenade physics, map collision thickness, and even invisible walls drift silently with each patch. Your muscle memory didn't change. The world did.
Introduction
You've practiced that default smoke a hundred times, then one day it leaks a sliver. You blame your aim, your resolution, your monitor—but the truth is colder: grenade physics, map collision thickness, and even invisible walls drift silently with each patch. Your muscle memory didn't change. The world did.
1. Trajectory Is Not a Parabola—It's a Piecewise Function
Most players imagine a grenade's path as a clean parabola. That's the biggest misconception. In CS2, a grenade's flight involves at least three physics phases: initial velocity, air resistance decay, and post-collision bounce. Each phase can be tuned independently.
That smoke you practiced in the workshop relies on "release velocity + flight time + impact normal." A 0.5% difference in initial speed shifts the landing point by several units. Map collisions—especially decorative box edges, eaves, billboards—their normals determine bounce direction. When a patch reimports art assets and rebakes collision, a normal can shift from 45° to 43°. You see the same box; the grenade sees a different plane.
So first: don't memorize "positions." Memorize "release point + velocity + landing point." Position is just scaffolding to reproduce velocity.
2. Bounce Decay: The Ignored Third Collision
Pro utility lines often bounce only once, because the second bounce introduces randomness that eats precision. But default lines—especially long-range ones from spawn to mid—often rely on two or even three bounces.
The problem: in CS2, grenades lose speed on each collision, and the loss coefficient isn't fixed. It depends on incidence angle, surface material flags, and grenade type. Smokes are heavier than molotovs, losing more speed; flashes are lighter, bouncing farther. When a patch adjusts mass for a grenade type, your triple-bounce line shifts back entirely.
In practice: the smoke is still the same smoke, but the landing point goes from "blocking the choke" to "blocking half." The opponent peeks through the gap, and you think they got lucky—actually, your line has expired.
Default lines are called "default" because they assume a stable physics environment. When the environment changes, default is no longer default.
3. Relearning Defaults: From "Reproduction" to "Calibration"
Relearning isn't running old positions a hundred more times. It's building a calibration process.
Step 1: Fix variables. Use workshop trajectory display to record release coordinates, velocity direction, first impact coordinates. Step 2: Compare landing offset before and after the patch. If offset is less than one body width, adjust position slightly; if more, scrap the line. Step 3: Find new bounce points. Don't look for "similar-looking" surfaces—look for stable normals: large flat ground, vertical walls, avoid chamfered or decorative collisions.
Step 4, most important: verify in the live map. Workshop maps and live maps don't always share identical collisions, especially late-added decorations. Many lines are perfect in workshop but leak in live because the workshop version hasn't synced the latest collision bake.
4. First Thing After a Patch
After every major patch, don't rush into ranked. Spend twenty minutes running your three most-used default smokes, two default flashes, and one default molotov on the live map. Check landing points, bounces, and gaps.
Grenades don't talk, but they do expire. Your utility lines need to breathe with the patch.