man coverage CB

When a Quarterback audibles, the cornerbacks on Defense automatically switch and change receivers that they are covering for no reason which leaves Wide Receivers wide open down the field. Thats a huge bug in the game that needs to be fixed...

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.

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).

Product: Madden NFL 21
Platform:PC
Which console generation do you have?
What is your gamertag/PSN ID? Neo_Novalis
Date/time issue occurred Dec 17th, 2020, 18:00 CET
What type of issue do you have? Gameplay
Which mode has this happened in? Ultimate Team
Which part of the mode? Solo Challenges
Summarize your bug played my 1st Solo Battle from the Wednesday update and won the game. afterwards I was kicked out of MUT and the Solo Battle result is DNF.
How often does the bug occur? Every time (100%)
Steps: How can we find the bug ourselves? please do at least some QA BEFORE releasing a new update! I did the update just before the I played the Solo Battle...
What happens when the bug occurs? DNF
What do you expect to see? 25k+ Solo Battle score...
PS4 Crash Reporting: Please copy the text you put in the crash report here.
What is the AMD or Nvidia Model Number of your graphics card?
Enter RAM memory size in GB

‌

just downloaded the new update and played my 1st Solo Battle from the Wednesday update (Dec 16th) against the Falcons. I won the game, but was kicked out of MUT after selecting 'Finish'. the result, surprisingly DNF!

if that's the way how to solve all the issues Solo Battles have (if I got it right, this update was also to tackle the huge DNF issue), frankly I have to say: please do not try to fix Solo Battles under any circumstances! (sorry for my sarcasm, but after waiting weeks for this mode to be fixed, it's really a bit too much not to be completely pissed off when you run into the exact same &§(/$/(/&" on the very first game again!)

EDIT: I do not know why this post ended up in this thread. I did post it in a Solo Battles related thread...

I added one more video to the playlist (#9). I took it from a offline Franchise game when I tried the adjustment 'press' out of 3-4 odd ('Pinch Buck O') instead of 'show blitz'. the same issue occured: the CB only makes a small move sidewards but does not react until the pass is thrown to the WR he should cover.

now I'm very convinced that this bug occurs when the position of the CB is too far inside relative to the WR he covers. it is not the 'show blitz' adjustment only, but the 3-4 odd formation when facing some offensive formations with simple streak routes for the WR.

some more observations since I've seen this bug quite frequently over the last weeks.

• it does not only happen in 3-4 odd but also in 3-4 bear.
• it happens when doing the 'show blitz' adjustment or doing the 'press' adjustment (either in 3-4 odd or 3-4 bear).
• it happens in streak routes, but also slants.

I'd guess it might happen for every route where the WR starts just running straight at least a few yards and the CB is lined up close to the LOS but slightly too far inside (relative to the WR). I'd also guess that in this case the CB just does not identify the WR as the player he has to cover (since there are similar bugs where the CB and the WR just ignore each other in some run plays instead of picking up the block or reacting to the play at all).

I think I found a workaround for this issue. or it has already been fixed? at least I did not see this issue anymore since I make use of the workaround.

if the WR is lined up very close to the sideline, I do the 'outside' adjustment for the DBs (after 'showing blitz') which moves the CBs slightly closer to the sideline.(and their WR). afterwards I call either 'underneath' or 'over the top' (maybe I now used the wrong names for these options; I'm talking about the two other alternative coverage adjustments to 'inside' or 'outside'). it seems that the 'outside' adjustment avoids that the CBs are lined up too far inside and therefore do not react at the snap.

the negative side of this workaround: I cannot call the 'inside' adjustment afterwards. this would move the CBs too far inside again...