OTOY Forums

Layer hierarchy overriding not working

Hi Aoktar!
I have noticed problem when using Layers in C4D.
If I assign multiple layers hierarchy of multiple objects (like in screenshot above)
and I turn off render visibilty to layers that are in above of other layers in hierarchy, the most top layer overrides
all the layer settings that are above it in the hierarchy.

This only happens with Octane.
With Cinam4D built in renders , it works as expected.

I could use those those two little dots in Object manager, but its not effective when we have to deal with big hierarchys of objects and
its un-effective to browse throught everything and manage things.

Here is example (used scene attached)

1) layer_1
OCTANE RENDER
viewport visibilty: ON
render visibilty: ON




2) layer_1
OCTANE RENDER
viewport visibilty: OFF
render visibilty: OFF

In this scenario, the most top layer is overriding every layer that is below, but it shouldnt work like this.




3 ) layer_1
STANDART RENDER
viewport visibilty: OFF
render visibilty: OFF

In this scenario, where Standart render is used, everything works as expected, layer_2 and layer_3 is overriding layer_1 and they are rendered the way I had chosen in Layers manager.





My info:
A. Windows 10
B. GTX 1080Ti (happens on multiple machines)
C. RAM Capacity 32GB
D. Nvidia driver version = 398.11
E. OctaneRender Standalone version = 3.08.3 (3080300)
F. OctaneRender plugin version = 3.08.3
G. Host application version = Cinema4D R17.055 and Cinema4D R19 (latest build)

Could you please attach images in your post? I couldn't see otherwise.

I updated image in this topis and also in my other topic I created today viewtopic.php?f=86&t=68693&p=345222#p345222

Hi Aoktar!
Do you see images now?

tomsvfx wrote:Hi Aoktar!
Do you see images now?

yes

So the problem is clear to you?
I understand that you have alot of works for R20 release and future builds, but I just want to make sure that this problem is adressed for future and I have described good enough the problem.

Thanks in advance!

tomsvfx wrote:So the problem is clear to you?
I understand that you have alot of works for R20 release and future builds, but I just want to make sure that this problem is adressed for future and I have described good enough the problem.

Thanks in advance!

Yes! I've fixed it!

Thanks! Happy to hear that

Do you have some estimates when build with the fixes might get released?

tomsvfx wrote:Thanks! Happy to hear that

Do you have some estimates when build with the fixes might get released?

I can give you a build, don't have any estimation for next public build date.

If you can send it to me in PM that would be great.