Page 3 of 3

Re: Batch render from command line crash

Posted: Thu Apr 11, 2013 8:13 am
by sampakinpa
I found a temporary work around to the crash problem by dividing the render to three sequences: 1-20, 21-40, 41-60 in the batch file. In that way its probably refreshes the memory on each sequence.
But this is not a permanent solution and it must be fixed for us to implement octane to our in-house pipeline.

I added one of the animation mb files that I used for testing:
Ring_223315_ang01.zip
(6.92 MiB) Downloaded 204 times
It we'll be very helpful and appreciated that you and the engine team could use it to help us solve this problem.

Thanks
Ethan

Batch render from command line crash

Posted: Thu Apr 11, 2013 9:39 am
by JimStar
sampakinpa wrote:I found a temporary work around to the crash problem by dividing the render to three sequences: 1-20, 21-40, 41-60 in the batch file. In that way its probably refreshes the memory on each sequence.
But this is not a permanent solution and it must be fixed for us to implement octane to our in-house pipeline.

I added one of the animation mb files that I used for testing:
Ring_223315_ang01.zip
It we'll be very helpful and appreciated that you and the engine team could use it to help us solve this problem.

Thanks
Ethan
Thank you!
Will try to reproduce it with your scene.

Batch render from command line crash

Posted: Sat Apr 13, 2013 1:15 pm
by sampakinpa
A note about the work around:
As I increase the samples (pt) I need to render in smaller chunks because it crashes more frequently.