Quote Originally Posted by JeffHCross View Post
skip kind of spoke to this, but I want to elaborate. This is a very good example of the difference between playing the CPU and playing the user. Up until Tuesday (I haven't tried since), I could call a comeback/curl route, let the receiver run it, and if I threw before the break, the CPU CB would be probably 2 or 3 yards downfield while my WR is catching the ball. Pretty much exactly how a curl is supposed to be thrown.

Against a HUM player, that CB is in front of your receiver before he even starts on his own break, and it's a pick. Every. time.

And just to make things more fun ... against the CPU, since the patch, apparently they can make the "sit in the pocket for 5 seconds, have my player sit in a curl route, have the DB in his hip pocket, and still throw the ball with no reaction from the DB" play. I hate that crap.
While I certianly acknowledge that there are plenty of times where the CB runs the route for you I challenge you to go load up Boise State and run patterns with their WR's or with Notre Dame throwing to Michael Floyd. The Boise State receivers especially have high route running ratings and make cuts in routes unrealistically fast and will always be ahead of the DB. What I have noticed with my recievers (top three are 90 OVR) is that some times they will make their cuts at a normal speed and be ahead of the DB and other times (not as often) they will make super human cuts which completely throw off the timing of the pass, yes they will be WIDE open but because of how fast they make their cut and the difference in timing its usually an imcompletion.

It all comes down to the WR/TE's route running ability and the DB's coverage ability, a high route running ability will typically beat high man coverage ability though but the DB will at least be near and be able to make a play on the ball. The higher the route running ability the more predictable the route will be run.