NCAA Football 14 Demo Arrives June 18, Full Game, 3 Min. Qtrs, Coordinator Cam

[OregonianTexan]

As an Oregon fan I'm in love with this new playbook. so many types of motion zone reads, fake bubble screen post routes, etc.
This is awesome.

[Matt10]

can someone switch sides and place the Def Adjustments on the CPU side to Aggressive on Pass Coverage? This is the formula for the DB Glitch from 13.

Please report back - thanks!!

[GetReal]

Quote: Originally Posted by Jeremy.Horne.SC

Do you seriously have to be a Gold member to even get to play the demo?

My Gold ran out last month. Don't see the point in renewing unless you play a lot of online. Guess I'll just watch the vids and wait till next week. Really starting to hate Microsoft...

[x kcdeE x]

This game is going to be so much fun running the old school wishbone offense with OU.

[Adder15]

I was able to use a bull rush to drive the lineman right into the qb

It was jaw dropping

[IlluminatusUIUC]

It felt great, probably a day 1 buy for me now. But I still noticed some bugs

1) When running the hurry up with UO, one of TAMU's defensive ends lined up in a 3 point stance all the way at the sideline. I was facing a 3-3 front lol
2) The AI still has a tendency to ignore a guy right in front of them to block someone downfield
3) On a slant, my wideout went into the "1 handed grab" animation as if the ball was thrown behind, except I was leading him and the ball caught him in the facemask.

[Gap Integrity]

Started downloading at 2:50 EST.... only at 58%.... I'm living vicariously through you all.

[Art01]

Quote: Originally Posted by Matt10

can someone switch sides and place the Def Adjustments on the CPU side to Aggressive on Pass Coverage? This is the formula for the DB Glitch from 13. Please report back - thanks!!

Matt, I believe that the DB Glitch in NCAA13 had to do with the CPU keeping the Defensive Adjustment at Aggressive on Pass Coverage. If the setting is on Aggressive, the DBs should come up more often, with the result that they are more likely to get burned on deep routes. The real test would be to see whether or not the software leaves the CPU coverage in Normal, except when Aggressive would be appropriate. And, whether or not the coverage is shifted to Conservative at appropriate times.