Page 1 of 1

Force maxwell stop

Posted: Mon Jan 18, 2010 10:14 pm
by Tok_Tok
Is there a way to force maxwell to stop rendering?

I have this render that I did over a couple of days but now it doesn't come of it when I hit the stop button..
Also the temp file is corrupted..

Re: Force maxwell stop

Posted: Tue Jan 19, 2010 12:26 am
by QuakeMarine1
sounds like the render have hung
if the temp mxi is broken then render have stucked during last autosave
try to print screen the image you see to save at least "something"

Re: Force maxwell stop

Posted: Tue Jan 19, 2010 12:53 pm
by Tok_Tok
that would be the last option, but I have no choice ;)

thanx anyway

Re: Force maxwell stop

Posted: Wed Jan 20, 2010 12:00 pm
by choo-chee
instead of print-screen just look for the image maxwell last saved - not only the mxi but the ldr image

Re: Force maxwell stop

Posted: Wed Jan 20, 2010 1:13 pm
by Tok_Tok
Good one, but I already rendered another image so that file is overwriten... too bad :?

I seem to have found te problem why maxwell stopped rendering after a certain time.
Windows 7 has it's power settings set to "turn the harddisk after 4 hours" or so. You will have to go to the advanced options
to change it. The weird thing is, is that the rest of the power settings is set NOT to Sleep..

So if anybody else has the same problem, this COULD be the solution. :)

Re: Force maxwell stop

Posted: Wed Jan 20, 2010 1:23 pm
by choo-chee
I had similar problems , I configed the pc to never standby, hibernate or anything other than turn monitor off....

Re: Force maxwell stop

Posted: Wed Jan 20, 2010 4:22 pm
by Bubbaloo
Also be careful about Windows updates that restart your computer.

Re: Force maxwell stop

Posted: Wed Jan 20, 2010 4:33 pm
by choo-chee
who needs them, I canceled auto-updates ...

Re: Force maxwell stop

Posted: Thu Jan 28, 2010 7:31 pm
by manuelmatamoros
Hi: I have same problem when I install new maxwell 2.0.1 or/and maxwell plugin 2.0.24; i solved this, unistall this maxwell version and re install old version 2.0.0 and same for 3d max. 2.0.24 list of bugs talk about this, but isn't resolve... bye