So, do you feel this is a serious issue or is it acceptable for this release? The problem is with the predictive formula to determine where in the route the runner will be, which can be less than the QB expects because of the acceleration delay or perhaps low route running skill and a cut still to be made (one of the impacts of a low route running is slowing down through a cut). Also, if the DB is hand fighting this is possible to happen because it's upsetting the timing. A third possibility is that the QB has decided to throw the ball further out of reach of the DB, trying to give the WR a chance to make a play on it. But I suspect what you're seeing is the first issue I described.

So again, is this something that needs to be addressed or do you think it's ok to let it go into a future release?

Sometimes it happen when the WR is all alone. That is the most annoying, but I see throws where the QB is leading the WR, which is great, so. Overall, i think it is releasable. It's annoying, but the passing game (O and D) is much better right now, and visually the game looks good. I also see plays i didn't see before.

Next thing i would like to be corrected is the passivity of the defenders (LBs and DBs) against the run. But i suspect that would shut down the run game completely.

I think it's releasable. It's pretty logical and explainable in terms of game play. The QB throws it to where the WR is supposed to be, but the DB prevents him from getting there. That's a good football play.

Thanks for the feedback, guys! If nothing goes wrong over the weekend I'll probably plan to release this early to mid next week.

I still think this is releasable, but the TE turning the LB around can be a bit excessive: https://mfn1.myfootballnow.com/watch/7910#1434617

The LB here has 43 M2M, which is a definite No-No for my defense. But I wonder how many folks this is going to catch off guard.

I'm not sure which WR was targeted here: https://mfn1.myfootballnow.com/watch/7910#1434631

https://mfn1.myfootballnow.com/watch/7911#1434865

Minor stuff, but why wasn't anyone charged with a sack?

I'm pointing out minor things, but I didn't see any problems with pass blocking. I'll have to look at film again.

---

Here's another one where the WR stutters and then cuts and the CB doesn't know what to do: https://mfn1.myfootballnow.com/watch/7910#1434638

This is a 100 vs 100 roll, so it could go either way and I don't see many of them, but I've been recording them when I do.

1) https://beta87.myfootballnow.com/watch/1617#295614
a) A lot of footwork to finally break down the CB on this one.

2) https://beta87.myfootballnow.com/watch/1617#295632
a) This is happening to sub-50 M2M guys a lot. This guy has 35 functional M2M and gets completely lost. What's worse is the safety that is supposed to play the deep half of the field where the WR catches it is almost on the sideline when the play goes down.

3) https://beta87.myfootballnow.com/watch/1617#295702
a) Hmm... this is starting to make me question whether this issue makes 0.4.3 releasable. Again, bad M2M on this LB, but he's no where on this play at all.

I really don’t mind bad M2M ratings making a player unplayable. I’ve felt like low numbers should really be poorer and high numbers should really be more elite than they are now even. If M2M doesn’t matter like this, than you’ll go back to only worrying about speed again.

https://beta87.myfootballnow.com/watch/1612#294759

The RG blocks then peels off or gets blown by then the RB gets destroyed . Why not double the DT . Looks a little strange .