aoktar wrote:No need, I've noted. But i think it's not possible to do in c4d's system by plugins. Maybe a different way is required.

Hopefully they provided a way to to say your render failed, even if you can't pop up a nice dialog. Maybe you could add a checkbox for renders to fail when textures are missing?

aoktar wrote:I'd not call somethings like "BUG" which are not implemented. It can be only a feature request to me.

Fine, where do I file my feature request?

aoktar wrote:Is this a reproach or wish for a feature?

I think I'd call it a bug report. Is there a specific place for me to file them?

When rendering C4D scenes with Octane on our farm (i.e. Commandline), sometimes after all the frames have rendered we see this:


renderTM:196.304ms. totalTM:196.477ms.
Rendering Phase: Finalize
Rendering successful: 1054.764 sec.
Error: application crashed
C4DUnhandledExceptionFilter: writing ...

Have you checked the Octane log?

I tried rendering with the log open, but it didn't say anything about the missing textures.

I just think it should behave more like the C4D renderer, which gives you messages in the GUI and on the command line and causes the command line render to fail. Would ...

The render queue window will report if there are textures missing.

Thanks for the tip! The Render Queue does indeed identify the missing textures.

I still think this is an oversight though. Missing textures should result in a rendering error.

If I render Octane in C4D and there are missing textures, the render completes without an error, making it hard to figure out what is causing my render to look off. The C4D renderer shows errors.

I see this in both the C4D GUI as well as the Commandline.