Render instance combined with Octane tag (visibility) Tweet

[twistereli]

When you make multiple render instances of an object in C4D and try to control their visibility with Octane tags on each, only 1 random tag appears to controls all instances. The other tags don't respond. The desired behavior would be that each tag only controls its own object.

This only happens on render instances, not the default instances.

A current workaround I found is parenting the source object in as much nulls as you have render instances - then assigning the different nulls to the different render instances, so they all source a different object (that holds the geometry at the bottom level)
See attached file for both the bug and workaround

C4D render instance Octane tag Bug.zip

(81.94 KiB) Downloaded 279 times

OS: Windows 10
GPU: RTX 3090 FE
RAM: 32GB
Nvidia driver: 516.94
Octane plugin version: 2022.1-R8
Host application: Cinema 4D 2023.1.0

[aoktar]

It will affect the many older scenes if I change the behavior. And What I see that's not much easy to do. Even we can say that's not possible without making big revisions.

[frankmci]

Since they are specifically render instances and the same set of render data, the render visibility control for the instances always rests with the last instance created. They are all one. All the instances can be hidden at once. Render instances can be hidden while the source object remains visible, but they can not remain visible if the source object is hidden. If you think of it in terms of a simple two level hierarchy, it makes sense. There is really only one "parent" and one "child." Any additional children are just images in a looking glass, no vampires allowed.