View layer overrides on EVERYTHING
The current state of the view layers is quite limited, especially for us that comes from other softwares that have really strong render layers. Feels like the only real thing you can do with Blenders view layers is to show and hide collections, with some very few and generally very specific overrides that you seldom need.
What would be VERY useful though is per view layer settings, I mean as in you can maybe right click on whatever settings anywhere and select "Toggle view layer override" (or simply maybe ctrl-click?) and the text of the setting go bold, maybe a different color or an outline around the setting
indicating that this particular setting have it's own value on this particular view layer that you can change to whatever your hearts desire.
For example having a view layer having more samples, less light bounces, using Eevee instead of Cycles or the background can be transparent instead of visible as on the other layers.
Should also apply to objects where you can have the Ray Visibility for shadows be on in all view layers but one, or having some modifiers be on or off. Also being able to have material overrides per objects would be SO useful.
I guess I could go on with more examples, but I think you get the drill :)
3 Comments
If i am not mistaking, this is a design choice, you are expected to use Scenes for deeper customization.
Though personally I'd rather have such possibilities through layers directly instead of managing basically a duplicate of my project.
Yeah guess you can do that ish, tbh I haven explored scenes that much, but having everything split instead of just splitting those few settings feels more cumbersome. Actually I just wish they'd copy and improve on Mayas render layers, the only thing I really miss from that old thing.
Library overrides were designed for this. I think if we would be able to use them in the same file instead of across files it would perfectly fulfill OP's (and my) wish.
Imagine linking collections to a second scene and being able to override some properties there. That would be powerful. And I don't believe it would be farfetched to implement using existing library override system.