When I'm killing the CPU why does it call a stupid timeout?

[SportsAce]

Why is it when I'm killing the CPU by about 42 or so, do they have to call a damn timeout. I mean come'on your not going to come back when your down 42-0 with 1:30 left in the game.

[triplej96]

They call timeouts in real NFL blow outs so I guess its just more realism lol

[MSRoble33]

Actually, I was talking to a buddy saying it was a little bit better this year. Last year the CPU was notorious for that, but this year I've had them leave a TO unused when I was kneeling the ball. IMO, I think if they got 3 TO's they are going to use them all on your last kneeling drive, because that'll mean they're guaranteed to touch the ball on offense for a final drive. Not like they're going to come back, but that's just the CPU thinking I guess.

Reminds me of the Dolphins playoff game last year or the year before where they were down by like 17 with 2:00 to go, they fought all the way on a final drive and you KNOW, there's no way, even if they do get the 6, that they'll be able to get the ball for 2 more scores. Coach was on the post-game going, "But we never gave up!!" lol

I think the situation where the CPU decides to nix using it's last TO is when they had just used two of their TO's on their last drive, and you got next to no time remaining and you have the ball.

[BlackNGold]

It does seem silly at times, but no big deal. The CPU doesn have some serious Clock Management issues though as stated here in post in the following thread:

http://forums.operationsports.com/ub..****e#Post656162