Nodegroup crash with custom nodes and sockets #115277
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#115277
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: macOS 13.6 (Intel), Windows 11
Graphics card:
Blender Version
Broken: 4.0
Worked: 3.6
Short description of error
Creating a nodegroup from a custom node that uses custom sockets in the Shader Graph (ShaderNodeTree) crashes Blender.
Exact steps for others to reproduce the error
The 4.0 API release notes mentions that for the new NodeTree interface, "socket_type accepts only base socket type names". Is there any way around this, or are addons now required to use their own NodeTree?
Right now, if you create a custom node with custom sockets in the Shader Graph, and then try to make NodeGroup out of it, it crashes Blender.
Attached is a blend file that shows the problem (it crashes both on macOS and Windows for me). To reproduce:
One thing I did notice is that if I manually create the node group and then create the nodes inside with all of the links, then it works as expected. So it sounds like it's something about the node.group_make operator that's failing.
The only ways I can see to workaround this:
I'm not fond of either option.
Thank you for bringing this issue to our attention, @ianhsieh. I can confirm that Blender is indeed crashing when trying to create a node group from a custom node that uses custom sockets in the Shader Graph.
The call stack indicates that there is a problem within the node interface when attempting to refine from a custom socket:
This indicates an issue at the Python C API level, possibly linked with how the new API handles custom socket types when creating node groups.
@JacquesLucke, (as the maintainer of nodes in Blender) does this issue ring a bell to you?