Motion & M2M coverage

[Yngvai]

Something I've noticed about M2M coverage when a guy goes into motion. A receiver goes into motion, going laterally, and the DB follows him. When the computer is snapping the ball, the computer often snaps the ball soon after the motion begins. After the snap, if the receiver continues to move laterally, the DB will studder, move towards him, studder again, then continue following him. The receiver gets pretty open when this happens because the DB falls way behind him. The DB does this regardless of whether he's in under, over, or deep coverage.

Is there any way to prevent this from happening?

[Marauders]

Another good observation, Yngvai.
 
I had brought something similar up in the private forum.
 
David was taking a look at it to make a small change in coverage that may clean this up a bit.
 
I can't go into it more than that, as we are still testing.
 

[Yngvai]

I'm not sure if this was intended to be fixed or changed, but I did see that this still happens in version 2.2.