Honestly, I’m hoping they will take a close look at hit boxes in general. I’ve been getting clipped by one hit but dexing the rest of a combo, having hits registered where the contact point isn’t anywhere near my champ…I don’t have the exquisitely detailed visual documentation of the OP, but I’m confident I’m not the only one who’s experienced erratic hit boxes.
That’s an amazing recovery mid-combo by Bucky. If you slow it down to 0.25 speed, you can even see Shang with hands on just as WS pivots to his special.
@DrZola This happens all the time in different ways you see the OP was doing a heavy and it missed, I was just attacking and it missed and unless your a content creator most people don’t sit around recording fights to catch it.
I've had this happen where Hercs foot is halfway through the AI's face but it doesnt register as a hit on a stand up heavy intercept. Then I eat a special.
Well done OP for having decent evidence of what you saw, makes it harder for the "I havent seen it therefore it doesnt exist" crowd to poo poo your post.
Don’t know what you all are complaining about… this has already been explained. The AI we are facing just “rolls the dice,.” In these circumstances, the dice came up “ignore all inputs and interactions and wreck the attacker.” Hopefully next time dice comes up “take the hit as normal”
@GrandOldKai It applied the slow because I made contact the defender is just able to attack through my attack which is a huge issue but imagine you’re in BGs or AW and this happens and you are not as lucky as I was to get out of the way, you get slapped up and game over.
Not my analysis (and I can’t recall whose it is), but some of this looks like synchronization between what we see and what the game thinks is happening.
@DNA3000 are there more server calls in the current game (perhaps to check for cheats) that might cause what we see on our devices to deviate slightly from what the server *perceives* to be happening? Or is this just a hit box malfunction?
Maybe we can blame the server and the game engine for why the inputs and AI are acting ridiculous but what I have leaned in life is when issues come up people blame everything and everyone but them self and the issues don’t get resolved.
Not my analysis (and I can’t recall whose it is), but some of this looks like synchronization between what we see and what the game thinks is happening.
@DNA3000 are there more server calls in the current game (perhaps to check for cheats) that might cause what we see on our devices to deviate slightly from what the server *perceives* to be happening? Or is this just a hit box malfunction?
Dr. Zola
I don’t think so. This feels more like a left hand not knowing what the right hand is doing on the client side. Collisions with hit boxes in Unity games are probably not like sprite collisons - I.e. the game isn’t literally seeing if your pixels touch the opponent pixels. It’s done with geometry calculations. And the thing I most suspect here, although this is pure speculation, is the way the game handles timing.
Imagine two light sabers swinging at each other. We know in the real world they would hit each other, but at what exact moment in time does that happen? Now imagine this happens in a game world where everything happens in ticks of a clock. What happens if that collision happens between clock ticks? It could, in a sense, not happen because the game “sees” the light sabers here before the collision and there after the collision but doesn’t understand there’s physics happening on between those moments. And the thing that’s had the most overhauling in recent times is the handling of time, due to the iOS clock bug in Unity that threw off inputs and well timed actions (aka Parry). And we’ve seen sporadic instances of games running on devices with nonstandard frame rates doing funky things. Maybe what we’re seeing here is a collision our eyes see and some parts of those game engine “see”, but other parts of the game engine don’t “see” and that results in an odd malfunction.
This is, as I said, pure speculation, but that’s where I would look if it was me troubleshooting the problem, absent additional clarifying technical information.
This just happened to me after trying to time a heavy during a relic stun. Stun ended early and defender ignored my heavy and sp1 to my face. Kicking myself I wasn't recording, but this was not the first time.
This is just one of the many reasons why we complain so much! 💩 like this makes the game frustrating to play and it shouldn't be
I had this happen in the final war of the season. Almost flawless fight and Longshot somehow launches an SP2 after I’d connected with the first hit of my heavy and it’s an instant KO. Absolute joke. We were ranked 4th in P3 at the time and going for P2. All wars are ridiculously close at that level, so 1 lost AB could be the difference between a P2 & P3 finish. Fix the bloody game! Do you Kabam people actually care about any posts on forums other than the ones that garner a “frightening” warning message for using a naughty word?
Wow. LS somehow slip the second hit of your heavy and throws a special 2. I'd like to see Kabam explain that one!
This has been happening forever. It's even better when you try to sp intercept you hit th sp and they throw thier sp mid- dash its like it overrides your sp and you take it straight to the face.
Yup! I've had that happen before too!! It almost as if the AI senses when our finger is closing in on the special attack 😂
But let us try to BAIT the AI special.....be dancing around all damn day 😂
My champ CMM, clearly hits the defender, but it's not counted as a hit. Defender even lights up from contact, and you can even hear the hit, but it's still not counted as a hit. 🙃 This has happened so many times! Finally able to get some proof.
If you heavy and the special has been initiated your heavy or basic hits basically get phased in preference to the special. Got caught with it far too often in AW. That heavy gets cancelled by a special starting mid-heavy.
He was stunned when I first made contact though. A special shouldn't cancel that
Don’t know what you all are complaining about… this has already been explained. The AI we are facing just “rolls the dice,.” In these circumstances, the dice came up “ignore all inputs and interactions and wreck the attacker.” Hopefully next time dice comes up “take the hit as normal”
Along the same hit box lines, I'm wondering if there's been video evidence of the range of the defenders specials. I'll be a dash back away when they release their special and do another dash at the same time they release their special and somehow I'm only blocking the special instead of evading it all together. I assume it's not just me.
Not my analysis (and I can’t recall whose it is), but some of this looks like synchronization between what we see and what the game thinks is happening.
@DNA3000 are there more server calls in the current game (perhaps to check for cheats) that might cause what we see on our devices to deviate slightly from what the server *perceives* to be happening? Or is this just a hit box malfunction?
Dr. Zola
I don’t think so. This feels more like a left hand not knowing what the right hand is doing on the client side. Collisions with hit boxes in Unity games are probably not like sprite collisons - I.e. the game isn’t literally seeing if your pixels touch the opponent pixels. It’s done with geometry calculations. And the thing I most suspect here, although this is pure speculation, is the way the game handles timing.
Imagine two light sabers swinging at each other. We know in the real world they would hit each other, but at what exact moment in time does that happen? Now imagine this happens in a game world where everything happens in ticks of a clock. What happens if that collision happens between clock ticks? It could, in a sense, not happen because the game “sees” the light sabers here before the collision and there after the collision but doesn’t understand there’s physics happening on between those moments. And the thing that’s had the most overhauling in recent times is the handling of time, due to the iOS clock bug in Unity that threw off inputs and well timed actions (aka Parry). And we’ve seen sporadic instances of games running on devices with nonstandard frame rates doing funky things. Maybe what we’re seeing here is a collision our eyes see and some parts of those game engine “see”, but other parts of the game engine don’t “see” and that results in an odd malfunction.
This is, as I said, pure speculation, but that’s where I would look if it was me troubleshooting the problem, absent additional clarifying technical information.
Right. That’s what I mean by synchronization, which is likely not the technical term for it. That was how the Unity bug/fix felt a couple years ago—players had ingrained the parry/block muscle memory and suddenly found it didn’t work any longer. That timing element (especially in a game that relies on fairly precise timing) threw everyone.
I’m beginning to think something like this is the culprit behind many of the mechanical issues that seem to plague BGs periodically. One example I encountered yesterday was punishing specials—specifically Chavez, who managed to dex my super fast swipe in from close up to punish her Sp1 but couldn’t evade my swipe in from further away on a subsequent Sp1. Just one example, but things like that make me question the reliability of the way the game *sees* the fight.
Comments
Dr. Zola
I guess the hit box got really, really small.
Dr. Zola
Well done OP for having decent evidence of what you saw, makes it harder for the "I havent seen it therefore it doesnt exist" crowd to poo poo your post.
how'd Slow still trigger?
@DNA3000 are there more server calls in the current game (perhaps to check for cheats) that might cause what we see on our devices to deviate slightly from what the server *perceives* to be happening? Or is this just a hit box malfunction?
Dr. Zola
Imagine two light sabers swinging at each other. We know in the real world they would hit each other, but at what exact moment in time does that happen? Now imagine this happens in a game world where everything happens in ticks of a clock. What happens if that collision happens between clock ticks? It could, in a sense, not happen because the game “sees” the light sabers here before the collision and there after the collision but doesn’t understand there’s physics happening on between those moments. And the thing that’s had the most overhauling in recent times is the handling of time, due to the iOS clock bug in Unity that threw off inputs and well timed actions (aka Parry). And we’ve seen sporadic instances of games running on devices with nonstandard frame rates doing funky things. Maybe what we’re seeing here is a collision our eyes see and some parts of those game engine “see”, but other parts of the game engine don’t “see” and that results in an odd malfunction.
This is, as I said, pure speculation, but that’s where I would look if it was me troubleshooting the problem, absent additional clarifying technical information.
That Tigra block hit parry videos are already forgotten and eating dust.
But let us try to BAIT the AI special.....be dancing around all damn day 😂
Let me spew some curse words real quick to see if that gets their attention lol
Video number 2 is in comments.
you know , like The Amazing Ingenious ?
Joking aside , this happened to me a few times , as well. alongside ai dexing heavy back to the wall.
I’m beginning to think something like this is the culprit behind many of the mechanical issues that seem to plague BGs periodically. One example I encountered yesterday was punishing specials—specifically Chavez, who managed to dex my super fast swipe in from close up to punish her Sp1 but couldn’t evade my swipe in from further away on a subsequent Sp1. Just one example, but things like that make me question the reliability of the way the game *sees* the fight.
Dr. Zola