Subtick Architecture vs 128-Tick Dispatch in Source 2: Competitive Benchmark Analysis and 하드웨어 Interactions

[Henry Bailey]

The subtick system in Source 2 completely changed how I approach competitive play, and I want to hear from people who’ve actually benchmarked it. In my own testing across different tick-based implementations, I keep seeing hit registration inconsistency at the boundaries between simulation ticks—when I fire during rapid movement, hits sometimes land on interpolated positions instead of my actual query point. So here’s what I need to know: how are you all handling micro-tick timestamping when your input latency is already under 10

[Max Bell]

Solid topic, and honestly one I’ve been digging into heavily since the CS2 swap. The biggest misconception I keep seeing is that subtick “replaces” 128-tick — it doesn’t, it decouples interpolation from authoritative sampling. With SSS, the server still runs a fixed tick loop for simulation, but each input/event gets stamped with microsecond precision, so a shot registered at t=12.347ms resolves correctly regardless of the 64/128 tick interval. In real matches, the difference you actually feel is in shot registration on movement and peek advantages — the old fixed-tick system punished you if your input landed between ticks, and “I shot him but he survived” was mostly quantization error. Subtick largely kills that. That said, don’t expect it to fix bad netcode: it’s still UDP on top, so packet loss and reordering still bite you, it just doesn’t punish you for the timing of your inputs anymore.

On the hardware side, the interesting shift is that subtick moves load around rather than just piling it onto the CPU. 12

"Lag isn’t an excuse, but it definitely wasn’t my fault."

[Jayden Nelson]

The core thing people keep getting wrong in this thread is that subtick doesn’t actually raise your server’s tick rate—it decouples input sampling from the simulation clock. In CS:GO’s 128-tick model, your movement was

"Overwatch 2 Top 500 Hitscan | 1600 DPI @ 2.5 Sens • EU Region"

[Author]

Posts