Getting clipped no matter how fast you dash back.

Is anyone getting clipped no matter how fast you dash back. I don't know, it feels the player is stuck in quicksand or molasses as you try to dash back to avoid an sp or a hit. It's as if the defender is moving twice as fast and watching yourself get pounded and you see it coming. Don't know if it's just an input issue or they just sped up the movement of the defender. The defender is moving across and reaching you much quicker while it seem you're moving back in baby steps.

Comments

Sir_Globalot

This is why i'm struggling using Kitty; any time I try get some distance to phase-dash, they close the gap faster than I can even dash. Noticed a lot in the last month or two.

Squirrelguy

To be fair, lots of special attacks and things like that need to be anticipated. For instance, if you just try to dodge Korg’s sp1 beams when you see the gun fire, it’s already too late. You actually have to swipe before the animation happens to properly time the evade. Maybe this is something like what you’re experiencing.

WayWorn2525

To be fair, lots of special attacks and things like that need to be anticipated. For instance, if you just try to dodge Korg’s sp1 beams when you see the gun fire, it’s already too late. You actually have to swipe before the animation happens to properly time the evade. Maybe this is something like what you’re experiencing.

That would be understandable if I started out recently with not much knowledge and experience, but I've been at this game for almost 2 years. Taking your example dodging Korg's sp1 is doable, but if the input is not working according to your tap or it's not moving as quickly as you are swiping back, it's feels sluggish.

WayWorn2525

To be fair, lots of special attacks and things like that need to be anticipated. For instance, if you just try to dodge Korg’s sp1 beams when you see the gun fire, it’s already too late. You actually have to swipe before the animation happens to properly time the evade. Maybe this is something like what you’re experiencing.
That would be understandable if I started out recently with not much knowledge and experience, but I've been at this game for almost 2 years. Taking your example dodging Korg's sp1 is doable, but if the input is not working according to your tap or it's not moving as quickly as you are swiping back, it's feels sluggish.

I wanted to say I do see (or anticipate) the sp coming, but if the input isn't responding to your tap or swipe, anticipating is going to help much.

Malreck04

It's not necessarily about how fast you dash back, timing is incredibly important. If you're spamming dash backs you're almost definitely going to get a mistime in which they can dash in and hit when it is impossible for you recover, in the middle of a dash back.

Shiroihara

It's not necessarily about how fast you dash back, timing is incredibly important. If you're spamming dash backs you're almost definitely going to get a mistime in which they can dash in and hit when it is impossible for you recover, in the middle of a dash back.

Not sure about that. If I spam dash backs, meaning that I dash in sequence as fast as I can from the moment I see the opponent coming at me, but they are still able to reach me mid combo, then it seems to me that their attack is faster than what my defence can be.

WayWorn2525

It's not necessarily about how fast you dash back, timing is incredibly important. If you're spamming dash backs you're almost definitely going to get a mistime in which they can dash in and hit when it is impossible for you recover, in the middle of a dash back.

I agree timing is important, but if the input isn't responding correctly to your swipe and tap, then it's an issue. It's one thing if you don't have the timing down, and obviously getting destroyed by it, but if having the timing down and the input isn't responding to your touch is another.

WayWorn2525

To be fair, lots of special attacks and things like that need to be anticipated. For instance, if you just try to dodge Korg’s sp1 beams when you see the gun fire, it’s already too late. You actually have to swipe before the animation happens to properly time the evade. Maybe this is something like what you’re experiencing.
That would be understandable if I started out recently with not much knowledge and experience, but I've been at this game for almost 2 years. Taking your example dodging Korg's sp1 is doable, but if the input is not working according to your tap or it's not moving as quickly as you are swiping back, it's feels sluggish.
I wanted to say I do see (or anticipate) the sp coming, but if the input isn't responding to your tap or swipe, anticipating is going to help much.

Correction:I wanted to say I do see (or anticipate) the sp coming, but if the input isn't responding to your tap or swipe, anticipating isn't going to help much.

Pikolu

Biggest thing I've seen was in EoP when I would dash back and while dodging back, warlocks heavy would reach forever far and hit me while I was dashing back

Colinwhitworth69

I do feel like sometimes the defender is moving at light speed in comparison to me. I wish I could dash that fast. Maybe when Quicksilver is released...

Carnage313

Yes the speed increase is very apparent. I’m getting hit by specials that I used to be able to dodge with ease. It’s been talked about for months and all that’s ever said is nothing is changed and might be a bug. Then it gets closed and buried in without discussion. Just like the one a day or two ago.

SuelGames

Is anyone getting clipped no matter how fast you dash back. I don't know, it feels the player is stuck in quicksand or molasses as you try to dash back to avoid an sp or a hit. It's as if the defender is moving twice as fast and watching yourself get pounded and you see it coming. Don't know if it's just an input issue or they just sped up the movement of the defender. The defender is moving across and reaching you much quicker while it seem you're moving back in baby steps.

I died yesterday in war cause of this. Oponent was at 1% and i dashed back to avoid getting hit, yet it registred as a parry and the node was reflexive stun, so rip. The timing for evading seems a bit off for a couple months, this used to be something very stupid and straght forward, just swipe left, but its been weird lately, ive been doing accidental blocks/parries when i want to evade and a couple times that can be fatal. I play this for 7 years, i know the evade timing, i cant just suddently unlearn that, something has been off for some time now.

SuelGames

To be fair, lots of special attacks and things like that need to be anticipated. For instance, if you just try to dodge Korg’s sp1 beams when you see the gun fire, it’s already too late. You actually have to swipe before the animation happens to properly time the evade. Maybe this is something like what you’re experiencing.

You are correct on your first sentence. However, Korg s spc1 timing for evade has always been when he pulls the gun, not when he fires, try that and it will work, nothing changed there.

Bugmat78

In case some players haven't realized this yet, there is a period in which the game animations don't allow you to do certain actions as a player but it does for the defender.

For example if you ever check, when you knock a defender down there is a period after that which the animation locks and you cannot dash back. Logically if you or someone in the grind this should be free to move away from them while they try to get up.

Not in this game especially when you play content of a certain difficulty. When you doa knock down and try to move away they are already recovered from being knocked down and following you to clip you in the face, unless you plan/use a light intercept.

If you try to simply dash back your dash back animation will not finish in time to allow you to use block, while their recovery from being knocked down and forward dash can and will somehow get to you in that time span. It's why you have to learn intercepting.

I can never forget the video dinnertime posted once of storm x getting up from a heavy before the heavy animation was finished lol

VegetaNoOuji

Timing in general has been off for a while for me at least, I've been hitting parries instead of dexs or getting hit mid dash back lately that never occurred in all my years prior. Along with light intercepts leading to a punch to the dome piece. Don't know if it's input timing changes, input delay or AI reaction time. Also the hilarity that ensues lately when certain champs can launch a special attack while they're still half on the floor.

Hera1d_of_Ga1actus

Most annoying thing is when you finish combo, try to light intercept, they don't go for it but instead walk to you and when you do a light attack they'll parry. This is like all over the game rn

J0eySn0w

The AI has completely changed. They definitely did something to mess with it. I used to think it maybe cos of input and timing issues but it's not. We have that going and the AI has been tweaked in other modes of the game as well. Anytime I fight Heimdall he spams heavies almost at the same rate Mysterio does, but that wasn't the case at all a year or two ago

BLEEDlNG_DGE

This game has become riddled with timing issues, inconsistencies and changes (that weren't communicated). What I've noticed is the inconsitent recovery time that allows defenders to get up and dash foward with varying degrees of speed. Another is what I call the "stutter-dash", where a defender will first take a normal running step to fool you into thinking their commiting a normal run up which they cancel into a surprise dash right after you dash back, with their attack reaching you just before the animation can allow you to register the next dash back.
Both instances will get you wrecked. Worse, there is no way to anticipate or predict these movements. Whenever you do avoid them, it's pure frame rate luck and their attack will miss you by inches.
My only solution so far... I minimize dash backs to only when a defender is knocked down. Ofcourse this is only a half-measure since it doesn't work during unblockable attacks and is still vulnerable to the varying recovery speeds.

J0eySn0w

It’s very unfair, the AI when they choose to react even if we want to and can response as quickly to counter, the timing, lags, input response or whatever it is we’re not able to. I can tell you how many times I’ve tried dashing back to dex and avoid AI advance but the game doesn’t seem to response as fast I want and faster enough to avoid. Some of their hits either hits my block and catches me. It is what it is at this point. They know it…aware of it, but here we are again with another post on the same issue.

0casual0

Am I getting worse at the game or the AI is getting smarter each day? Also, nowadays the AI know how to "shallow dex" and intercept me right away. It feels worse to get intercept by an AI than getting backhand slap by Doom.

RiderofHell

I been getting clipped before my special animations are even finished by the AI 🤦‍♂️

VegetaNoOuji

After some testing in RoL, I've noticed dashing back with certain champs, initiates a block for a frame or two before dashing back, even though you've never held the block at all in that sequence. That and the fact AI is able to react In places it's never been able to react before, like launching specials when they are still in the invulnerable phases like On the floor or Ms Marvel launched her SP1 while still being partially in her SP2 animation during a power reserve fight, or as mentioned above, AI being able to smack you while you're still on the back end of your own animation. Also the thing where you dash right after a SP3 is back sporadically too.

KattohS

Is anyone getting clipped no matter how fast you dash back. I don't know, it feels the player is stuck in quicksand or molasses as you try to dash back to avoid an sp or a hit. It's as if the defender is moving twice as fast and watching yourself get pounded and you see it coming. Don't know if it's just an input issue or they just sped up the movement of the defender. The defender is moving across and reaching you much quicker while it seem you're moving back in baby steps.
I died yesterday in war cause of this. Oponent was at 1% and i dashed back to avoid getting hit, yet it registred as a parry and the node was reflexive stun, so rip. The timing for evading seems a bit off for a couple months, this used to be something very stupid and straght forward, just swipe left, but its been weird lately, ive been doing accidental blocks/parries when i want to evade and a couple times that can be fatal. I play this for 7 years, i know the evade timing, i cant just suddently unlearn that, something has been off for some time now.

Reflective stun…. the one time parry works flawlessly.