Clock Stopped

Niall Teasdale

I was wondering whether anyone else has seen this:

Basically, the elapsed time counter on my renders gets stuck at some arbitrary time. The render I'm currently running has been going for a couple of hours, but the displayed time is 53 minutes 47 seconds, and that hasn't changed in a while.

This does not stop the render from progressing, though I've yet to determine whether it affects the time limit cut-off. Eventually, the convergence limit is reached and the render stops.

This began happening a couple of days ago and, as far as I'm aware, nothing has changed in that time.

So, has anyone else met this problem? Anyone know what causes it?

Niall Teasdale

Resolved.

Turns out, the battery on my motherboard has died, so the clock wasn't set right. That affected the elapsed time display, but not the actual elapsed time. So, the renders still stop at the time limit, and if I remember to reset the computer's clock every time I turn it on, I don't have a problem. And I need a new battery.

Shows how long I've had this computer...