[Fixed] Simultanious shoot displays but misses
MME displays the recorded action exactly same frame, same as it looked ingame.
this can mean:
A: either rail can miss randomly (enemy was going backwards towards aiming direction)
B: Rail is displayed before client recives packets from the server which would also cause a lot of fake misses.
or some other stuff.
either way, hf.
Do you have the demo?
Edit: If not, just tell me what ctg were you playing, also if you can make same screenshots with the bounding boxes drawn, and what was the ping of you and the other guy.
bounding box doesnt matter, enemy was stepping back and i was exactly on his balls, pings were lower then 72 msec.
Hm, in that case your right, cuz even when hitbox is made smaller by cfg aiming there is almost a certain hit.
Ok, then it seems to be problem #1. Problem #2 just happens in-game when xp_delagWeapons is enabled because the rail trail is predicted, but if its recorded on a demo then it means the rail actually fired, because demos are recorded using the information sent by the server. That means that the yellow trail shot first and missed and then the other guy fired right after that and hit.
As for the reason of the miss, i dont have an explanation. The only thing i can think of is an engine bug, as it happened with the no self-knockback bug.
This is serious bug, at first I tried to ignore it,
but it happens so often that it drives me crazy.
I'm a railing guy, I focus on killing with rail,
rest of weapons I use to fill the gap between rail cycle time.
To be honest on fw/cw it happens to me like 5 times per map.
And on servers like rail4ever it's just unplayable when 1/3 doesn't hit.
imo it's most important job now, to fix it and forget about it xD
ok now this is kinda odd imo, the enemy went through the nade (ping of the player who recorded was around 94-100
That's a feature, not a bug xD. Starting from 13 Dec server update projectiles are unlagged on close combat (first 300 msec of the projectile life).
but why did it miss? it was totally on the enemy.
Exactly for the same reason rail goes through players sometimes: because after applying the missile ping to the players positions they are not in that place, so there is no hit.
Fixed the issue with projectiles.
A demo to the first issue could help if it still happens.
got demo, but will just send it over on need.
bounding box doesnt matter, enemy was stepping back and i was exactly on his balls, pings were lower then 72 msec.
hurrenson: "This idiot is apparently not familiar with a rail/sniper style."