Looks like it was your ally that hit the shot at 3 seconds in your clip, then you landed two shots (one mid jump at 6 seconds and another one after they landed)

The sparks that show up there are server-side hit confirms, which means a shot was registered and damage was dealt

^ this

...actually some new tech got turned on this patch, which allowed the temporary invulnerability on Omen's ult to carry over on respawn. This has been fixed! Your games should be safe from Invulmen

👀

We are aware of this issue and are looking into it!

I think the bots use different tech than players do for rewinding- looks like there's possibly an issue with the bot hitbox getting desynced. Thanks for the report and video!

Ty, looking into it. From these gifs here it looks like there isn't a hitreg bug- but it IS super confusing that the hit impacts and tracers (which are delayed) can appear over the head when a player crouches, making it look like it should have been a head shot when it was actually a body shot. No bug here that I can see, but definitely a good candidate for some QoL changes to make this less confusing

Tagging is helpful- I check each of these posts! Definitely not ignoring you guys, I was just on vacation.

That is absolutely not true. I'm looking for hitreg issues (and talking about hitreg issues) all the time. We care a lot about this- but text anecdotes are a terrible way to go about narrowing down the problem. There are lots of connected systems that are a part of hitreg, investigating off an anecdote is not particularly helpful.

That being said, this video is excellent! Really well done here- just enough footage before the bug, slow-mo during the bug, and just enough time after the bug. You've also got your FPS and packet loss in the clip and ping in the comments! This makes it a lot easier to follow up on- video of the incident and the conditions in which it occurred are really helpful. Given your conditions (18 ping, 180fps, 0% packet loss) hitboxes should be almost perfectly synced, but it looks like they're not. There's probably a bug here.

Thanks for the video! This video is an excellent example of what we look for in a video about a bug- there's just enough context for before and after the bug occurred, which helps narrow things down. Lovely.

I found a repro for this bug- it looks like it's possible to fire the OP on the server while the client is still readying the OP if you attempt to fire it within a small window while equipping after using Omen ult. This puts the state machine of the gun out of sync on client and server. This causes other weird downstream effects like mentioned in the comments here- stuff like the reload not visually occurring on the client. Just found the bug so no ETA on a fix, but we have eyes on it now. Thanks again for the video!

Yay! Thanks :)

Appreciate it! Always happy to look into potential hitreg issues.

TL:DR Looks like there may be a bug here with the way we're representing the impacts on the smaller target, but otherwise things should be okay here.

There's a couple of things here to talk about:
1.) Hit impacts and the way they are being represented on the tiny target. The hit impacts for the weapons on the larger target should be accurate, but the ones on the smaller target are not- notice the real hit impacts are in the center of the crosshair, and the ones on the smaller target are off-center. This is most likely a bug with how those hit impacts are being represented on the tiny target, and not the shots themselves being fired too low.

2.) The headshot on the bot. The bots' models are a bit thinner than their actual hitboxes, if you shoot slightly around the bots you should see hit impacts and deal damage in most cases- this includes the top of the head. This is true for many of the agents as well- all agents share the same hitbox, but have slightly di...

The bug affects players at all FPS ranges, but scales in severity the lower you go. At 30-15 FPS it gets pretty bad- not hugely bad but bad enough that the shots (as seen in your video) would miss a moving target if you were lined up directly on them. I believe that's what is going on in the video you linked here- you can see the player dips to about 70 fps while shooting- low enough for the hitreg desync to be large enough for the shots to miss.

I'm not sure yet, I imagine more color options is not off the table.

I can talk with some folks about it, yeah. As I understand it it's a competitive advantage question- do we allow a setting that helps alleviate the 'headache' problem if that setting is a must for competitive play? I'm sure there's more to it than that, but that's my simple understanding of the problem in adding that setting for now

Edit: Don't worry about shooting stuff my way that's not out of my domain- my domain is rather broad (most of the underlying game tech is done by my team, stuff like movement, HUD, UI, Hitreg, Wall Pen, etc etc). If it's something I don't have knowledge about I can direct you to the right folks to talk to

If only all the FPS games I loved had perfect hitreg!

Thank you, I very much appreciate the kind words :)

This is a great video. We're looking into it!

Thanks again to all you wonderful people out there reporting bugs with videos- it makes reporting and fixing these much smoother.

Really appreciate that, thank you :)

We're still digging to fully understand what's happening. I can't confirm that we'll have a fix by next patch once we confirm where the bug(s) are, but we're trying!

Thanks for the link! Looking into this as well.