Page 1 of 1
quit after about 2 hours...
Posted: Thu Sep 15, 2005 8:31 am
by Hervé
Strange, but since a couple of days, Maxwell quits after rendering about for 2- 3 hour (approx) , desired time is always set to 100000... so I don't get why... anyone had the same problem...?
it gives no warning, when I came back, screen is like I forgot to push render frame...
Posted: Thu Sep 15, 2005 8:38 am
by macray
Perhaps you really didn't push it!?
Did you check the output folder if there was something new or if it was the previous version? Sorry to assume you really didn't push the button, but can it be?
Posted: Thu Sep 15, 2005 8:41 am
by Hervé
oh yeah, no problem, the render was there, but I wished to render it longer....
Posted: Thu Sep 15, 2005 9:13 am
by hdesbois
Actually, I had this kind of problem after I installed an antivus (bit defender) on my machine. Now, I just shut down the antivirus while rendering, and, so far, so good.
HD
Posted: Thu Sep 15, 2005 9:23 am
by Hervé
Thanks Henri, I will try that tonight...
Posted: Fri Sep 16, 2005 5:35 am
by morbid angel
harve, i got same thing....are you writing mxi:w ?
Posted: Fri Sep 16, 2005 7:03 am
by Hervé
No, Morbid angel, no MXi writing... but my guess is that I was playing too long with that scene, replacing objects all the afternoon for tests...
I tried to render yesterday, it worked, so I dunno... difficult to reproduce and test... since it happened after 2 or 3 hours...
Posted: Fri Sep 16, 2005 7:54 am
by sidenimjay
were you rendering to the display or to disk?
are there any other processes that may kick in overnight?
NOTE : this includes screen savers.
its quite possible that any program that "auto" updates itself would fight for proc time
it is quite difficult to do anything but render on a single proc machine.
perhaps maxwell miswrites while fighting for position and is expecting to be done at a certain percentage of render time thus continues, then the data it needs is corrupt . . . .. cue crash . . . . .