https://www.youtube.com/watch?v=MHgPrEMvcrM
So, it isn't a spectator bug. It isn't ping. It is server desync and needs to be fixed! Can't have a competitive game without correctly showing people where to shoot.
Part 1: https://www.reddit.com/r/VALORANT/comments/i6luok/critical_failure_of_recoil_patterns_between/
External link →I don't know. When you start up a custom game with auto respawn enabled and you start killing someone every frame, the server that you are hosting usually cannot keep up and starts to lag causing the desync you see here. I really think this is too extreme of an example to show "how bad it is". Like the other commenter, I'm not saying there isn't a bug, but I don't feel that OP's post is evidence of it.
Preface: I haven't worked heavily with our combat systems so I don't have a super deep understanding of bullets, but I have worked on our respawn system. But I think you've got the right idea.
It's currently super expensive to respawn an agent in bomb mode, and it looks like auto respawn is infact mega chugging the server. In this video, you can see the server tick rate fall off a cliff from 128 down to like 10-20, my suspicion is that the server is chugging hard to keep up with these respawns and its bullet processing is falling behind as a result. If the server only processes bullets 10 times a second and is also under heavy load trying to respawn the agent many times, it would make sense to me that the hits would register late and the clients tracers would get ahead of them.
We are actively working to improve this and have some prototype respawn improvements in deathmatch that we're planning to bring to standard mode once we're confident they're stable - mid combat respawns are very rare in standard mode (limited to sage res) so we opted to ship them in dm only to see if any major bugs arise.
I'm not claiming that OPs issue is not an issue - I do not have the expertise in this. But I do not think the conditions in this video accurately represent real gameplay - server tickrate is generally steady at 128 throughout the match. And please know that we hear you and we care about this stuff a ton too.
Preface: I haven't worked heavily with our combat systems so I don't have a super deep understanding of bullets, but I have worked on our respawn system. But I think you've got the right idea.
It's currently super expensive to respawn an agent in bomb mode, and it looks like auto respawn is infact mega chugging the server. In this video, you can see the server tick rate fall off a cliff from 128 down to like 10-20, my suspicion is that the server is chugging hard to keep up with these respawns and its bullet processing is falling behind as a result. If the server only processes bullets 10 times a second and is also under heavy load trying to respawn the agent many times, it would make sense to me that the hits would register late and the clients tracers would get ahead of them.
We are actively working to improve this and have some prototype respawn improvements in deathmatch that we're planning to bring to standard mode once we're confident they're stable - mid combat respawns are very rare in standard mode (limited to sage res) so we opted to ship them in dm only to see if any major bugs arise.
I'm not claiming that OPs issue is not an issue - I do not have the expertise in this. But I do not think the conditions in this video accurately represent real gameplay - server tickrate is generally steady at 128 throughout the match. And please know that we hear you and we care about this stuff a ton too.
!pin
I managed to reproduce this with the dummy in practice where no respawn happens.
Thanks for this, this rules out respawn as the sole cause! Once we're back from break I'll chat with the team about it and reference this video.
devtrackers.gg