How Subtick Sampling Works in CS2's Engine
Unlike the older 64-tick or 128-tick servers that captured player actions only at fixed time intervals, CS2’s subtick system records the exact moment each input occurs—down to fractions of a millisecond—using a high-frequency clock on the client side. When a player shoots, moves, or changes their view angle, the game sends that action with a precise timestamp and the exact state of the mouse or keyboard input. The server then reconstructs the sequence of events using interpolation, effectively simulating what would have happened even between traditional tick boundaries. This design means the server no longer needs to wait for the next tick to process a shot; instead, it can evaluate the order and timing of multiple inputs as they truly occurred. However, this also places heavier demands on both CPU and network bandwidth. Every packet now carries more granular timing data, and the server must run a more complex reconciliation algorithm. In practice, this allows for flick shots that land on the exact pixel you were aiming at the moment of the click, but it also makes the entire system more sensitive to client-side clock drift and network jitter.
Improved Input Precision and Smoother Aiming
One of the most noticeable benefits of the subtick system is the increased input precision when swinging the crosshair and firing. In CS:GO, a shot fired between ticks would be registered at the next tick, meaning your exact crosshair position at the actual click could be slightly different from what the server recorded. CS2 eliminates this delay by timestamping the click together with the corresponding mouse movement data. For example, if you flick your crosshair quickly and shoot at the end of the flick, the subtick system preserves the last mouse movement sample before the click, so the bullet travels exactly to your intended point instead of a point from a few milliseconds earlier. This makes high-speed aiming feel much more direct and reduces the "input lag" sensation that many players complained about in the original engine. Additionally, moving the mouse during a shot now correctly reflects the real-time view angle change, meaning spray control and micro-corrections are rendered much more faithfully. For professional players and skilled riflers, this is a significant upgrade: tracking moving targets becomes more reliable, and the regretful feeling of "I was on his head but the server didn't register it" happens far less often in clean, low-ping conditions.
Desync and Hit Registration Inconsistencies
Despite the promise of greater accuracy, the subtick system has introduced a new class of problems related to desynchronization and hit registration. Because the server relies on precise client timestamps, any discrepancy between the client’s internal clock and the server’s clock—or any packet that arrives late due to jitter—can cause the game to reconstruct a slightly different sequence of events than what the shooter experienced. In practice, players have reported cases where their bullets land visually on an enemy’s head, but the server determines that the shot actually fired a few centimeters off because the subtick timestamp from the shooter’s ping was inconsistent. Additionally, when two players fire at nearly the same time, the system must decide which input was truly first. With subtick timestamps, that decision becomes heavily dependent on the quality of each player’s connection. A low-ping player has an advantage, but a high-ping player with stable jitter may sometimes have their timestamp treated as valid even though their reaction was later in real time. This has led to frustrating "peeker's advantage" scenarios and occasional hitbox desync where the enemy model on your screen is not the same as the server’s authoritative model. Valve has patched several iterations, but the inherent complexity of reconciling multiple high-frequency input streams means edge cases still remain.
The Impact on Movement, Peeking, and Competitive Fairness
Subtick doesn’t only affect shooting—it also changes the way movement and peeking feel. In CS:GO, strafing and counter-strafing were tied to the tick rate, so you had to release the movement key at a precise moment relative to a tick to stop instantly. In CS2, the subtick system records movement inputs continuously, meaning that counter-strafing can be executed more smoothly without needing to "hit a tick." This is a double-edged sword: on one hand, it makes movement feel more fluid and natural; on the other, it makes strafe-peeking sharper, as players can stop and fire more precisely than before, potentially increasing the power of wide swings. This has elevated the value of jiggle-peeks and shoulder-peeks at the highest level, adding a new layer of tactical depth. However, it also raises concerns about competitive fairness. Professional tournaments often use high-performance LAN networks, where subtick works as intended. Online matchmaking, however, is subject to varying ping, router buffering, and fluctuating frame times, which can cause subtick timestamps to be slightly off. As a result, some players claim that online CS2 feels less "fair" than CS:GO’s tick-based system, because the difference between a good and a bad connection is amplified. Valve continues to refine the system with server-side adjustments, but the debate over whether subtick truly improves competitive integrity remains a central talking point in the community.
