Nemesis666 wrote: » It's been happening to me too in AW and uncollected event quest. I can't play this until this is fixed.
addisonbassist wrote: » Jaded wrote: » Problem with videos on this issue is how do we know you didn’t accidentally dash back when he hit you breaking your own block? Which causes the same outcome if timed incorrectly. I’m not saying that is what you did, but there could also have been something on your screen causing conflict in the controls. Just hard to prove this problem. Um. Did you look at the screen shots? Block is being held before the hit, and entirely through the hit, until the damage is done. There is absolutely nothing to indicate that I dashed back at any moment while I was getting hit. If it was from dashing back, Iceman would've had to have let go of the block at some point before the hit connected, and that doesn't happen.
Jaded wrote: » Problem with videos on this issue is how do we know you didn’t accidentally dash back when he hit you breaking your own block? Which causes the same outcome if timed incorrectly. I’m not saying that is what you did, but there could also have been something on your screen causing conflict in the controls. Just hard to prove this problem.
addisonbassist wrote: » Jaded wrote: » the video and photos prove nothing because we don’t see your fingers and their movements So, what you're saying is that character movements don't reflect device input, further proving my point that there's a problem that needs to be fixed. What you're saying clearly did not happen... but even if it did it still represents a glaring issue that is confusing to players and needs to be addressed.
Jaded wrote: » the video and photos prove nothing because we don’t see your fingers and their movements
rockykoston wrote: » Jaded wrote: » addisonbassist wrote: » Jaded wrote: » Problem with videos on this issue is how do we know you didn’t accidentally dash back when he hit you breaking your own block? Which causes the same outcome if timed incorrectly. I’m not saying that is what you did, but there could also have been something on your screen causing conflict in the controls. Just hard to prove this problem. Um. Did you look at the screen shots? Block is being held before the hit, and entirely through the hit, until the damage is done. There is absolutely nothing to indicate that I dashed back at any moment while I was getting hit. If it was from dashing back, Iceman would've had to have let go of the block at some point before the hit connected, and that doesn't happen. Not true at all, if improperly timed it can look like a hit through a block. Again read what I said, I am not saying that this happened to you exactly. But it’s more of a case of how hard it is to prove this problem. Edit: the video and photos prove nothing because we don’t see your fingers and their movements Kabam Rep confirmed!! It isn't a problem unless you say it under oath, with 25k witnesses present, on a mic / on a podium in front of white house. Even then, you will be ignored because it is your opinion and not an actual problem!! Honestly, this happens only when AI difficulty level is greater than expert. Not sure why or how, but this happens a lot on my Android device. I'll block or parry and get hit, even though I know I timed it perfectly.
Jaded wrote: » addisonbassist wrote: » Jaded wrote: » Problem with videos on this issue is how do we know you didn’t accidentally dash back when he hit you breaking your own block? Which causes the same outcome if timed incorrectly. I’m not saying that is what you did, but there could also have been something on your screen causing conflict in the controls. Just hard to prove this problem. Um. Did you look at the screen shots? Block is being held before the hit, and entirely through the hit, until the damage is done. There is absolutely nothing to indicate that I dashed back at any moment while I was getting hit. If it was from dashing back, Iceman would've had to have let go of the block at some point before the hit connected, and that doesn't happen. Not true at all, if improperly timed it can look like a hit through a block. Again read what I said, I am not saying that this happened to you exactly. But it’s more of a case of how hard it is to prove this problem. Edit: the video and photos prove nothing because we don’t see your fingers and their movements
Blitzkilla420 wrote: » Jaded wrote: » Problem with videos on this issue is how do we know you didn’t accidentally dash back when he hit you breaking your own block? Which causes the same outcome if timed incorrectly. I’m not saying that is what you did, but there could also have been something on your screen causing conflict in the controls. Just hard to prove this problem. its 2018. do you really think its our phones still? the game still needs a lot of fixing up to do. whats the point of new content if simple gameplay mechanics dont work? also he has video proof hard to discredit that. plus the mods always ask for video evidence so here we are and dude hes HOLDING block so dont think hes dashing back but the AI hits right thru it
addisonbassist wrote: » Once again, my obtuse little friend... If even the smallest finger twitch is registering server-side as movement but I am unable to see that movement on my side at any point during the animation, there is still a problem, whether that is what happened here or not.
addisonbassist wrote: » chunkyb wrote: » But he is right. Without seeing what is physically happening, you can't 100% say whether it's a user-dropped block or a hit thru a block. You're missing an entirely separate point. EVEN IF THAT WERE THE CASE, THE FACT THAT USER INPUT DOES NOT EQUAL WHAT YOU SEE HAPPENING ON SCREEN IS ALSO CLEARLY A PROBLEM. It doesn't MATTER that you can't see input blips on the screen during the video, what matters is that it's impossible to tell whether I messed up or if Kabam messed up... if that's because of user error, or lag, or whatever, it doesn't matter because IT'S A PROBLEM FOR USERS AND FOR KABAM. Both issues... user input not being reflected on screen and getting punched through blocks... have to do with lag that is affecting gameplay, both mechanically AND visually. It makes the gameplay experience incredibly frustrating and should be reported. Over and over and over again, ad nauseam, until it's fixed.
chunkyb wrote: » But he is right. Without seeing what is physically happening, you can't 100% say whether it's a user-dropped block or a hit thru a block.