Page MenuHome

Problems with materials nodes in Alpha Trees
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15

Blender Version
Broken: version: 3.4.0 Alpha, branch: master, commit date: 2022-09-04 04:25, hash: rB0ff920b77779
Worked: version: 3.4.0 Alpha, branch: master, commit date: 2022-08-14 18:40, hash: 659b63751d63

Loaded materials of the Alpha Trees addon are not correct
When opening an existing file with the Alpha Trees addon loaded and visible, there is a noticeable problem with colours. Maybe it's due to some MixRGB or Hue/Saturation node having a bug.

Exact steps for others to reproduce the error
Add a plane, scatter Alpha Trees, reduce saturation and open with a new version.

Event Timeline

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Sep 6 2022, 5:12 PM

I can confirm the issue.

rBbfa0ee13d539: Node: Mix node is the first "bad" commit.

But the file is too complex and too time consuming for us to track down (and determine if it's really a bug or a temporary indeterminate behavior).

We require the bug reporter to narrow down the problem.

Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Original bug report file opens in both 3.2 and 3.4 alpha with red undefined node in montagne material

This file created in 3.2 opens fine in 3.4 alpha

As @Germano Cavalcante (mano-wii) stated it is difficult to track down the issue in the original bug report file.

It seems related to the new Mix Node but it's unclear where or how the bug has happened.

Saving a 3.4 file with the new node will not be forward compatible with 3.2.

3.4 is in alpha so please be careful with any important or production files.

No, the problem is still in 3.4.0-alpha+master.e108d67635a0-windows.amd64-release.

@Stefano Toneatto (stefanotoneatto) yes, it's still replicable. But as Germano said, we need reporter to simplify the file.
At the moment its quite difficult to investigate with larger node-tree

But the file is too complex and too time consuming for us to track down (and determine if it's really a bug or a temporary indeterminate behavior).
We require the bug reporter to narrow down the problem.
Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

@Stefano Toneatto (stefanotoneatto) this report was closed automatically by the commit for forward compatibility -- see rB680fa8a523e0

The patch will not fix files that are opened and saved in older versions of Blender.