2 critical buggy ISSUES in RUN + How to fix it

[SUGATA]

Run input was changed.

ISSUE #1 - Run input is WRONG.
Now for Run we need to click LS BWD or FWD and then click OR holding LS FWD - this is wrong, b/c:
I want to make a bait by BWD Dash (minor lunge) into FWD Dash by clicking LS = and instead of BWD>FWD Dash bait i getting Run startup which has another properties.

This issue is affecting this GPD's tip:

Quote:

you can chain fwd/back minor lunges and chain into strikes out of them as well. People have been doing that with the straight for months in the game.

> How to fix: make input for Run by HOLDING 2nd LS input after 1st BWD/FWD click; click 2nd LS input - for Dash , not Run.


ISSUE #2 - After several Dash with Strikes inputs a RUN becomes UNAVAILABLE.
I dont now the exact bug trigger scenario, i think it is triggering by some Dash-Strikes series, so my character is loosing central line, and it becomes impossible to make correct inputs for Run. As you can see in my videos at the end i can not to input Run.

> How to fix: FIX CAMERA ROTATION! It is terrible b/c it is not only changing the LS input direction relative to camera angle (which 50% of time causing wrong LS direction inputs especially in Lunges) but also provokes bugs and issues.

[SUGATA]

Am I the only one who meet this bug #2?
It is easy to recreate : go to practice , start to perform different footwork with striking (dashes, lunges, etc) with camera moving .... and after several minutes the Run input will fail and Run becomes to be impossible.

[johnmangala]

True, the sprinting or running has a bit of a difficult input. I think if it were multidirectional it would be more fluid. Or at least give it a more easy input as you suggest.

[SUGATA]

Quote: Originally Posted by johnmangala

True, the sprinting or running has a bit of a difficult input. I think if it were multidirectional it would be more fluid. Or at least give it a more easy input as you suggest.

Old input was: from any Dash (minor) or Lunge (major L1/R1) click and hold LS FWD to Run.
The current inputs (by clicking FWD is enough for Run, w/o need to _hold_ LS FWD) restricts buffering/chaining scenarious in Dashes.

But the #2 bug not depends on input difficulty. It happens after several minutes of footwork (for me 2-3 minutes) sooner or later (very welcome suggestions about exact bug trigger scenarious) - you simply can NOT Run anymore UNTIL new round begins (i.e. reset position)! This is a BUG, very strange that nobody noticed it...

[Solid_Altair]

I had that bug happen to me on pracice mode, too. Did it ever happen in a fight for you?

[SUGATA]

Yes, don’t know the exact trigger scenario , need more testing
I am pretty sure it is causing by Camera rotation and follow up changes in relative direction input by LS. It also causes much problems to me in right inputs for Dashes/Lunges - VERY OFTENmy character stepping not where I wanted too b/c of camera angles.
This was NOT a problem at all in UFC 1 - 2, where camera was NOT so circling.
May be grappling moves clinches resets this bug, so in modes w/o grappling this issue may be more critical.
> Needs to return that old camera w restricted rotation at least! It is breaking gameplay very much!

[Solid_Altair]

Quote: Originally Posted by SUGATA

Yes, don’t know the exact trigger scenario , need more testing I am pretty sure it is causing by Camera rotation and follow up changes in relative direction input by LS. It also causes much problems to me in right inputs for Dashes/Lunges - VERY OFTENmy character stepping not where I wanted too b/c of camera angles. This was NOT a problem at all in UFC 1 - 2, where camera was NOT so circling. May be grappling moves clinches resets this bug, so in modes w/o grappling this issue may be more critical. > Needs to return that old camera w restricted rotation at least! It is breaking gameplay very much!

I think the camera rotates less in wide angle. You might want to try it out.

[SUGATA]

Quote: Originally Posted by Solid_Altair

I think the camera rotates less in wide angle. You might want to try it out.

May be
Anyway these 2 issues I hope will be fixed in next patch