Counter-Strike 2

CS2 “All Aboard” Update: Damage Prediction, Jump Throw Previews, New Maps & More



Check out Skinsmonkey: https://skinsmonkey.com/r/MAXIM

cs2 new predict system in a nutshell
byu/ProstiX inGlobalOffensive


https://x.com/ThourCS2/status/1856904713276371005
https://x.com/Mecke_Dev/status/1857021851257471350
https://www.reddit.com/r/GlobalOffensive/s/prcS3b7d0T

Future Maps?
byu/alettertoppl inGlobalOffensive


https://x.com/aquaismissing/status/1853897814213894627

🔔 Subscribe for new videos every week: https://www.youtube.com/channel/UCPKbW1excf-E7Tmwom1AgkQ?sub_confirmation=1

22 Comments

  1. I swear all the problems that CS2 has is cuz of the tick rate shit, why can’t we just get 128

  2. if you think this "damage prediction" feature did anything, please check my most recent video. game still blows unfortunately

  3. idk about yall but my networking is horrific after this update , back to playing other games till next update rip me

  4. The prediction system I think is something that a lot of games kind of already do. Your game isn't always necessarily waiting for the server to say the enemy is still walking to the left. Since it knows the enemy was walking to the left a millisecond ago, it's gonna assume the enemy will keep walking in the next millisecond. If it's wrong, then your game will correct itself.

    In this case, if you press your mouse, it assumes you killed that guy without waiting for the server to tell you that you did indeed kill that guy, and so it plays the animations and sounds right away so it feels instant. But sometimes the computer assumes wrong, and the guy you killed, that sounds like he died, will actually still be alive because he sidestepped on his end.

    This is just the major issue of latency and client to server to client connections. The server has the "true" version of the game running, but how do you communicate all the information to all players as fast as possible for a responsive feeling game?

    I believe this sort of tech was called "Client Prediction" back when it was created for the Quake games. Go look it up, it's fascinating stuff.

  5. kind of silly people saying "there's something wrong with the prediction system" when it's very clearly stated that predictions can be incorrect

  6. Imagine wasting hours implementing damage prediction to the engine when they could just change the number 64 to 128. Huge valve L

  7. Damage Prediction sucks. Make no sense to have a 0 ms feel when its not 0 ms. What you see is what you get but not what you hear is what you get.

  8. Basalt looks so much better in cs2, something always felt off about that map in GO to me. The new lighting, 3d skybox, models for the basalt columns look so good.

Write A Comment