Bullets are hitting, but not counting.

[Hippnosis]

I've been playing this game for some time now and started to notice something. So, when playing, you shoot a person like 5 times up close, but then somehow they survive it and kills you. Once that box pops up on how many times they shot you and how many times you shot them, it says 0 shots were given. Sometimes when your lucky, it would say 2 shots hit, but still there are bullets that went missing. This confused me, this also irritates me too. I'd play competitive and this still happens. I know this happens to other people, sometimes when I kill someone, they would say in the mic that they shot me. While the box that pops up for them says that they landed 0 shots, I tell them that they at least hit me 3 times.
I not a expert on money and making games here...but, doesn't Valve make a lot of money? I mean, I payed for this game and suspected it to be 100% no ♥♥♥♥♥♥♥♥. I know there's going to be small errors in the game...but since this happens a lot, its a big error. Definitely if it happens in competitive.
PLEASE FIX THIS.

[ariba]

Yes, that's the tickrate for you.

[Maltazar]

..
It's the hit reg.

The client side, your side, think it hits.
But the server side, the thing everyone is playing on, think it didnt hit.
And the server side it what counts.

[Maltazar]

If you stay updated on CSGO you can see that everyone is complaining

[Dr. Zoidberg]

Originally posted by Maltazar:

..
It's the hit reg.

The client side, your side, think it hits.
But the server side, the thing everyone is playing on, think it didnt hit.
And the server side it what counts.

this statement is more right than this.

Originally posted by ariba:

Yes, that's the tickrate for you.

[WD-40]

64 tick servers

[Maltazar]

Originally posted by Talha:

64 tick servers

It happens on 128 servers too.

[Dr. Zoidberg]

it'll happen on even 1024 tick servers too, if you have very bad ping.

[Grizzledorf]

also some people do not realize it was not the person they were shooting at who killed them.

make sure to check console for damage. i use to make that mistake sometimes when new, i die and assumed it was the dude i knew i hit a couple times then see done 0 damage.

but ya other than that. server side trumps client side, so its possible your client to show one thing but by time data reach server is calculated a miss not a hit

[THE LORD]

This time around, I don't think it's the tick rate being 64.

Something changed server side, after bloodhound was released, resulting in bad hit registration. Stupid volvo isn't admitting it.

Before bloodhound, everything was fine for me. After this silly new operation, hit registration went downhill for me.

[Peon]

You're not alone, I've found this happening a boat load. The biggest tell tale sign is when you get shot at a distance multiple times from a gun that couldn't possibly have hit you that many times in the amount time you saw the player firing. What do I mean? Take the AK for example. If you're at a distance you have to fire single shots or you won't hit. If you see someone far away with an AK and you instantly die from 4 hits, then you're playing in the past compared to what your opponent was seeing. To him, it seemed like he was firing a long time. Likewise, if you're up close and your bullets aren't registering, then your bullets are delayed in transit and his will affect you before you were able to see him. This crap happens all the time, and it's no coincidence that players with the best scores are also the hardest to hit. I've been on the giving end of this a whole bunch as well, and for a half second it looks like your opponent can't see you, while their bullets appear to be missing. I just have to think this is just how the internet works, and data is constantly being shuffled around.

[Maltazar]

Originally posted by Peon:

You're not alone, I've found this happening a boat load. The biggest tell tale sign is when you get shot at a distance multiple times from a gun that couldn't possibly have hit you that many times in the amount time you saw the player firing. What do I mean? Take the AK for example. If you're at a distance you have to fire single shots or you won't hit. If you see someone far away with an AK and you instantly die from 4 hits, then you're playing in the past compared to what your opponent was seeing. To him, it seemed like he was firing a long time. Likewise, if you're up close and your bullets aren't registering, then your bullets are delayed in transit and his will affect you before you were able to see him. This crap happens all the time, and it's no coincidence that players with the best scores are also the hardest to hit. I've been on the giving end of this a whole bunch as well, and for a half second it looks like your opponent can't see you, while their bullets appear to be missing. I just have to think this is just how the internet works, and data is constantly being shuffled around.

Go back to the AWP thread.

[WD-40]

actually that is true but what also i realised after the bloodhound is that if u hit a guy with the awp some times he dosent die immediatly but takes split seconds as the hit to register and die , it reached a point that i scope again thinking i didnt hit him

[Peon]

Originally posted by Maltazar:

Go back to the AWP thread.

Just another issue in CS land. Both of these issues aren't a lot of fun.

[WD-40]

lol

[THE LORD]

Originally posted by Talha:

actually that is true but what also i realised after the bloodhound is that if u hit a guy with the awp some times he dosent die immediatly but takes split seconds as the hit to register and die , it reached a point that i scope again thinking i didnt hit him

Yeah it happened to me too. I hit an AFK guy 5 times with an AWP before he died. Stupid game.