Geometry Node cannot have two group output nodes at the same time #85220

Closed
opened 2021-01-30 05:19:09 +01:00 by Yuro · 10 comments

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: AMD Radeon(TM) R7 Graphics ATI Technologies Inc. 4.5.13539 Core Profile Context 24.20.13011.1009

Blender Version
Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-01-29 16:35, hash: d0f59d3842
Worked: (newest version of Blender that worked as expected)

Short description of error
Geometry Node cannot have two Group Output nodes at the same time, otherwise it will invalid.
The expected behavior in the Shader Editor:
1.gif
Gometry Node Editor:
2.gif

Exact steps for others to reproduce the error
Open the geometry Node Editor.
Duplicate the group output node, Subdivision Surface will invalid.
Geometry Node Group Output.blend

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: AMD Radeon(TM) R7 Graphics ATI Technologies Inc. 4.5.13539 Core Profile Context 24.20.13011.1009 **Blender Version** Broken: version: 2.93.0 Alpha, branch: master, commit date: 2021-01-29 16:35, hash: `d0f59d3842` Worked: (newest version of Blender that worked as expected) **Short description of error** Geometry Node cannot have two Group Output nodes at the same time, otherwise it will invalid. The expected behavior in the Shader Editor: ![1.gif](https://archive.blender.org/developer/F9604870/1.gif) Gometry Node Editor: ![2.gif](https://archive.blender.org/developer/F9604872/2.gif) **Exact steps for others to reproduce the error** Open the geometry Node Editor. Duplicate the group output node, Subdivision Surface will invalid. [Geometry Node Group Output.blend](https://archive.blender.org/developer/F9604888/Geometry_Node_Group_Output.blend)
Author

Added subscriber: @Yuro

Added subscriber: @Yuro
Robert Guetzkow changed title from Gometry Node cannot have two group output nodes at the same time to Geometry Node cannot have two group output nodes at the same time 2021-01-30 09:47:41 +01:00

Added subscribers: @JacquesLucke, @rjg

Added subscribers: @JacquesLucke, @rjg

This is a design question that would require a decision by the module team how this is intended to work.

Geometry nodes don't seem to follow the same concept as material nodes as there apparently should only ever be one group output. There also isn't an entry to add additional group outputs in the Add menu, but duplicating an existing node of that type works. Perhaps the copying & pasting and duplicating of the node should be prevented to be consistent in that only ever one is allowed or there needs to be a concept of an active output similar to the material nodes.

CC @JacquesLucke

This is a design question that would require a decision by the module team how this is intended to work. Geometry nodes don't seem to follow the same concept as material nodes as there apparently should only ever be one group output. There also isn't an entry to add additional group outputs in the *Add* menu, but duplicating an existing node of that type works. Perhaps the copying & pasting and duplicating of the node should be prevented to be consistent in that only ever one is allowed or there needs to be a concept of an active output similar to the material nodes. CC @JacquesLucke
Author

Thank you for your reply.
One group output will be fine. In the shader editor, I like to use this method to check different parts of complex nodes. Emm... I have to say it is very useful :)

Thank you for your reply. One group output will be fine. In the shader editor, I like to use this method to check different parts of complex nodes. Emm... I have to say it is very useful :)
Member

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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

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

Will confirm for now, agree one of the two should be implemented:

copying & pasting and duplicating of the node should be prevented to be consistent in that only ever one is allowed or there needs to be a concept of an active output similar to the material nodes.

Will confirm for now, agree one of the two should be implemented: > copying & pasting and duplicating of the node should be prevented to be consistent in that only ever one is allowed or there needs to be a concept of an active output similar to the material nodes.

Added subscriber: @dfelinto

Added subscriber: @dfelinto

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

Thanks for the report, but this is a not a bug. The system is working as it was designed to. It works the same way any other Node Group in Blender, including the ones used in material.

Thanks for the report, but this is a not a bug. The system is working as it was designed to. It works the same way any other Node Group in Blender, including the ones used in material.
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
4 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#85220
No description provided.