Implement "Mute" for geometry nodes #82546

Closed
opened 2020-11-09 19:57:09 +01:00 by Dalai Felinto · 12 comments

Mute is suppose to make the node to be bypassed. It is not working at the moment though.

  • If the input and output have a geometry connected, just pass it through.
  • If the input and output have a color connected, just pass it through.

Muting means the node can be considered removed from the nodetree. In some cases it means assuming the node is disconnected even (or passing 0.0?) leaving the following node to use its default values instead.

Mute is suppose to make the node to be bypassed. It is not working at the moment though. * If the input and output have a geometry connected, just pass it through. * If the input and output have a color connected, just pass it through. Muting means the node can be considered removed from the nodetree. In some cases it means assuming the node is disconnected even (or passing 0.0?) leaving the following node to use its default values instead.
Author
Owner

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Author
Owner

Added subscribers: @dfelinto, @PiloeGAO

Added subscribers: @dfelinto, @PiloeGAO

#82565 was marked as duplicate of this issue

#82565 was marked as duplicate of this issue
Contributor

Added subscriber: @KenzieMac130

Added subscriber: @KenzieMac130
Contributor

How will muting be handled if the downstream nodes depend on generated values from the muted node? (Such as muting a mesh analysis node that's constant value outputs or generated attributes used by other nodes to do cleanup) Should it just throw an error if it runs into dependency problems downstream?

How will muting be handled if the downstream nodes depend on generated values from the muted node? (Such as muting a mesh analysis node that's constant value outputs or generated attributes used by other nodes to do cleanup) Should it just throw an error if it runs into dependency problems downstream?
Author
Owner

For the existent nodes it seems very straightforward. If the input and output have a geometry connected, just pass it through. If the input and output have a color connected, just pass it through. Muting means the node can be considered removed from the nodetree. In your hypothetical example it would return 0.0, or 0.0, 0.0, 0.0, or no geometry, depending on the output.

For the existent nodes it seems very straightforward. If the input and output have a geometry connected, just pass it through. If the input and output have a color connected, just pass it through. Muting means the node can be considered removed from the nodetree. In your hypothetical example it would return 0.0, or 0.0, 0.0, 0.0, or no geometry, depending on the output.

Added subscribers: @EchoDot, @rboxman

Added subscribers: @EchoDot, @rboxman

Added subscriber: @MiroHorvath

Added subscriber: @MiroHorvath

Not sure if it is in scope of this task, but have you considered also to allow user to mute all nodes from the selected one up to the Output node?
image.png
I don't have Houdini here right now, but if I'm not mistaken there's something similar in opposite fashion that user can preview node graph up to the selected node.

Not sure if it is in scope of this task, but have you considered also to allow user to mute all nodes from the selected one up to the Output node? ![image.png](https://archive.blender.org/developer/F9251949/image.png) I don't have Houdini here right now, but if I'm not mistaken there's something similar in opposite fashion that user can preview node graph up to the selected node.
Member

Added subscriber: @HooglyBoogly

Added subscriber: @HooglyBoogly
Member

In #82546#1051658, @MiroHorvath wrote:
Not sure if it is in scope of this task, but have you considered also to allow user to mute all nodes from the selected one up to the Output node?

I think some sort of viewer option for a node might be more effective at doing this.

> In #82546#1051658, @MiroHorvath wrote: > Not sure if it is in scope of this task, but have you considered also to allow user to mute all nodes from the selected one up to the Output node? I think some sort of viewer option for a node might be more effective at doing this.
Author
Owner

Changed status from 'Confirmed' to: 'Resolved'

Changed status from 'Confirmed' to: 'Resolved'
Dalai Felinto self-assigned this 2020-12-18 14:55:33 +01:00
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#82546
No description provided.