Problems with materials nodes in Alpha Trees #100846

Closed
opened 2022-09-06 08:03:43 +02:00 by Stefano Toneatto · 13 comments

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: 0ff920b777
Worked: version: 3.4.0 Alpha, branch: master, commit date: 2022-08-14 18:40, hash: 659b63751d

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.
Working.png

Not Working.png

untitled.blend

**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: `0ff920b777` 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. ![Working.png](https://archive.blender.org/developer/F13462313/Working.png) ![Not Working.png](https://archive.blender.org/developer/F13462312/Not_Working.png) [untitled.blend](https://archive.blender.org/developer/F13462316/untitled.blend)

Added subscriber: @stefanotoneatto

Added subscriber: @stefanotoneatto
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Added subscriber: @CharlieJolly

Added subscriber: @CharlieJolly

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I can confirm the issue.

bfa0ee13d5 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.

I can confirm the issue. bfa0ee13d5 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.
Member

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

This file created in 3.2 opens fine in 3.4 alpha
node_mix_bug.blend

As @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.

Original bug report file opens in both 3.2 and 3.4 alpha with red undefined node in montagne material ![image.png](https://archive.blender.org/developer/F13463074/image.png) This file created in 3.2 opens fine in 3.4 alpha [node_mix_bug.blend](https://archive.blender.org/developer/F13463071/node_mix_bug.blend) As @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.
Member

@stefanotoneatto, Any updates?

@stefanotoneatto, Any updates?

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

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

@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

In #100846#1413117, @mano-wii wrote:
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.

@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 > In #100846#1413117, @mano-wii wrote: > 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.

This issue was referenced by 680fa8a523

This issue was referenced by 680fa8a523e0df2181305a1d2abfb52011510f59
Member

Changed status from 'Needs User Info' to: 'Resolved'

Changed status from 'Needs User Info' to: 'Resolved'
Charlie Jolly self-assigned this 2022-09-22 18:09:47 +02:00
Member

@stefanotoneatto this report was closed automatically by the commit for forward compatibility -- see 680fa8a523

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

@stefanotoneatto this report was closed automatically by the commit for forward compatibility -- see 680fa8a523 The patch will not fix files that are opened and saved in older versions of Blender.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#100846
No description provided.