Gun not firing in CS:GO

[Tympanista]

EDIT: Issue fixed a while ago. Odd mouse problems.

I've found that, every now and then, I can't fire AT ALL when I aim at something destructable or an enemy when using an accurate weapon. What basically happens is I line up a good shot, click the mouse, nothing happens, and then I get destroyed by the player who thinks he justt saw a guy ♥♥♥♥♥ out and lose control of his hand. I've had to use shotguns and spray with SMGs for the last few matches so i wouldn'nt have to deal with that ♥♥♥♥♥♥♥♥.

I've confirmed this problem while doing aim training on the workshop map with the targets that pop up. I can shoot and miss over and over again, but as soon as I get good crosshair accuracy, the gun won't fire.

Is this a game issue? I've had friends tell me the same thing is happening to them. And is it going to be fixed too if it is a game issue?

EDIT: Issue fixed a while ago. Odd mouse problems.

[Vic]

It seems to be happening to me too, I honestly thought it was an issue with my mouse.

[Tympanista]

Same here. I've also found that it is not likely to be a problem with Windows 8's laptop settings for trackpad intereference with typing.

[JuanDiego Montoya]

Heard of the many complaints about their 64 tick servers they have hosting CS:GO? This is why. The servers don't refresh fast enough to register a hit that you saw, so it shows back up on your screen as a "miss" even though you clearly shot it. There's videos on Youtube that back up peoples' complaints on this terrible phenomenon. I saw a video that showed two people having a pistol fight, about medium range, with sv_showimpacts on so they can see when THERE OWN COMPUTER registers a hit. The battle continues, the first guy has many hits on the other, according to the blood splatter as well as sv_showimpacts making a ghost of the player where they were when hit. About 4-5 hits I believe. It seems like the second guy is almost dead... but he manages to kill the first and, lo and behold first guy only has like 2 hits on the other because the slow servers didn't see the computer's "hit" as a "hit" and so counted it as a "miss" even though that's wrong.

[Vic]

Originally posted by GeT_ShReK'd:

Heard of the many complaints about their 64 tick servers they have hosting CS:GO? This is why. The servers don't refresh fast enough to register a hit that you saw, so it shows back up on your screen as a "miss" even though you clearly shot it. There's videos on Youtube that back up peoples' complaints on this terrible phenomenon. I saw a video that showed two people having a pistol fight, about medium range, with sv_showimpacts on so they can see when THERE OWN COMPUTER registers a hit. The battle continues, the first guy has many hits on the other, according to the blood splatter as well as sv_showimpacts making a ghost of the player where they were when hit. About 4-5 hits I believe. It seems like the second guy is almost dead... but he manages to kill the first and, lo and behold first guy only has like 2 hits on the other because the slow servers didn't see the computer's "hit" as a "hit" and so counted it as a "miss" even though that's wrong.

http://www.youtube.com/watch?v=J6u26YTpIF0
This video?

[ShadowzBane]

Yah latency issue... what'cha going to do?

Often when I play I hear the familiar headshot helmet sound 4-8 time (automatic weapon)
Low and behold 1-none of those hits register... next thing I know I'm dead with the server telling me I can't hit ♥♥♥♥♥♥♥♥♥ =S.

Just cause you hit something on your side (client) doesn't mean the server acknowledges it...

[ikke en and]

Ya horrible lag compensation. Need to be fixed ...

[Karellen]

Originally posted by Tympanista:

Same here. I've also found that it is not likely to be a problem with Windows 8's laptop settings for trackpad intereference with typing.

How is this relevant?

[H.E.R.O]

you mean "hit detection" .. and yes . csgo is a piece of ♥♥♥♥ . with ak first shot, my crosshair sits tight on enemies face and I literally do 0 damage .

[SheetznGiggles]

This is a well known issue valve refuses to fix and instead comes up with excuses why it should stay bad.

[LoNeZiLLa]

I have noticed the same issue.
Lets say the enemy is running from the left side of your screen to the right, and you click Mouse1 once their head is in the center of your crosshairs. The shot won't register.
But if you fire and follow the enemies head afterwards, the shot will register.

If you do the same test on CSS, your shot will register as soon as you shoot.

[Ch@os]

thats why i only play with the p90 and with the shotgun really the hitdedection is horrible.
the only thing you can do is pre firering like a badass.

[Ξ︎∨○︎L∨Ξ]

It's (server) lag or packet loss.



http://www.youtube.com/watch?v=J6u26YTpIF0
[/quote]Demo videos are complete ♥♥♥♥♥♥♥♥.

[Ξ︎∨○︎L∨Ξ]

Originally posted by GeT_ShReK'd:

Heard of the many complaints about their 64 tick servers they have hosting CS:GO? This is why.

64 tick is not the cause of this. It's actually a bit easier to lucky hit somebody on 64 tick servers.

[Arabsky.Rytir]

try to change netcodes "like lerp , rates" it helps alot.

[Tympanista]

*FACEPALM* I understand the lag problem with hits not registering, but that is not what I'm talking about. Please actually read what I'm talking about.

The problem I'm facing is that a gun aiming directly at someone WILL NOT FIRE. Understand? The issue I'm having is basically like a gun jamming curse.