https://private-gm-nfl.myfootballnow.com/watch/3564#616100

No matter how overpowered the coverage is in 4.6...blanket the entire time of this play...Why did the QB just stand there after the first sack attempt. Broken tackle bug?

cares about a stuck QB, doesn't care about a cumulative negative play differential.
Meh, Ima just shove this under the same miniscule doesn't matter file that made me stop feilding a team.
Y'all said the small stuff doesn't matter, and in comparision to a bug that impacts 70%+ plays, this doesn't matter.

...but it definitely does.
Pardon my dismissal of every bug until the defensive play advantage is fixed :)
Happy turkey killing day!

Long pass, which is not allowed to hit vertically on over the top streak. Engine didn't allow for a scramble here but did the next play. It got stuck when it didn't go to the QB scramble and the coding halted it from flinging it over the top, therefore, QB stood in frozen isolation until brought down.

....someone can slo-mo it to check if the WRs are way open down the field and that would paint the complete picture.

Update: their covered, no one to throw to.

Totality = bug to not allow the long pass to be effective

There are more plays we can not use than plays we can in 4.6.
Fix it.

It's not a bug, this was a so-called fix that was never re-addressed post 4.3.

all WRs well covered, plenty of time to run. 2 lb's in the middle, but so. much. room available to decrease yardage lost - or even a possible yardage gain.

Clearly no throw options, absolutely qb run options.

Good catch, good topic, add QB scrambles to the fix it pile.

The AI, upon any breakdown of any user play or any play called by the offense during the predetermined order of operations should always seek a positive net yardage.

Although a positive gain may not ultimitely be realized, the AI should make the effort after following through all existing and pre-determined outcomes.

The code hit an endgame without an end result of seeking a positive yardage result.
Seeking positive yardage as the final "Z" - or last option is, obviously, not coded.
Thus, QB is stuck.
It is important to understand the QB AI has already directed to a QB scramble, refused/failed, and did not return to a QB scramble in the check down cycle (yet continued to do WR checkdowns and countinued to loop WR checkdowns without any further QB options).

In the above case, with all WR covered through 2 checkdowns, the code should funnel into either A: throw to sideline or B: QB scramble.
z=(A or B)

Everything went perfect according to 4.6 code.
Which ought to underline how bad 4.6 is.

**IN case the defensive play familiarity bug was not enough, already.**

There are no "qb throw aways" to the sidelines in MFN to prevent a loss of yards, nor is there more than one opportunity in the code cycle for a qb scramble.

~CSB remebering post - post to unsubscribe from the thread and having to edit yet a billionth time to correct it so I don't get MFN EMAIL SPAMMED> UGGGGGGGGH!

FIX this ****.

btw, kudos to that O line, serious meaties.