You shot too early, visual delay made you think you hit the shot. Solved.
Beautiful-Active2727
Spectator is not the same as the player
youUncoolButMeCool
This is spectator so it means fuck all
Diddinho
Swapped to fast bro.
ThrowingSid
Obviously you have to hit the heart directly for a kill
Substantial-Stick-44
Gaben fix this joke of a game…
Monso
Submissions like these is what RL was referring to with his manbabies post the other day.
Love how people are using a “64 tick is now more accurate” slogan to invalidate the existence of lag.
stilliffex
Looks like you moved and shot at the same time… hmm maybe not. Who knows.
knowledgeboar
They might have had better ping meaning their shots on the server registered before yours on the server. You need to show ping if you bring subtick into it because I’m pretty sure subtick is registered server side. You would have to compare your ping and your foes ping to actually be accurate. I have experienced this as well. Ping isn’t consistent and if your ISP (Internet service provider) sent the message later it’s actually the truth of what happened on the server. The ping you see is an estimation within a certain time frame, if it wasn’t the game would spent too many resources on your computer for calculating ping and you would lose frames. In competitive the pings are more accurate because the game server is not as latent, you have less distance and cables between the wires. To register shots in game the computer sends electric binary messages miles and miles to your team and opponents. It’s just how the Internet works.
BigMik_PL
A lot of effort to highlight something that isn’t a problem and was persistent in CSGO replay as well.
CSGO replay didn’t even register flick shots it looked like you never aimed at the person and just spin botted onto a player.
Limp-Assignment9281
Sabtik
jike_mordan
What you see is what you get*
*with a little of latency
sim0of
Dumbtick
Mavmav6
I laugh and cry so wildly, that the cord around my neck slips off.
Strg-Alt-Entf
What you see is what you get.
What the spectator sees has nothing to do with the game though.
riade3788
checked it frame by frame …first you flicked up exactly as you shot for some reason also you moved right as you shot 100% ..also you are aiming at his side pockets so you are likely to miss
Apamid86
Open cases it will fix
edgygothteen69
I’m sorry but this is a skill issue. You need to keep up with the meta and stop playing like it’s CSGO. In CS2 you need to predict where his lag will take him in the future, and then shoot at the point where you expect the subtick to rubberband your shot to via interpolation, accounting for ping difference and player style, meaning you need to shoot somewhere he isn’t, but not the place where he will be.
KmsCS2
Spectator is same as player but demo not the same. Op os igrat nekoliko gejmova
AgreeableBroomSlayer
Ball washers and shills coming in to say its a skill issue, muh demo or “iT hApPeNed in cSg0”
22 Comments
Average CS2 Experience
What you see is what the fuck !!!
You shot too early, visual delay made you think you hit the shot. Solved.
Spectator is not the same as the player
This is spectator so it means fuck all
Swapped to fast bro.
Obviously you have to hit the heart directly for a kill
Gaben fix this joke of a game…
Submissions like these is what RL was referring to with his manbabies post the other day.
Love how people are using a “64 tick is now more accurate” slogan to invalidate the existence of lag.
Looks like you moved and shot at the same time… hmm maybe not. Who knows.
They might have had better ping meaning their shots on the server registered before yours on the server. You need to show ping if you bring subtick into it because I’m pretty sure subtick is registered server side. You would have to compare your ping and your foes ping to actually be accurate. I have experienced this as well. Ping isn’t consistent and if your ISP (Internet service provider) sent the message later it’s actually the truth of what happened on the server. The ping you see is an estimation within a certain time frame, if it wasn’t the game would spent too many resources on your computer for calculating ping and you would lose frames. In competitive the pings are more accurate because the game server is not as latent, you have less distance and cables between the wires. To register shots in game the computer sends electric binary messages miles and miles to your team and opponents. It’s just how the Internet works.
A lot of effort to highlight something that isn’t a problem and was persistent in CSGO replay as well.
CSGO replay didn’t even register flick shots it looked like you never aimed at the person and just spin botted onto a player.
Sabtik
What you see is what you get*
*with a little of latency
Dumbtick
I laugh and cry so wildly, that the cord around my neck slips off.
What you see is what you get.
What the spectator sees has nothing to do with the game though.
checked it frame by frame …first you flicked up exactly as you shot for some reason also you moved right as you shot 100% ..also you are aiming at his side pockets so you are likely to miss
Open cases it will fix
I’m sorry but this is a skill issue. You need to keep up with the meta and stop playing like it’s CSGO. In CS2 you need to predict where his lag will take him in the future, and then shoot at the point where you expect the subtick to rubberband your shot to via interpolation, accounting for ping difference and player style, meaning you need to shoot somewhere he isn’t, but not the place where he will be.
Spectator is same as player but demo not the same. Op os igrat nekoliko gejmova
Ball washers and shills coming in to say its a skill issue, muh demo or “iT hApPeNed in cSg0”