Blender 2.79 to 2.80 material edit breaks material #64069

New Issue

Zak Tab · 2019-05-01T21:29:45+02:00

Zak Tab commented

2019-05-01 21:29:45 +02:00

System Information
Operating system: Ubuntu 16.04
Graphics card: MSI 1080Ti

Blender Version
Broken: 2.80, 75f551faca, master, 2019-04-07
Worked: 2.79

Short description of error
The modifications to the material shader nodemap break the texture.
When the nodes are saved in 2.79, and opened in 2.80, before displacement outputs, we prepend a displacement node. This causes our texture to go all black or all white.

Exact steps for others to reproduce the error
Download MAT_test.blend, created on blender 2.79. Look at the custom bump map being used in the material called: Changed. Save this file.
Open the file in Blender 2.80 and look at the material in Rendered or LookDev.
The material has changed from its original color (teal) to black.

Note: This modification to the material node-tree does not occur if the Cube object in MAT_test.blend is appended to a new file in Blender 2.80.

Note: MAT_test.blend is saved in 2.79, MAT_test_new.blend is saved in 2.80, and is the expected outcome of the above steps.

MAT_test.blend

MAT_test_new.blend

**System Information** Operating system: Ubuntu 16.04 Graphics card: MSI 1080Ti **Blender Version** Broken: 2.80, 75f551facaf0, master, 2019-04-07 Worked: 2.79 **Short description of error** The modifications to the material shader nodemap break the texture. When the nodes are saved in 2.79, and opened in 2.80, before displacement outputs, we prepend a displacement node. This causes our texture to go all black or all white. **Exact steps for others to reproduce the error** Download `MAT_test.blend`, created on blender 2.79. Look at the custom bump map being used in the material called: `Changed`. Save this file. Open the file in `Blender 2.80` and look at the material in `Rendered` or `LookDev`. The material has changed from its original color (teal) to black. Note: This modification to the material node-tree does not occur if the Cube object in `MAT_test.blend` is appended to a new file in `Blender 2.80`. Note: `MAT_test.blend` is saved in `2.79`, `MAT_test_new.blend` is saved in `2.80`, and is the expected outcome of the above steps. [MAT_test.blend](https://archive.blender.org/developer/F6999523/MAT_test.blend) [MAT_test_new.blend](https://archive.blender.org/developer/F6999524/MAT_test_new.blend)

Zak Tab commented

2019-05-01 21:29:45 +02:00

Added subscriber: @zakleap

Sebastian Parborg commented

2019-05-02 15:28:42 +02:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-05-02 15:28:42 +02:00

I can not reproduce this on my end. The 2.79 file is teal in rendered mode in both 2.79 and the latest 2.8 build for me.

Zak Tab commented

2019-05-02 17:03:47 +02:00

@ZedDB I can confirm that in the latest version, the issue remains --> hash 480a09a92f7f.
You may have been looking at the rendered version through cycles. Eevee rendered view or LookDev show an all black cube.
The teal color comes back if the added Displacement node is bypassed.
I am happy to supply any more information.

@ZedDB I can confirm that in the latest version, the issue remains --> hash `480a09a92f7f`. You may have been looking at the rendered version through cycles. `Eevee` rendered view or `LookDev` show an all black cube. The teal color comes back if the added `Displacement` node is bypassed. I am happy to supply any more information.

Sebastian Parborg commented

2019-05-02 17:24:02 +02:00

Changed status from 'Open' to: 'Archived'

Sebastian Parborg closed this issue

2019-05-02 17:24:02 +02:00

Sebastian Parborg self-assigned this 2019-05-02 17:24:02 +02:00

Sebastian Parborg commented

2019-05-02 17:24:02 +02:00

Eevee/Lookdev does not support displacement/vector displacement.

Zak Tab commented

2019-05-02 17:42:41 +02:00

@ZedDB In that case, should the displacement node be automatically added during conversion? If it's not supported, wouldn't it be better to add the displacement node only to the cycles material output and not to the eevee?

Sebastian Parborg commented

2019-05-02 17:46:35 +02:00

There are no separate materials anymore in 2.8. Eevee and cycles both uses the same.

Zak Tab commented

2019-05-02 20:28:20 +02:00

@ZedDB Material Output still supports rendering engine specific outputs.

nodes['Material Output'].target

If the displacement node is not supported for Eevee, the automated modifier should instead create two Material Output nodes, one for Cycles and one for Eevee and connect the displacement node to the Cycles - Material Output node and not to the Eevee - Material Output node. It doesn't make sense to introduce unsupported nodes to the Eevee shader if we don't need to.

@ZedDB `Material Output` still supports rendering engine specific outputs. ``` nodes['Material Output'].target ``` If the displacement node is not supported for `Eevee`, the automated modifier should instead create two `Material Output` nodes, one for `Cycles` and one for `Eevee` and connect the displacement node to the `Cycles - Material Output` node and not to the `Eevee - Material Output` node. It doesn't make sense to introduce unsupported nodes to the Eevee shader if we don't need to.

Sebastian Parborg commented

2019-05-03 10:03:00 +02:00

There is no eevee backend in 2.79 and your file is using cycles. So if you want anything else to happen, then this is a feature request and should go to: https://blender.community/c/rightclickselect/

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

Blender 2.79 to 2.80 material edit breaks material #64069