Custom node sockets don't get relinked when dropping a node on an existing link #93430
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93430
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-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 496.49
Blender Version
Broken: version: 3.0.0 Release Candidate, branch: master, commit date: 2021-11-25 17:24, hash:
2fb8c6805a
Worked: version: 3.0.0 Beta, branch: master, commit date: 2021-11-07 23:44, hash:
56ee96349d
(maybe also with a bit newer versions, that was the last one I was using before updating to the release candidate)Short description of error
When creating custom python nodes that have only custom sockets, the node can't be dropped onto an existing link. This is not the case if the node has normal blender sockets, only with custom ones. It also doesn't happen if the node has blender and custom sockets as the blender sockets will be connected and the custom ones ignored.
Exact steps for others to reproduce the error
If the same process is repeated in the version marked as working above the node is connected to the other two. If the same thing is done with the original default custom node template, the custom sockets will be ignored and the blender internal sockets will connect.
custom node tree.blend
Added subscriber: @JoshuaKnauber
#93438 was marked as duplicate of this issue
Added subscriber: @lichtwerk
Has also been reported in #93438 (Custom nodes no longer get inserted in between two linked nodes)
This issue was referenced by
61fe0d6264
This issue was referenced by
ab2a7aa0da
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Resolved'
Can confirm this has been fixed by:
ab2a7aa0da
Will close the report. Feel free to reopen if you are still able to reproduce. And thanks for the report :)
Added subscriber: @valera-8
@PratikPB2123 @OmarEmaraDev
This is still broken for my add-on in 3.0.0, can you take a look at it please?
terrain_nodes_demo.zip
@valera-8 This fix didn't make it in 3.0 unfortunately, we only fixed it a few days before the 3.0 release.
This comment was removed by @JoshuaKnauber
@lichtwerk , would it be safe to add this fix for 3.0.1? (Commit did not break anything so far)
This should definitely be in 3.0.1, thanks for the fix much appreciated!
On the list now #93479 (3.0 Potential candidates for corrective releases)