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:
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
Moderator: JimStar
- sampakinpa
- Posts: 110
- Joined: Mon Dec 03, 2012 11:46 am
- Contact:
2x Xeon E5-2620, 32 GB RAM, 4X GTX1080ti, Windows 10, Octane 3 for Maya 2018, Radeon HD6450 for disply BRIO Animation ltd
Thank you!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: 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
Will try to reproduce it with your scene.
- sampakinpa
- Posts: 110
- Joined: Mon Dec 03, 2012 11:46 am
- Contact:
A note about the work around:
As I increase the samples (pt) I need to render in smaller chunks because it crashes more frequently.
As I increase the samples (pt) I need to render in smaller chunks because it crashes more frequently.
2x Xeon E5-2620, 32 GB RAM, 4X GTX1080ti, Windows 10, Octane 3 for Maya 2018, Radeon HD6450 for disply BRIO Animation ltd