chris.scherer
02-12-2006, 10:01 AM
Hello world,
everyone loves batchrendering. More memory, less troubles, can run overnight. Except maybe the large amounts of junk text thrown out by Mray that tell you anything but the current frame rendered...the electric image render-stats were way much cooler. Anyway, I ran into a problem somebody probably had before:
Some of my *.mb files produce "mayabatch" fatal errors, the ones with the neat messagebox that say "Fatal error: blah blah saving as blah.ma". That alone is of course unpleasant. But the real treat is that itīs a messagebox, hence the render process stops until somebody presses "OK". Wich, in turn, would cancel out the "overnight" feature of batch rendering and cost some ounces of sleep and productive working time in the morning.
Is there any way to bulletproof the rendering options so they don't display these error messages ?
And is there a way to customize the status report of mray (e.g. to just display the current image file processed) ?
Thanx world, chris.scherer
everyone loves batchrendering. More memory, less troubles, can run overnight. Except maybe the large amounts of junk text thrown out by Mray that tell you anything but the current frame rendered...the electric image render-stats were way much cooler. Anyway, I ran into a problem somebody probably had before:
Some of my *.mb files produce "mayabatch" fatal errors, the ones with the neat messagebox that say "Fatal error: blah blah saving as blah.ma". That alone is of course unpleasant. But the real treat is that itīs a messagebox, hence the render process stops until somebody presses "OK". Wich, in turn, would cancel out the "overnight" feature of batch rendering and cost some ounces of sleep and productive working time in the morning.
Is there any way to bulletproof the rendering options so they don't display these error messages ?
And is there a way to customize the status report of mray (e.g. to just display the current image file processed) ?
Thanx world, chris.scherer