I guess I should thank the CPU coach of the Western Michigan Broncos for gift-wrapping a victory for me last night in the opening game of my Michigan dynasty.
However, I'm more disappointed in the continued poor CPU clock management late in games.
Western Michigan is beating me 21-16 in the final minutes, but twice throws long incompletions on third down to stop the clock and give me time to win the game.
On third-and-13, a deep ball is broken up with 2:01 left. Western punts.
I fumble an option pitchout with 1:29 left at my own 30. I have only two timeouts left. I use them on first and second down. On third-and-19, Western again goes deep and it's incomplete with 1:14 left in the game.
Western punts into the end zone and I get the ball with 1:09 left. I have no timeouts remaining.
On my second play, with 44 seconds left, I hit Junior Hemingway for the game-winning touchdown. I'm figuring that almost all of those seconds would've been off the clock had the CPU just run the ball and milked the clock with the lead late in the game in my territory.
I remember winning several games in NCAA '11 because the CPU gift-wrapped more time on the clock for me. It appears this CPU clock-management flaw has not been fixed.
Another example was the CPU calling a quick timeout with 1:40-ish left in the first half to save time when it really wasn't necessary yet. That's a smaller issue, but still not the way a real team would manage the clock.
I should be 0-1 with an upset loss to Western. Instead, I'm 1-0 and the athletic director is giving me a free pass for that near-debacle.
However, I'm more disappointed in the continued poor CPU clock management late in games.
Western Michigan is beating me 21-16 in the final minutes, but twice throws long incompletions on third down to stop the clock and give me time to win the game.
On third-and-13, a deep ball is broken up with 2:01 left. Western punts.
I fumble an option pitchout with 1:29 left at my own 30. I have only two timeouts left. I use them on first and second down. On third-and-19, Western again goes deep and it's incomplete with 1:14 left in the game.
Western punts into the end zone and I get the ball with 1:09 left. I have no timeouts remaining.
On my second play, with 44 seconds left, I hit Junior Hemingway for the game-winning touchdown. I'm figuring that almost all of those seconds would've been off the clock had the CPU just run the ball and milked the clock with the lead late in the game in my territory.
I remember winning several games in NCAA '11 because the CPU gift-wrapped more time on the clock for me. It appears this CPU clock-management flaw has not been fixed.
Another example was the CPU calling a quick timeout with 1:40-ish left in the first half to save time when it really wasn't necessary yet. That's a smaller issue, but still not the way a real team would manage the clock.
I should be 0-1 with an upset loss to Western. Instead, I'm 1-0 and the athletic director is giving me a free pass for that near-debacle.
Comment