Octane didn't render all of the frames

[helloimneil]

So I started rendering a 210 frame animation tonight and everything was going as perfect as could be until I came back in to check on the render's progress and noticed it stopped short at frame 125. Does anyone have any idea how I can figure out why Octane didn't render the remaining frames? I'm very confused as everything else, to my knowledge, was setup correctly in the render settings...

Any insight that could be shed on this issue would be greatly appreciated!

[helloimneil]

I should mention that a few of the materials I used for this animation were not Octane materials. In trying to solve this problem I haven't encountered other users reporting this sort of issue with using non-Octane materials.

Some additional information: I have a total of 3 GPUs on my computer, all 1070s. For the render, mostly to see what render times could be, I engaged all 3 GPUs to render. I'm not sure if this is what caused the problem, or perhaps this and the materials? I'm really drawing all sorts of blanks on this and it's bumming me out because otherwise the render was going so well!

It's boggling to me that it would render 125/210 frames and then stop. Nothing zany or wild happens at frame 125, no new materials or anything like that, I dunno... very strange, very strange.

[bepeg4d]

Hi helloimneil,
sorry to hear that you are having issues, but difficult to say without the scene. The non octane materials are surely a good culprit... have you tried to render without them a preview range?
Please, go to Script/Console and post the log after the error.
What about geometry and instances at frame 125?
What about VRAM usage?
What about GPUs temperatures?
ciao beppe

[aoktar]

make a quick previews at lowres and very low maxsamples. If it's not failing on preview so that's not a bug or somethings on plugin side. Another problem which is not clear yet.

[ralf_breninek]

Like Aoktar suggested I would do a low res render but would also delete all C4D materials from this file for that test.
If it runs through it is definately a problem with one of those materials instead of geometry.

If I do recall correctly I had a problem once where I used a C4D material and had some fancy procedural noise in one channel, athough I switched that channel of I ran into VRAM limitations. This happend somewhere last year or the year before and I do not know the exact problem anymore, might also be that Aoktar already implemented a fallback for that particular issue because I never had it again

Also sometimes on C4D it helps to copy paste all your work into a new file. Happened to me once but from time to time you can read others were able to overcome their problems with this method too. (nothing Octane related but more a seldom occuring C4D issue)