man coverage CB
Product: Madden NFL 21 Platform:PC Which console generation do you have? What is your gamertag/PSN ID? Neo_Novalis Date/time issue occurred since October I guess What type of issue do you have?...
Forum Discussion
@EA_Blueberry just managed to reconstruct the bug in practice mode. I uploaded a 4th video (see youtube-link in my previous post)
I used the 49ers' defense with the Multiple D playbook and the Raiders' offense.
Defense play: 3-4 odd Pinch Buck O; coverage adjustments: 'show blitz' and 'underneath'
Offense play: Gun Spread Y-Flex, Y-Option; no adjustments
Raiders' #15 Nelson Agholor beats 49ers' #22 Jason Verrett simply by running straight.
I've tried it a few times in practice mode. My guess would be that it happens half the time that the CB makes a minimal move to the side during the snap but then stops while the WR runs the streak route. as soon as the passing animation starts the CB starts to turn around and pursuing the WR without any chance to catch him.
the difference between 1) 'the CB stands still' and 2) 'the CB 'covers the WR' (i.e. bug vs. normal) seems to me to be that in one case the WR's run is slightly slowed down by body contact (the CB makes its first move to the side sufficiently large), while in the other case the WR's run is not affected.
added one more (#5): 91 OVR Bo Jackson beats #21 94 OVR Nnamdi Asomugha
this time it is a bit different because the CB is still in motion when the ball is snapped, but it looks very similar (i.e. the QB almost immediately threw the ball)
after having recorded some more cases (see youtube playlist), I'm quite sure that this bug always happens when the CB is not close enough to the WR such that the WR can run just straight to pass the CB.
- EA_Blueberry
Community Manager
Thank you for the videos! Does it always happen when the safeties are brought down in the same spots? It feels like it could be a logic issue but if the CB is on man coverage it's odd he would still get blown by like that. If it's due to the safeties being moved to a certain spot it could be the root cause.
If the CB was able to hold up coverage, do you expect a quick blitz from the players on the line? Wondering if this could be an intended counter to a nano blitz to encourage players to leave a safety over the top.@EA_Blueberrythank you for your response!
I have repeated the play (as shown in clip #4) several times in practice mode. first I did it without moving the safeties pre-snap and afterwards with moving the safeties. the pattern occured in both situations. it did not always occur.if the CB reacted on the snap, then his move sidewards was large enough to at least slightly touch the WR and trigger this animation of decerating the WR (by 'holding' incl. turning the CB around).
if the CB did not turn around, he made a small move sidewards but this move did not affect the direction of the WR's run.
I would guess that this pattern depends on the exact spot the CBs are placed after doing the adjustment 'show blitz'. if the CB is too far from the WR by a minimal distance, the bug happens, otherwise it does not. I assume the relative distance between WR and CB is not always exactly the same. to this consideration would also fit that the bug just occurred more often in my attempts, if the ball was on the left hash at the snap (the WR and CB were also on this side of the field).
It seems to me that the frequency of the bug depends on the position of the ball at the snap. the position of the ball may also affect the relative position of the CB (if perhaps not visible to the naked eye).
