← All ideas
  • Published 4 Apr 2019

ViewLayers: Per-Layer Renderer Selection.

EEVEE and Cycles have very similar looking materials, so in some cases you can get away with just using EEVEE, even in the final render. So I would like to be able to set some ViewLayers to Cycles, and others to EEVEE for use in compositing. Of course, I'd like to support third-party renderers as well, such as the awesome LuxCore.

How could we do this? Perhaps the "use for rendering" checkbox could be available for each enabled renderer, or at least remembered for each renderer. Then, the user could simply render out an animation in each render engine, and composite the results together. Currently, it's a little tricky to pull this off because I have to keep checking and un-checking the box each time I render. Moreover, the layers that aren't used for rendering are deleted/overwritten, so I have to save them as images for the compositer.

The viewlayers already support information for each renderer, such as passes, denoising, and number of samples. I don't think this will be terribly hard to do, but I could be wrong!

NOTE: I know it's probably possible to use Python to work around this. I am willing to do this for my own project, but I think other Blender users will want this feature.

96%

Development Status: In Development

Upvote 24 Downvote 1
Josephbburg
4 Apr 2019

5 Comments

Josephbburg Author

UPDATE: It seems this feature is under consideration, and must wait for asset management/ dynamic overrides to land (hopefully by 2.81). I will update the description to In-Development for now, since Pablo suggested it as a future feature in last week's Blender Today at 48:50 (just after answering my question about EEVEE!).

1
Draise

* @Josephbburg * a great step in the right direction. Along with overrides, this can become a capable pass system.

1
Josephbburg Author

* @Andres Stephens - Trinumedia * From what I understand this IS an override. Dynamic overrides won't be in 2.81 or probably 2.82, but they're in the works!

nunoalexconceicao

I would see this as something simpler than an override, right now the render properties are global to the scene and basically we also need to have a local render property that could be enabled per render layer. In the view layer properties along with the other check boxes of "Use for rendering" and "Render Single Layer" there could be another check box like "Use local render properties" . This could expose the layer name to a drop down on the Render properties where we could have different render settings than the global scene render properties. Hope this makes sense

Josephbburg Author

* @nunoalexconceicao * It makes sense but from a software architecture point-of-view I think it's still an override. I donno, it seems like this won't be done until near the end of 2020, but overrides are at least one of the big priorities for the year.