Re: Dodge is not dodging in correct direction

While we're at it, let's ensure the development team is working on this other Day 1 bug, which is NOT working "as designed".  Please make sure that bug does NOT show as resolved in this forum.

Poking the team on the dodge issue and see what they say. 

On the link, you posted @DarthFDG, as my colleague explained that is working as intended and for reference, we did talk to the people designing that system. The topic will remain marked as solved.

/Atic 

I haven't been able to prepare this test yet, I needed to do some Obi-Wan tests that took all my time last time I ahd the chance, but I'll prepare footage for this issue as soon as I get some time

still happening, even with new optical keyboard, although I could swear it is slightly better...

And I can't manage to setup the splitscreen mod since the update prior to last. But it happens to me every HvV match.

---

@EA_Atic wrote:

Poking the team on the dodge issue and see what they say. 

/Atic 

---

@EA_Atic - Any word from Development on this bug?

For what its worth...

I notice it more with Rey - when trying to dodge back, she goes forward.  Quite annoying, as you might imagine.

---

@DarthFDG wrote:

---

@EA_Atic wrote:

Poking the team on the dodge issue and see what they say. 

/Atic 

---

@EA_Atic - Any word from Development on this bug?

For what its worth...

I notice it more with Rey - when trying to dodge back, she goes forward.  Quite annoying, as you might imagine.

---

Nothing?

@EA_Ataashi ?

Getting this in the next update would be a great Christmas present for me.  🙂

Ok so I have a testing case ready for this issue. Splitscreen mod is working flawlessly in this update, so as soon as I get home today I'll share my findings.

I already managed to trigger this bug on purpose in a previous test, I just didn't find an easy and 100% reproducible method to trigger this.

I also believe I proved wrong my theory that the dodge would go opposite of where you want it to go when this bug happens. It certainly seems likely to go opposite, but sometimes it didn't.

Nothing very concrete yet, besides the very real existence of a Dodge BUG which makes you dodge to a different direction from where you commanded it to go, while your character is under some special circumstances.

@EA_Atic 

Ok, got one easily reproducible case:

The situation is the following: As Rey I first dodge backwards, the default dodge by only pressing the dodge button once and nothing more. This is to signal the dodge I'm going to use, the default dodge. I then get Rey back into position and:

- Freeze her with Kylo (and as Rey I start to spam the dodge button with no direction input, which should dodge rey backwards);

- Then proceed as Kylo to hit her in the back, producing a hard stagger.

The BUG is then triggered and the dodge goes to the wrong direction.

I'm still unsure of more specifics, but this case is somewhat easy to reproduce. I have tried with other directions and it seems to affect them all.

I hope this helps on getting rid of this BUG once and for all. Yet another Day 1 BUG never solved.

Great reproduction of the bug.

It would be even more obvious if it showed that she erroneously dodges into the opponent's lightsaber, as has happened to me many times.  LOL

@DarthFDG @EA_Atic 
Ok, after doing some tests because of the Dodge Attacks that were "fixed" in this patch, I found an even better way to reproduce this BUG here.

Hold the attack button and then spam the default dodge as fast as possible (so just the dodge button, no directions). The first one shall behave correctly dodging you backwards, but soon you'll start dodging forward everytime.

Can you test this and confirm if it happens on your ends too? It's 100% reproducible here, tested several times already.

---

@RogueZeroRendar wrote:

@DarthFDG @EA_Atic 
Ok, after doing some tests because of the Dodge Attacks that were "fixed" in this patch, I found an even better way to reproduce this BUG here.

Hold the attack button and then spam the default dodge as fast as possible (so just the dodge button, no directions). The first one shall behave correctly dodging you backwards, but soon you'll start dodging forward everytime.

Can you test this and confirm if it happens on your ends too? It's 100% reproducible here, tested several times already.

---

Not sure what patch you're referring to, as I don't see any release notes about a dodge fix.

When I hold down attack and dodge, it pretty much goes in the direction it should whether I hold a direction key or not.

I did notice that when I hold attack down and dodge back repeatedly, Rey will lunge forward on the next attack. Maybe that's what I've been experiencing all along without knowing it.

@DarthFDG 
'Dodge Attacks' is a label of mine. In the patch notes it's this item here:

Which means they brought back all the specific saber attack animations you'd perform after dodging. I exposed the issue here: https://answers.ea.com/t5/Bug-Reports/You-can-t-Saber-Attack-immediately-after-Dodging-anymore/td-p/8783624

And yes, holding the attack button and dodging backwards will work correctly. But if you keep pressing the dodge button as fast as possible, and not let go of the attack button at any time, you'll see your character will instead dodge forward and attack as many times as your Stamina allows it.

This is definitely not the only case this happens, as in the case before it happened due to spam dodging while frozen and getting staggered out of it, so the attack button wasn't even touched.

But as this case now is easier and 100% reproducible, it might be a perfect test case for devs to finally understand what causes this and fix it once and for all.

@DarthFDG @EA_Atic 

Ok so I finally discovered why this issue happens. I made a topic in the main forum explaining it with detail, which can be found here: https://battlefront-forums.ea.com/discussion/158374/how-directional-dodges-work-and-why-its-a-bad-thing

So I'll make it brief here

This game decides where you'll dodge to based on the momentum applied to your character, rather then the input you provided. Most of the time the directional input you provide will apply the correct momentum and will make the dodge go to the intended direction.

But sometimes, due to specific effects like getting frozen by Kylo and staggered out of it, you'll get momentum due to the stagger, and even if you input your dodge to go to any direction, the game will force you to dodge in the direction the stagger moved you to, just like I showed in a GIF in a previous reply of mine here in this report.

There are many situations that can produce this effect, although being rare. The worst about this issue is that it happens more oftenly when you're in the heat of a battle, facing many opponents at once.

---

@RogueZeroRendar wrote:

@DarthFDG @EA_Atic 

Ok so I finally discovered why this issue happens. I made a topic in the main forum explaining it with detail, which can be found here: https://battlefront-forums.ea.com/discussion/158374/how-directional-dodges-work-and-why-its-a-bad-thing

So I'll make it brief here

This game decides where you'll dodge to based on the momentum applied to your character, rather then the input you provided. Most of the time the directional input you provide will apply the correct momentum and will make the dodge go to the intended direction.

But sometimes, due to specific effects like getting frozen by Kylo and staggered out of it, you'll get momentum due to the stagger, and even if you input your dodge to go to any direction, the game will force you to dodge in the direction the stagger moved you to, just like I showed in a GIF in a previous reply of mine here in this report.

There are many situations that can produce this effect, although being rare. The worst about this issue is that it happens more oftenly when you're in the heat of a battle, facing many opponents at once.

---

A very thorough and insightful analysis in that link, @RogueZeroRendar . Thanks for taking the time to put it together. I know it wasn't something you did in 5 minutes.  🙂

@EA_Atic - If this was a design decision, a few people would suggest it was a poor one; some would argue its a bug. You mind presenting @RogueZeroRendar 's detailed analysis to Development? You might need to show it to someone other than who you spoke with before. 😉