Cinema4D version 2020.1.4 (Obsolete stable) 23.07.2020

[thanulee]

You have to be sure to select your extra passes within the Octane tab - not the c4d native render pass tab. AND you must output with the file type: Octane EXR.

Thanks im using cryptomatte with other modes like material and instance. Object node is just not working as i described.

[thodosplay998]

Mate, is that ok?

Basic thing, Material ID. It changes from one color to another in one sequence.

And it's not a Standalone SDK problem, because it works fine in Standalone.



I had also experience when using Layer ID and some of objects just dissapearing in the sequence on the last frames!\
Also Render Queue just crashes Cinema 4D.
Your OpenGL alpha on materials makes objects fully invisible in viewport even when no opacity is used inside of it(and it was working fine in 3.08-3.09)!!!!

Do something with it, it's a basic things that needs to be working! Why do i pay for my suffer?

I experiencing same problems from 3.06 C4D Octane Render.

[aoktar]

Mate, is that ok?

Basic thing, Material ID. It changes from one color to another in one sequence.

And it's not a Standalone SDK problem, because it works fine in Standalone.

I had also experience when using Layer ID and some of objects just dissapearing in the sequence on the last frames!\
Also Render Queue just crashes Cinema 4D.
Your OpenGL alpha on materials makes objects fully invisible in viewport even when no opacity is used inside of it(and it was working fine in 3.08-3.09)!!!!

Do something with it, it's a basic things that needs to be working! Why do i pay for my suffer?

I experiencing same problems from 3.06 C4D Octane Render.

1-Read manual to see how to use it! SEE PICTURE
2-It's not a simple issue as you can think! C4D's custom material support is not very well and limited. Just don't use opacity for opengl previews if that's not working well. We did our best! You don't have to talk like this!

@thanulee, please check this section

[thodosplay998]

Mate, is that ok?

Basic thing, Material ID. It changes from one color to another in one sequence.

And it's not a Standalone SDK problem, because it works fine in Standalone.

I had also experience when using Layer ID and some of objects just dissapearing in the sequence on the last frames!\
Also Render Queue just crashes Cinema 4D.
Your OpenGL alpha on materials makes objects fully invisible in viewport even when no opacity is used inside of it(and it was working fine in 3.08-3.09)!!!!

Do something with it, it's a basic things that needs to be working! Why do i pay for my suffer?

I experiencing same problems from 3.06 C4D Octane Render.

1-Read manual to see how to use it! SEE PICTURE
2-It's not a simple issue as you can think! C4D's custom material support is not very well and limited. Just don't use opacity for opengl previews if that's not working well. We did our best! You don't have to talk like this!

@thanulee, please check this section

Alright, i get about openGL alpha(why do even add it?). I get that it's complicated.
BUT! Why is Material ID works fine when rendering an image from Standalone, but not from c4d? And render Layer issues?

If you are reffering to manual, please, send some links, didn't see any of Material ID.

[aoktar]

BUT! Why is Material ID works fine when rendering an image from Standalone, but not from c4d? And render Layer issues?

If you are reffering to manual, please, send some links, didn't see any of Material ID.

material id will change because of ID changes, use material names instead. See picture to find the link from c4d manual.

[thodosplay998]

BUT! Why is Material ID works fine when rendering an image from Standalone, but not from c4d? And render Layer issues?

If you are reffering to manual, please, send some links, didn't see any of Material ID.

material id will change because of ID changes, use material names instead. See picture to find the link from c4d manual.

To be fair this situation is giving me a frustration. Materials are the same, same scene, same render sequence. 74 frames are with one color, 75 and further are another. Standalone is rendering without changes, how is it possible? What do i get wrong?

[aoktar]

To be fair this situation is giving me a frustration. Materials are the same, same scene, same render sequence. 74 frames are with one color, 75 and further are another. Standalone is rendering without changes, how is it possible? What do i get wrong?

It's not fault of plugin(me). Probably SA has an internal ID to keep same, plugins doesn't. Keep to use "material name" instead of it, and lost your frustation.

[thanulee]

Thanks Ahmet.
I have read it yea, and ObjectNode doesnt work correct in AE. Neither ObjectNodeName nor ObjectPinName
It selects all objects as one matte. While it should show each object as a unique color.
Have u experienced this behaviour?

ty

[thanulee]

74 frames are with one color, 75 and further are another. Standalone is rendering without changes, how is it possible? What do i get wrong?

Hey bud, if it helps, i had some issues these days myself. I realised when polygons overlapped in an object, the passes were changing. I was using divider plugin in my case and i was pushing it beyond its limits. When i figured it out everything worked again. Maybe there is an object in ur scene that deforms in a "bad" way?

[thodosplay998]

74 frames are with one color, 75 and further are another. Standalone is rendering without changes, how is it possible? What do i get wrong?

Hey bud, if it helps, i had some issues these days myself. I realised when polygons overlapped in an object, the passes where changing. I was using divider plugin in my case and i was pushing it beyond its limits. When i figured it out everything worked again. Maybe there is an object in ur scene that deforms in a "bad" way?

Hi! Well, mesh is static and Standalone is working fine with no changes. So i don't think that overlapping is causing any problem.