Multi Input Socket for Nodes #84433
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#84433
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?
Design discussion about Multi Input Sockets.
Goal is to add node sockets that can take multiple inputs.
General idea is to display Multi Input Sockets multiple times as tall as a Single Input Socktes to indicate that they can take multiple inputs.
A first use case is the Join Geometry Node.
Other possible use cases could be other nodes that mix or join something and are often chained like the Alpha Over node in Compositor. Ideas are welcome.
Following are some mockups with some of my ideas thoughts and questions. I will update them as we collect ideas and feedback.
Questions are:
Changed status from 'Needs Triage' to: 'Needs User Info'
Added subscribers: @FabianSchempp, @HooglyBoogly
Added subscriber: @pablovazquez
I really like this idea, and it's great to see it considered completely. As the mock-ups show, it does bring up some questions. Here are some thoughts:
Added subscriber: @Rusculleda
This is great! The last mockup where it shows the individual sockets upon mouse over or expanding look especially interesting to me thinking about the eventual possibility of a color ramp node where each color stop is connected to a color input. (A bit out of topic here, but related and shows exciting coming possibilities!)
For a use case like color ramp, it would be useful if they where user sortable i guess.
I don't think these sort of sockets should be used where the order matters. For color ramp, I think it would be better to expose a varying number of separate sockets.
The goal of these sockets is to cut down on vertical space and remove that distinction, which is counter to the idea of making a clear order between different inputs.
This issue was referenced by
c5514d3a2a
I'm going to close this since what's described in this task is implemented and in master.
Changed status from 'Needs User Info' to: 'Resolved'