Hello,
I'd like to have a single place where I say "okay this collection and all it's children will use Light ID 5, 10 and 12" and whatever I put into this collection receives these properties - same as as in C4D for example where all children inherit these properties.
But at this point it seems I have to set these properties individually on every single child in Blender? And whatever new child I add into the collection won't inherit anything and I have to manualy set the Light IDs again?
Light IDs on collections?
-
linograndiotoy
- Posts: 1342
- Joined: Thu Feb 01, 2018 7:10 pm
You can change any attribute for multiple selected objects by simply pressing "Alt" when editing it.
-
Hurricane046
- Posts: 98
- Joined: Wed Jul 25, 2018 6:57 am
Yeah. But problem with this solution is that it requires constant maintenance.linograndiotoy wrote: Thu Apr 10, 2025 2:26 pm You can change any attribute for multiple selected objects by simply pressing "Alt" when editing it.
Whenever we bring any new object to existing collection we HAVE to adjust their LID properties accordingly. This will result in random mistakes where people for example add fence to the environment collection and forgot to set the fence to proper LIDs (or any other Octane-related properties for that matter).
I've been using the C4D solution where all children automatically inherit proper LIDs for years and it's the most convenient, fool-proof solution there is. You never have to double check whether an object in question has proper Octane settings, it inherits them and that's that.
-
linograndiotoy
- Posts: 1342
- Joined: Thu Feb 01, 2018 7:10 pm
Cinema 4D and Blender have fundamentally different systems and APIs. For example, a Collection in Blender currently doesn’t even support an “ID” attribute. In Cinema 4D, parenting and inheritance are core aspects of the system itself—unrelated to Octane.
The user “errors” you mentioned can easily be avoided by simply right-clicking the Collection, choosing “Select Objects” and then performing the ID change while holding Alt.
Adding Octane attributes directly to a Collection—and making them automatically inherited by all contained items—is theoretically possible, but quite complex. We’d need a way to determine which specific attributes should be inherited and which shouldn’t. That’s far from trivial and has significant implications for both workflow and UI design.
It’s something we might explore in the future, but there are still many other areas that need to be addressed first.
The user “errors” you mentioned can easily be avoided by simply right-clicking the Collection, choosing “Select Objects” and then performing the ID change while holding Alt.
Adding Octane attributes directly to a Collection—and making them automatically inherited by all contained items—is theoretically possible, but quite complex. We’d need a way to determine which specific attributes should be inherited and which shouldn’t. That’s far from trivial and has significant implications for both workflow and UI design.
It’s something we might explore in the future, but there are still many other areas that need to be addressed first.