Error with custom nodes and node editor #60384
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#60384
Loading…
Reference in New Issue
Block a user
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?
possibly related to #60382.
When I view the node editor with appleseed as the render engine, all my nodes appear in the add list:
When I try to add a node, I get this:
No other details are provided. So I have no idea why the error is occurring or how to fix it.
For the sake of completeness, I've attached the full terminal log plus the Python file we use for creating the nodes and node tree.
nodes.py
Untitled-1.txt
Added subscriber: @jdent02
Added subscriber: @lichtwerk
Havent look in depth, but the
AppleseedOSLNode
polls forAppleseedNodeTree
whereas the nodetree itself is calledAppleseedOSLNodeTree
, could this be the cause?Added subscriber: @JacquesLucke
Besides that it would be helpful when you try to remove everything from the file that is not necessary to reproduce the bug.
Also currently the script you provided does not run on its own, which makes it hard to reproduce the issue.
Changed status from 'Open' to: 'Archived'
Good Lord that's embarrassing, must've been doing stuff too late into the evening.
Philipp, you are correct.