The engine seems a lot better. Here's a couple of good examples with one bad play or really just the text didn't match the play. And that happened a few times but I could only find the one atm. But all in all you could see the QB's going through their progressions when they had time and checking down at times.
I think that the text play calls could be more generic and sometimes not needed. When a QB has been pressured we already know why the QB made a bad throw. And for example instead of saying a wobbly pass maybe just say the QB made a bad pass to generalize it. That kinda covers a wider range and leaves less room for question. Just one example.
Below are a couple of examples on a play working as should and a play working as should but text didnt match or made me question it.
Result: Int (worked as should)
Play:
O = singleback empty 4 : slot crosses : medium pass
D = dime normal : LB blitz : sec 1 deep man
Fam = O: 45% D: 51%
QB throws the ball long into double coverage and the safety got there in time to pick it off.
https://mfn1.myfootballnow.com/watch/7824#1414008*************************************************************************************************
Result: TD (text didn't match the play)
Play:
O = Singleback Big : waggle post : long pass
D = 4-3 under : LB blitz 2 : sec 3 deep zone
Fam = O: 31% D: 21%
QB finds WR with one on one situation in zone coverage with the CB having two receivers in his zone. But text says "The ball was not released cleanly". It appeared to be a strike in 2D.
https://mfn1.myfootballnow.com/watch/7824#1414151
Last edited at 3/20/2018 9:09 am