CPU RB Ballcarrier Logic Issues

The issue isn't only effecting run plays either. On kickoff returns, where vision is just as important as run plays, the CPU is constantly getting pulled to the sideline by some unknown force.

Below is the catch point. The way the return team has aligned to this point indicates this is a middle return call.

And we see that the blocking is actually shaping up pretty well, however, the return man is already bouncing this outside despite having no blockers out there to take on the 3 coverage guys. He should be taking this straight up the field along the right hash mark or just inside it a yard or two. If he takes this down the middle, that changes the pursuit angle of the guy in front of 23 as he'd be coming in at a more vertical angle that would allow 23 to get hands on him. And, had he gone inside, the blocker directly in front of the return man would have a very easy angle on the nearest free coverage man standing on the F in FIELD. If those two blocks are made, the return man has a TD.

But he doesn't do that. He continues heading outside. And, like I noted before, when the CPU decides to cut, it's often too late, and it is here.

The cut was so late he doesn't even complete it and is just take down in the middle of it. The return is over, the ball is at the 21.

In short, this return was actually set up extremely well to be taken to the 30 at minimum and potentially to the house. The lane was huge, this wasn't a hard read to where you'd expect a guy to need to have a high return or ballcarrier vision ratings to see it, if ballcarrier vision even comes into effect on return plays. 

What we get is the return man willingly running into 3 guys that aren't being blocked and have little chance of being blocked based on where they are, where his blockers are, and the angle he's taking. For some reason CPU ball carriers are inexplicably wanting to take everything as wide as they can even when it's the clear wrong decision.

This issue is having enough impact as is with it severely hurting the CPU's ability to run. Realizing it also hurts the CPU in the return game in ways like this and completely kills off the chance to have a game changing play like a return TD just makes it all the more impactful.

I truly think this is one of the biggest issues the vs CPU crowd is experiencing at the moment. if the CPU cannot run the ball properly at all, that's a gigantic hit to their offense and removes a lot of the challenge and strategy that many of us are seeking from the game. Like I said previously, the game is great in so many other areas, that's part of what makes this stick out like a sore thumb even more. If this issue could be fixed and the CPU became a legitimate threat in the run and return games and behaved much more like a user/real football player would, that would take the gameplay to a special place.