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.