| Jeroen Bakker (jbakker) |
| Jeroen Bakker (jbakker) | |
| Jul 17 2019, 3:24 PM |
| Jeroen Bakker (jbakker) |
| Joseph Brandenburg (TheAngerSpecialist) |
| Stefan Werner (swerner) |
This task will add options shading pop-over when using cycles in the viewport.
Details depends on what is being discussed in T68312: LookDev & Eevee Preview.
Here is a node graph that supports these features.
The Rotation maps to the Mapping Rotation-Z
The Background slider maps to the Background value
The Studiolight HDRI maps to the Environment Texture.
A future requirement is to change the Strength of the background. This can be connected to the Intensity node.
| rB Blender | |||
| D5292 Cycles: LookDev Mode | |||
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | TO DO | Jeroen Bakker (jbakker) | T67218 EEVEE Preview Shading Mode (Parent Task) | ||
| Archived | TO DO | Jeroen Bakker (jbakker) | T66746 Use External Render Engines for Look Development | ||
| Resolved | TO DO | Jeroen Bakker (jbakker) | T67128 Cycles Viewport Rendering Shading Options | ||
| Resolved | TO DO | Jeroen Bakker (jbakker) | T67188 Write Documentation for the EEVEE Preview shading mode |
I wonder if we might have separate output nodes for LookDev and Render? I use EEVEE to do NPR shading, which results in shaders with hundreds of nodes. I'd like to have simpler versions of the materials in LookDev mode so I can use them while animating without losing performance. It isn't a problem with simpler node networks -- if I was doing PBR I could animate in lookdev no problem.
This is entirely possible when using Cycles as the renderer, since EEVEE has its own output node. But Cycles can't use the Shader-to-RGB node. And again, it's already a beautifully streamlined process with the Principled BSDF.
Thanks for all your hard work!