Then there would be no point at setting properties on a parent layer ? IMO : A layer should be renderable if it is renderable itself and its parent is renderable aswell. A layer should not be renderable if it is renderable itself and its parent is not renderable. It seems to me it's the less confusing way, but i don't see…
Hi guys, I need some more input on the nested layers behavior. This time about layer properties. Currently the Outliner's layer hierarchy only affects the hidden, frozen and boxmode properties. They work like this: a layer is hidden if either it is hidden itself, or if its parent is hidden. I think that is logical. With…
Ah yes, my head starts to hurt, but i think i was looking it the other way around : unhidden and unfrozen, because those are the default states, like is renderable on.
Aha I didn't know about that preference setting... Makes this feature a bit less awesome. Still, as you say, with this you can set it per layer, and per property type (display, render, etc). Maybe I should make defaults for new layers too.
Hi PJanssen take a look at Ephere Zookeeper they actually offer every thing you're talking about from double window, to render pass manager, and filters. You'll maybe find some answer inside it. I use this plug in everyday and i can say that it really robust and powerfull.
I've made a new preview video, which shows the new nested layers for the Outliner 3.0: https://vimeo.com/46955894 In the Outliner 3 nested layer setups will be merged along with objects automatically. Basic layer properties are preserved too. That is to say, properties which affect child layers (hidden, frozen, renderable,…
On scriptspot someone suggested/requested about an Outliner-based render pass manager. Do you guys have any thoughts on that? First of all, would it be useful? (Since there are some renderpass managers out there already I believe) And secondly, how would it have to work, what features would it have to have, etcetera.