Material Ouptut selection broken #62351

New Issue

Daniel Paul · 2019-03-08T11:29:37+01:00

Daniel Paul commented

2019-03-08 11:29:37 +01:00

System Information
Operating system: Win 10
Graphics card: GTX 1080 TI

Blender Version
2.80, 0ba143a1d6, 2019-03-08

When two Material Outputs per shader are used, blender doesn't change to the designated.
Rendering the right material output works but changing the shader refreshes only when related material output is selected.

For example:
One Output is set to eevee and the other is set to cycles.
Switching between cycles and eevee renderer loads the right tree.

When parameters from the cycles tree are changed while rendering in cycles,
there are no changes made when eevee material output is selected.

Possible fix: just select the designated material output automatically when the renderer is changed.

EEVEE_Cycles_Shader.blend

**System Information** Operating system: Win 10 Graphics card: GTX 1080 TI **Blender Version** 2.80, 0ba143a1d675, 2019-03-08 When two Material Outputs per shader are used, blender doesn't change to the designated. Rendering the right material output works but changing the shader refreshes only when related material output is selected. For example: One Output is set to eevee and the other is set to cycles. Switching between cycles and eevee renderer loads the right tree. When parameters from the cycles tree are changed while rendering in cycles, there are no changes made when eevee material output is selected. Possible fix: just select the designated material output automatically when the renderer is changed. [EEVEE_Cycles_Shader.blend](https://archive.blender.org/developer/F6783936/EEVEE_Cycles_Shader.blend)

Daniel Paul commented

2019-03-08 11:29:37 +01:00

Added subscriber: @DanielPaul

Philipp Oeser commented

2019-03-08 12:23:17 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-03-08 12:23:17 +01:00

Confirmed, checking...

Philipp Oeser commented

2019-03-08 14:56:37 +01:00

Seems like we are allowing a (shader) output node to become the current output (NODE_DO_OUTPUT) regardless of the target this node specifies.
Would suggest to check the current render engine and only allow the output node to be come the current output if it matches the target?

Had a go at the first steps in D4482, further discussion there...

Seems like we are allowing a (shader) output node to become the current output (`NODE_DO_OUTPUT`) regardless of the target this node specifies. Would suggest to check the current render engine and only allow the output node to be come the current output if it matches the target? Had a go at the first steps in [D4482](https://archive.blender.org/developer/D4482), further discussion there...

Philipp Oeser commented

2019-04-01 13:43:55 +02:00

will check on D4482 again

will check on [D4482](https://archive.blender.org/developer/D4482) again

Philipp Oeser commented

2019-04-01 15:24:38 +02:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2019-04-01 15:24:38 +02:00

Philipp Oeser self-assigned this 2019-04-01 15:24:38 +02:00

Philipp Oeser commented

2019-04-01 15:24:38 +02:00

Actually, the issue seems resolved already...
So we now do get updates when rendering in cycles if eevee material output is selected, but changes are made in nodes that are connected to the 'designated' cycles output node...

[unsure why I didnt notice this, since the change must have been made around the time when this report was made...]
[to doublecheck I will git bisect when this started to work...]

EDIT: 89fa6a7a06 was the commit that made this work.

No need to workaround by actually selecting the designated output, cycles will pick up updates from the tree where the most appropriate output is connected.

To my understanding, we can close this one [@DanielPaul: make sure to comment again/reopen if issues persist...]

Actually, the issue seems resolved already... So we now do get updates when rendering in cycles if eevee material output is selected, but changes are made in nodes that are connected to the 'designated' cycles output node... [unsure why I didnt notice this, since the change must have been made around the time when this report was made...] [to doublecheck I will git bisect when this started to work...] EDIT: 89fa6a7a06 was the commit that made this work. No need to workaround by actually selecting the designated output, cycles will pick up updates from the tree where the most appropriate output is connected. To my understanding, we can close this one [@DanielPaul: make sure to comment again/reopen if issues persist...]

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Material Ouptut selection broken #62351