Hacker News new | ask | show | jobs
by sosodev 254 days ago
CS2 is mostly 64 tick from what I understand. The "sub-tick" stuff is timestamping actions that happen on a local frame before the next tick. So in theory the client feels perfectly responsive and the server can adjust for the delta between your frame and the tick.

In practice it seems to have been an implementation nightmare because they've regularly shipped both bugs and fixes for the "sub-tick" system.

The netcode in CS2 is generally much worse than CSGO or other source games. The game transmits way more data for each tick and they disabled snapshot buffering by default. Meaning that way more players are experiencing jank when their network inevitably drops packets.

3 comments

That's very interesting. The CS2 netcode always felt a little brittle and janky to me, but I could never pin point exactly what was causing the issues. Especially since other games mostly run fine for me.

I also remember reading a few posts about their new subtick system but never put two and two together. Hopefully they keep refining it.

Worth noting that part of the packet size appears to be due to animation data, which they’ve begun the process of transitioning to a more efficient system. [0]

With that being said: totally agree on the netcode.

[0]: https://old.reddit.com/r/GlobalOffensive/comments/1fwgd59/an...

It's actually incredible how CSGO was such a great game and it's been replaced (not deprecated, replaced!) by CS2 which is still inferior over 2 years after the launch.
CS2 while still has some rough edge, i think it's fine. I don't have any complaint with it, and i has been day 1 player.(but just casual)