OTOY Forums

Heyall, hoping someone can help me here.
I've animated a title/logo sequence and only want to render a portion of it (frames 55 - 110). Here is a screen shot of my settings within C4D
http://i.imgur.com/RvSYsyR.png

When I commit the render, Octane only is able to one frame and then stops. Screenshot of Octane quitting the render (not sure if this helps) :
http://i.imgur.com/ArVgq0Y.jpg


When I switch C4D back to the standard Render, it renders multiple frames without a problem. I'm very new to Octane so I might be missing something obvious. Anyone know what I might be doing wrong? Thanks!

It's not a bug quite likely. But I can't see any good info to say somethings. What's your version? Have you checked Octane log for any errors?
Also you don't need to add AO vpost. This is not a standard renderer.

This can happen if you have C4D-standard materials that use image textures in one or more channels. Replace those materials with Octane materials and the appropriate image textures in the appropriate channels.

rwalker wrote:This can happen if you have C4D-standard materials that use image textures in one or more channels. Replace those materials with Octane materials and the appropriate image textures in the appropriate channels.

I'm not sure what you mean but i suppose this kind of error should not happen with standard materials. Because plugin makes a conversion of this materials to Octane materials on the fly.

aoktar wrote:

rwalker wrote:This can happen if you have C4D-standard materials that use image textures in one or more channels. Replace those materials with Octane materials and the appropriate image textures in the appropriate channels.

I'm not sure what you mean but i suppose this kind of error should not happen with standard materials. Because plugin makes a conversion of this materials to Octane materials on the fly.

For example, I once used an object from the C4D library, and that object had a texture that used an image in the Color channel. Octane would preview it fine, and render a single frame fine - but if I tried to render out an animation (a series of exr files), the render would stop after one frame. The specific material in my case was wood. I just replaced the C4D wood material with one from the Octane liveDB and everything was fine.

rwalker wrote:

aoktar wrote:

rwalker wrote:This can happen if you have C4D-standard materials that use image textures in one or more channels. Replace those materials with Octane materials and the appropriate image textures in the appropriate channels.

I'm not sure what you mean but i suppose this kind of error should not happen with standard materials. Because plugin makes a conversion of this materials to Octane materials on the fly.

For example, I once used an object from the C4D library, and that object had a texture that used an image in the Color channel. Octane would preview it fine, and render a single frame fine - but if I tried to render out an animation (a series of exr files), the render would stop after one frame. The specific material in my case was wood. I just replaced the C4D wood material with one from the Octane liveDB and everything was fine.

I don't think this will occur on latest versions. If it happens please let me digg a scene. But as a remainder, if you have some C4D shaders in materials and using multi-processing for conversion then this can cause to some crashes. This may be a reason to break the render.

aoktar wrote:I don't think this will occur on latest versions. If it happens please let me digg a scene. But as a remainder, if you have some C4D shaders in materials and using multi-processing for conversion then this can cause to some crashes. This may be a reason to break the render.

Im having those issues aswell, seemingly even without multi-processing for c4d-shaders.

philmaron wrote:

aoktar wrote:I don't think this will occur on latest versions. If it happens please let me digg a scene. But as a remainder, if you have some C4D shaders in materials and using multi-processing for conversion then this can cause to some crashes. This may be a reason to break the render.

Im having those issues aswell, seemingly even without multi-processing for c4d-shaders.

AGAIN: Please give me some scenes, better info, etc... Otherwise you should solve it your self, i cannot help.

i can reproduce this behavior with 2.24.2 Test5.2

create c4d standard material
create layershader
load a image in the layershader

fuchsundvogel wrote:i can reproduce this behavior with 2.24.2 Test5.2

create c4d standard material
create layershader
load a image in the layershader

I can't be sure that's same issue.

But here is not any native Octane material or textures. C4D's shaders are working with some pre-render calculation/baking to a temporary image. There is some problems on this convertion with some type shaders like "Layer". I can't give guarantee for these. Try to use Octane shaders else of this.