blender/blender-addons
19
43
Fork 96
Code Issues 631 Pull Requests 27 Projects 1 Releases Wiki Activity

Using "Lazy Mix" in Node Wrangler add-on breaks the already existing connection. #104438

New Issue
Closed
opened 2023-02-26 03:37:46 +01:00 by Marius Eugen Mihai · 3 comments
Marius Eugen Mihai commented 2023-02-26 03:37:46 +01:00
Copy Link

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49

Add-On
Node Wrangler Add-On

Blender Version
Broken: version: 3.5.0 Beta, branch: blender-v3.5-release, commit date: 2023-02-24 19:46, hash: 01d4c8462d38
Worked: version: 3.5.0 Alpha, branch: master, commit date: 2023-02-06 23:58, hash: rB8703db393bfb

Note: both add-on versions show the same version number (3.43), but there are code differences between the two.

Short description of error
When using the "Lazy Mix" operation, either by using the shortcut (Ctrl+Shift+RMB drag), or by selecting two nodes and calling the operation through the menu (Shift+W > Merge Selected Nodes > Use Mix Nodes > Any) breaks an already existing connection, instead of adding the mix node along the existing connection, as it's meant to.

Exact steps for others to reproduce the error
Use the default startup scene or create a cube in a new empty file. Switch to the "Shading" tab. Add a new material to the cube (if using the default startup scene, one is already applied). Add two RGB nodes (Shift+A > Input > RGB). Connect one of the nodes to the "Base Color" input of the "Principled BSDF" node. Place your mouse pointer over one of the RGB nodes and, while holding down Ctrl+Shift+RMB, drag the pointer from one RGB node to the other until both of them are highlighted by a green border and release the mouse button. Alternatively, select both nodes and use the Node Wrangler menu to perform the operation (Shift+W > Merge Selected Nodes > Use Mix Nodes > Mix(Or any blend mode)).
At this point, the two nodes should be joined by a newly created Mix node, but the connection to the base color input of the Principled BSDF node has been severed. The expected behavior (as was the case in older versions of the add-on) was to have the two nodes joined by a mix node and the new mix node to be further connected to the base color input. In other words, the mix node is added to the chain without breaking it.

lazy mix issue.jpg

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 528.49 **Add-On** Node Wrangler Add-On **Blender Version** Broken: version: 3.5.0 Beta, branch: blender-v3.5-release, commit date: 2023-02-24 19:46, hash: `01d4c8462d38` Worked: version: 3.5.0 Alpha, branch: master, commit date: 2023-02-06 23:58, hash: `rB8703db393bfb` Note: both add-on versions show the same version number (3.43), but there are code differences between the two. **Short description of error** When using the "Lazy Mix" operation, either by using the shortcut (Ctrl+Shift+RMB drag), or by selecting two nodes and calling the operation through the menu (Shift+W > Merge Selected Nodes > Use Mix Nodes > Any) breaks an already existing connection, instead of adding the mix node along the existing connection, as it's meant to. **Exact steps for others to reproduce the error** Use the default startup scene or create a cube in a new empty file. Switch to the "Shading" tab. Add a new material to the cube (if using the default startup scene, one is already applied). Add two RGB nodes (Shift+A > Input > RGB). Connect one of the nodes to the "Base Color" input of the "Principled BSDF" node. Place your mouse pointer over one of the RGB nodes and, while holding down Ctrl+Shift+RMB, drag the pointer from one RGB node to the other until both of them are highlighted by a green border and release the mouse button. Alternatively, select both nodes and use the Node Wrangler menu to perform the operation (Shift+W > Merge Selected Nodes > Use Mix Nodes > Mix(Or any blend mode)). At this point, the two nodes should be joined by a newly created Mix node, but the connection to the base color input of the Principled BSDF node has been severed. The expected behavior (as was the case in older versions of the add-on) was to have the two nodes joined by a mix node and the new mix node to be further connected to the base color input. In other words, the mix node is added to the chain without breaking it. ![lazy mix issue.jpg](/attachments/929db051-03b9-40d6-8b35-5409776770dd)
lazy mix issue.jpg
430 KiB
Marius Eugen Mihai added the
Type
Report
Priority
Normal
Status
Needs Triage
 labels 2023-02-26 03:37:46 +01:00
Germano Cavalcante commented 2023-02-27 18:50:35 +01:00
Member
Copy Link

Thanks for the report, but however, this appears to be a feature request rather than a bug report, and it's not within the scope of the Triage team to accept feature requests.

We suggest submitting feature requests through the appropriate channels or forums designated by the product team for future consideration:
https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

For more information on what is considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug

Thanks for the report, but however, this appears to be a feature request rather than a bug report, and it's not within the scope of the Triage team to accept feature requests. We suggest submitting feature requests through the appropriate channels or forums designated by the product team for future consideration: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests For more information on what is considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
Blender Bot added
Status
Archived
 and removed
Status
Needs Triage
 labels 2023-02-27 18:50:38 +01:00
Damien Picard commented 2023-02-27 19:12:58 +01:00
Member
Copy Link

@mano-wii Actually I can confirm that it’s a regression: before !104425, using lazy mix would automatically connect the new MixRGB node to the output of the already-existing link.

This happens because the new mix node type has several outputs, and the hidden float output is connected instead of the color one.

CC @wannes.malfait

@mano-wii Actually I can confirm that it’s a regression: before !104425, using lazy mix would automatically connect the new MixRGB node to the output of the already-existing link. This happens because the new mix node type has several outputs, and the hidden float output is connected instead of the color one. CC @wannes.malfait
Blender Bot added
Status
Needs Triage
 and removed
Status
Archived
 labels 2023-02-27 19:13:00 +01:00
Damien Picard added
Status
Confirmed
 and removed
Status
Needs Triage
 labels 2023-02-27 19:13:59 +01:00
Germano Cavalcante commented 2023-02-27 19:26:07 +01:00
Member
Copy Link

@mano-wii Actually I can confirm that it’s a regression: before !104425, using lazy mix would automatically connect the new MixRGB node to the output of the already-existing link.

Oh! My mistake! Thanks for heads up.

> @mano-wii Actually I can confirm that it’s a regression: before !104425, using lazy mix would automatically connect the new MixRGB node to the output of the already-existing link. Oh! My mistake! Thanks for heads up.
Germano Cavalcante added
Priority
High
 and removed
Priority
Normal
 labels 2023-02-27 19:26:34 +01:00
Blender Bot added
Status
Resolved
 and removed
Status
Confirmed
 labels 2023-03-05 11:48:03 +01:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
Interest
Animation & Rigging

  
Interest
Blender Cloud

  
Interest
Collada

  
Interest
Core

  
Interest
Documentation

  
Interest
Eevee & Viewport

  
Interest
Geometry Nodes

  
Interest
Grease Pencil

  
Interest
Import and Export

  
Interest
Modeling

  
Interest
Modifiers

  
Interest
Nodes & Physics

  
Interest
Pipeline, Assets & IO

  
Interest
Platforms, Builds, Tests & Devices

  
Interest
Python API

  
Interest
Rendering & Cycles

  
Interest
Sculpt, Paint & Texture

  
Interest
Translations

  
Interest
User Interface

  
Interest
UV Editing

  
Interest
VFX & Video

  
Meta
Good First Issue

  
Meta
Papercut

  
Module
Add-ons (BF-Blender)

  
Module
Add-ons (Community)

  
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 Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
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
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
3 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-addons#104438
No description provided.
Delete Branch "%!s()"

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?