Python Nodes for Cycles, Eevee, Compositor and Textures #61655
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61655
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?
This task has the purpose of adding RNA classes that can be used to create custom python nodes for builtin nodetree types.
The main purpose of these classes is to provide a better interface for custom nodes, that can be used in the Shader, Compositor, and Texture Node Editors.
Any comments, sugestions and corrections are welcome.
Some custom nodes for testing the patches:
Testing_nodes.py
Added subscriber: @Secrop
This comment was removed by @Secrop
Added subscriber: @povmaniac
Added subscriber: @lvxejay
@Secrop What would it take to do these two?
//Add Python utilities for managing custom nodes
Add Python utilities for converting nodegroups into custom nodes//
@lvxejay I'd like to have custom nodes behaving like addons, with the option to select which nodes should be used or not. I already have some stuff written for the Preferences_Editor and I have an old convertor that can be improved; but this will require custom nodes to have some common structure (like a dict similar to 'bl_info' and specific register/unregister functions). I haven't fully defined how custom nodes should be written, and both managing and creating custom nodes need to have that definition apriori.
Added subscriber: @qwiglydee
This comment was removed by @qwiglydee
This comment was removed by @qwiglydee
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @timodriaan
This issue was closed last month, but what is the practical status? The code above works (when updated to the new socket interface system). Was the documentation ever published?
@knox the current documentation is only the auto-generated.. i don't think there's much to say about customnodegroups, but if you know of something that should be added to the documentation (or by creating some templates for the text editor), we could discuss it in devtalk.