Replying to @LincolnMargison @raratoman
I tried after giving them some time to move out of spawn and throughout matches and it’s the same with the positions updated, but it’s not always showing everyone’s diamonds I think so there’s probably more to it.
Can’t really think of a reason why they would hide the models but still deliberately show the diamonds so yeah there’s something weird.
41
I saw this other clip of basically the same thing happening. I don't think I've ever seen the diamond be separated from the player model like that in previous titles so maybe it just shows the effects of lag or mispredictions while the enemy is culled or something. Maybe the server is indeed not unculling enemies when it should either. teapawt.net/OwNLY_HFA/status/21161…
1
1
109
Replying to @LincolnMargison @raratoman
I agree about the hit registration/miss. Interestingly though, the diamonds of culled players will often still show, which you can test by cutting your connection and walking around. I had inconsistent results while quickly testing this though. Sometimes I wouldn't see any diamonds at all or just on one or two enemies. Maybe they show whenever the server decides to share limited info about culled enemies, like the location of their footstep audio or gunfire and things like that.
1
113
Replying to @Xanthais
Definitely broken lol. However there is no netcode involved in the firing range as it's just local/offline. It's just a bug with the dummies that almost certainly has nothing to do with the mp experience.
1
26
Replying to @Xanthais
It’s definitely nothing new, but I don’t know what causes it and sometimes it doesn’t happen at all. Similar clip from BO6 I found on Reddit.
1
1
41
Replying to @Xanthais
From my experience this will randomly happen in the firing range in the last couple of titles. I doubt this is related or can be attributed to whatever hit reg issues people are experiencing in mp.
1
3
74
Replying to @subonekd @geekypastimes
Surely they have to account for latency and predict peeks and movement by a pretty big margin so that the enemy is unhidden shortly before becoming ”visible”, so that this doesn’t happen. I guess this would give cheaters a small, but maybe negligible, heads-up still?
Also I assume your client still has to receive some kind of location data from any audible enemy. Might not be a big deal since you should be able to hear where they are anyway though.
80
They match perfectly when I compare them, give or take a frame since the clips have different frame rates. The post was just about the killcam looking choppy, it was a fair death.
38
Replying to @ChadOfDuty
Copy! That’s not how it worked in previous games but it could be a conscious decision to have it work like that now.
1
31
Nothing surprising, but if anyone's interested, a look at the server send rate in the MW4 beta shows the usual 64Hz in multiplayer, and roughly 20Hz in Warzone Resurgence.
1
9
539
Replying to @ChadOfDuty
Quick Fix does not appear to activate when damaged while already on an objective, only when entering the objective does it activate. I assume this is a bug because it doesn't match the description and was not the case in previous games. Also there should definitely be a visual cue for when attacking someone with active Quick Fix.
1
3
243
Depends on who you ask I guess. Someone who thinks a clear and demonstrated bug on the map is in fact intentional hit box shrinkage might also think that multiple people have proven it, a more sensible person might not think so. teapawt.net/freund_cod/status/1985…
Replying to @PronounPolice88 @SenseiLeCake
Oops! Wrong again. It's a bug on the map.
I guess it wasn't the evil patent this time either.. Dang. Keep guessing!
47
Replying to @lql_00 @lukkin_ahh
Aim assist will not affect the actual hit boxes or hit registration, and there’s no bullet magnetism. I’ve never heard about that being a thing, at least.
1
39




