Sub 40 man cover player completely baffled on his assignment. Decided to go out of bounds.
Same problem as above.
Really , the route didn't even start and the db headed in to flat, and once the WR made a cut the db went the opposite way and continues out of bounds. I thought you said the bug happens after the route ends? If what you are saying is true I am completely baffled as well.
Re: Beta update release
by
setherick
@
4/14/2018 4:00 pm
WR stutters right as he comes off of the line. That's the slight hesitation between the snap and the WR moving.
WR stutters right as he comes off of the line. That's the slight hesitation between the snap and the WR moving.
I think am starting to get the logic. I thought that the release off the LOS might be reserved only for B&R. So the logic man vs. Route logic actually ran twice during 5 yard slant /post? Once at the snap and again at the cut? Or just in the beginning ?
Re: Beta update release
by
setherick
@
4/14/2018 5:06 pm
raymattison21 wrote:
setherick wrote:
WR stutters right as he comes off of the line. That's the slight hesitation between the snap and the WR moving.
I think am starting to get the logic. I thought that the release off the LOS might be reserved only for B&R. So the logic man vs. Route logic actually ran twice during 5 yard slant /post? Once at the snap and again at the cut? Or just in the beginning ?
M2M vs Route will start on the snap if the DB is in M2M and he doesn't attempt to jam. So what happened on the play is that he started to engage in M2M, but then the WR stuttered and effectively ended the route. The DB doesn't know who to cover once his man's route ends and, for whatever reason, he doesn't recognize his man and runs to cover someone else.
Re: Beta update release
by
raymattison21
@
4/14/2018 5:56 pm
setherick wrote:
raymattison21 wrote:
setherick wrote:
WR stutters right as he comes off of the line. That's the slight hesitation between the snap and the WR moving.
I think am starting to get the logic. I thought that the release off the LOS might be reserved only for B&R. So the logic man vs. Route logic actually ran twice during 5 yard slant /post? Once at the snap and again at the cut? Or just in the beginning ?
M2M vs Route will start on the snap if the DB is in M2M and he doesn't attempt to jam. So what happened on the play is that he started to engage in M2M, but then the WR stuttered and effectively ended the route. The DB doesn't know who to cover once his man's route ends and, for whatever reason, he doesn't recognize his man and runs to cover someone else.
I guess you can press and not play B&R? I kinda looks like a B&R senerio . ...you could tell the difference? Still it sounds like the problem is in the stutter....could we take that out or rewrite it? For exmple....Instead of a stutter have the db give more deep cushion the worse he is at man.
Re: Beta update release
by
setherick
@
4/14/2018 9:23 pm
Yes, you can tell the difference between close M2M coverage and B&R coverage by how the DB lines up. Look at the play previous to the one you posted: https://mfn1.myfootballnow.com/watch/7989#1449207
In 207, CB at the bottom of the screen is in B&R. You can tell this pre-snap because he's lined up with no space between him and the WR. In play 208, there is at least a yard between the DB and the WR. The DB is not going to B&R in that situation.