mixRGB node becomes UNDEFINED when switching to 3.4.0 #103252
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#103252
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows 10 Home - OS Build 19045.2364
Graphics card:
Blender Version
Broken: 3.4.0
Worked: 3.3.0
Short description of error
When switching to 3.4.0 mixRGB nodes in the shading editor will be labled as UNDEFINED and become overlayed with red. This affects all materials in a scene that us mixRGB nodes causing then to appear as the default grey color in renders. It seems to have to do with a failure to convert mixRGB to the new Mix node.
Exact steps for others to reproduce the error
Open a .blend file that contained materials with mixRGB nodes in 3.4.0.
Blender mixRGB node broken.blend
Added subscriber: @DinnngRoomTable
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
Hi, thanks for the report. In newer version MixRGB node is replaced by mix node.
This compatibility is expected when you open file saved in 3.4 in previous versions. But your file seems broken in both version.
Did you save the same file in both versions? 3.4 and then in 3.3? In such way I'm able to reproduce this (but this is not a bug)
Yeah I realize that the node is supposed to be replaced, but some times it after successfully converting into the standardized mix node it would break and become undefined. I had already removed blender 3.3.0 from my computer so I don't think it could be caused from the way that you said. I uninstalled and then reinstalled 3.4.0, as the problem would occur every couple of hours and haven't had the problem appear since, so the only thing I can think is it had something to do with that.
mixRGB node bceomes UNDEFINED when switching to 3.4.0to mixRGB node becomes UNDEFINED when switching to 3.4.0Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs User Info'
The attached file was last saved in 3.4, and the type and idname are correctly set to
SH_NODE_MIX
andShaderNodeMix
, but it appears the storage is lost, which happens when he file is saved in an older version.Could you replicate this issue from scratch without saving in an older version of Blender? Otherwise, I think we should assume that this file is in an invalid state regardless.
Hi, any updates?
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.
Same problem.
When switching to 3.4.0 mixRGB nodes in the shading editor will be labled as UNDEFINED and become overlayed with red.
I also encountered this problem, although my issue seems to use the Asset Browser.
In 3.3 or earlier, create a material that uses a the old MixRGB node, and mark it as an Asset. Save and close.
In 3.4, create a new blend file, and assign the asset material to an object via the Asset Browser. If you inspect the Shader graph immediately, you will see the MixRGB(old) node successfully converted to MixRGB(new), and the scene renders correctly.
However, if you save the file with 3.4, close it, and open it in 3.4 again, the node will now be Undefined and red, and the object will render in default gray.
The same thing happens if you open a 3.3 file via the 3.4 Asset Browser (right click -> Open .blend file), then save it somewhere and open it again in 3.4. Looks converted at first, but is broken after save/reopen.