The CPU's clock management on DEFENSE needs work

[Deegeezy]

Is it just me or does the CPU on defense have no sense of time in late game situations? I have played several games over the past few NCAA series installments and this particular situation has yet to be addressed:

Under two minutes to go, game either tied or CPU up by less than a touchdown, opponent driving in the red zone.

Why is it that the CPU, while on defense, will never call a timeout when faced with the above situation? They always allow you to run the clock out and kick a FG at the end of the game or run clock to score a TD with as little time as possible.

In this situation, the CPU should be programmed to pretty much ALWAYS call a timeout on plays that end with the clock running.

I've played two games in a row now where the CPU should have called their timeouts to get the ball back but instead, watched me run the clock down from over a minute left to down to 0:02 to kick a game-winning field goal.

[speedy43]

They probably used them all up with the automatic time outs at 2:01 and 1:01.

[Haze88]

Considering they are still programmed to give us a two-minute warning after all these tears you can't expect them to use human-like awareness and logic to call timeouts or anything for that matter.

[stratospaly]

On the flipside you can get "free" timeouts when on defense. Just pick a play and run into the O line. You get a 5 yard penalty, but there have been many times where this would have been the difference between a W and a L.

I thought a few years back they put in a rule that defensive penalties would not stop the clock, guess that never made it into the game either.

[Deegeezy]

Quote: Originally Posted by Haze88

Considering they are still programmed to give us a two-minute warning after all these tears you can't expect them to use human-like awareness and logic to call timeouts or anything for that matter.

It's possible to do - they just don't know how, don't care to fix the problem, or don't realize there is a problem.