Default smoke lineups are a team's most cost-effective training asset, but version updates often cause subtle deviations. This article analyzes the physics behind utility trajectories, explains why low-speed, multi-bounce smokes are most sensitive to changes, and provides a three-step method to audit and update lineups.
Introduction
Default smoke lineups are a team's most cost-effective training asset: a smoke thrown three thousand times should theoretically have no deviation. But in reality, the same position and same aim point can result in a landing spot half a body width off after a version update, failing to block the window or getting stuck on a wall edge after bouncing. This is not a matter of feel; the utility trajectory itself is a dynamic system sensitive to parameters.
1. Trajectory is not a parabola; it's a damped integral
CS2 utility motion can be broken down into three parts: initial velocity vector, gravitational acceleration, and velocity decay and bounce direction after each collision. Many people treat it as high school physics projectile motion, looking only at initial speed and angle, but what really determines the landing spot is the collision sequence.
A smoke from release to landing typically undergoes 1 to 3 collisions. The first collision multiplies velocity by a restitution coefficient less than 1 and reflects according to the surface normal. The problem is that map geometry is not ideal planes: box edges have chamfers, walls have decorative protrusions, and invisible walls have thickness. These geometric details are most easily changed in version updates because they are byproducts of "visual optimization" and won't be written in patch notes.
As a result: your aim point hasn't changed, but the normal direction of the first collision has changed by 2 degrees, and the lateral displacement after the second bounce increases by a dozen units. The half-body-width deviation of default smoke lineups often comes from here.
2. The "non-linear zone" of bounce decay
Restitution coefficient is not constant. The decay curves for low-speed and high-speed collisions are different; the engine adds extra damping at low speeds to prevent utilities from sliding infinitely on the ground. This means that for the same smoke, throwing hard versus throwing lightly results in completely different sensitivity of landing spot to aim point error.
A hard-thrown smoke has a long flight time and few collisions; the landing spot is mainly determined by initial speed, and a slight aim offset results in a linear landing offset. A lightly-thrown smoke has many collisions, each bounce amplifies the error, and the landing spot is non-linear with respect to the aim point. This is why "light throw against the wall" default lineups are least resistant to version changes: they rely on a precise collision sequence, and any geometric tweak breaks the whole chain.
When teams re-practice default lineups, they always prioritize those "low initial speed, many collisions" smokes over hard-thrown overpass smokes. The former is the version-sensitive zone, the latter the version-stable zone.
3. Default utility lineups are a "consensus map", not personal skill
The value of default smoke lineups lies not in accuracy but in synchronization. Five players throwing at the same aim points in the same round can piece together a complete blocking line. Once a line drifts due to version changes, the team won't just adjust one person's aim point; they'll redraw the entire line, because synchronization is harder to rebuild than accuracy.
This is why pro teams always spend time "against the wall" during early-season scrims. They are not looking for new aim points; they are recalibrating that consensus: which lines still work, which need position changes, and which should be abandoned in favor of instant smokes.
4. How to judge whether a lineup should be re-practiced
My approach is three steps: first, fix the position and throw ten times with the same aim point to check landing variance; then move the position forward and backward by one body width to see if the landing spot moves linearly; finally, retest on a different server tick environment. If variance is high, movement is non-linear, and results are inconsistent across environments, the lineup should go on the re-practice list.
Version updates won't tell you which smoke lineup is obsolete; they'll just quietly change the thickness of a wall. Maintaining default utility lineups is essentially a periodic audit of the team's consensus map.