From aaf37e1216b2a9dfc43591e227c679a5b35af8c0 Mon Sep 17 00:00:00 2001 From: Luca Rood Date: Mon, 19 Jun 2017 16:31:10 +0200 Subject: Implement Eevee output node system This makes Eevee consistent with Cycles, by having a single output node, and multiple shader nodes that connect to it. Note that node systems for Eevee saved before this will be missing the output node, and thus will show an invalid material. This is easily resolved by connecting the shader output to a new output node. --- release/scripts/startup/nodeitems_builtins.py | 1 + 1 file changed, 1 insertion(+) (limited to 'release') diff --git a/release/scripts/startup/nodeitems_builtins.py b/release/scripts/startup/nodeitems_builtins.py index 2e2684a0524..59bf93696bc 100644 --- a/release/scripts/startup/nodeitems_builtins.py +++ b/release/scripts/startup/nodeitems_builtins.py @@ -219,6 +219,7 @@ shader_node_categories = [ NodeItem("ShaderNodeOutputMetallic", poll=object_shader_nodes_poll), NodeItem("ShaderNodeOutputSpecular", poll=object_shader_nodes_poll), NodeItem("ShaderNodeOutputMaterial", poll=object_shader_nodes_poll), + NodeItem("ShaderNodeOutputEeveeMaterial", poll=object_shader_nodes_poll), NodeItem("ShaderNodeOutputLamp", poll=object_shader_nodes_poll), NodeItem("ShaderNodeOutputWorld", poll=world_shader_nodes_poll), NodeItem("ShaderNodeOutputLineStyle", poll=line_style_shader_nodes_poll), -- cgit v1.2.3