Fix #104438 : Lazy mix connects wrong sockets #104457
No reviewers
Labels
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
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104457
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "wannes.malfait/blender-addons:nw_mix_disabled_sockets"
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?
Because the new mix nodes have different modes, the correct output
socket to connect is not just the first one, but the first enabled one.
There were already some checks in place for this, but apparently not yet
in all the needed places.
The current state of the code for the "Merge Nodes" operator is
terrible, and should probably be refactored in a future update. It is
becoming very hard to maintain.
@pioverfour I tested this as much as I could, but I'm not aware of all of node wrangler's functionality. Could you test this as well to make sure that there is not some other thing that I forgot to fix, or broke by accident?
Me neither, I probably use one tenth of it! I didn’t even know about the lazy mix reconnect.
I’ll test the PR tomorrow. :)
LGTM.
Out of scope for this PR, but it would be nice to detect the socket types for shading nodes, and use that as the type for the mix node since it can now be float, color, or vector.
I was thinking the same thing, but that is indeed a new feature, and should be for 3.6. It would probably be best to refactor the current code before that change though (and maybe add some tests).