Geometry Nodes Copy/Create inconsistency #105982
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#105982
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?
System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.29
Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash:
rB55485cb379f7Worked: (newest version of Blender that worked as expected)
Short description of error
Throughout the entire Blender, the double list icon in a datablock selector is established to be an operator which makes a copy of the active datablock. This is consistent almost everywhere except in the Geometry Nodes modifier, where the very same button at the very same place creates a new empty GN node tree. This is even inconsistent with the visually identical datablock selector in the GN editor.
This causes unintended result as most users won't be familiar to this one exception to otherwise widely maintained rule. I was unable to find any other instance of a datablock selector in Blender where the double list icon button makes a new default datablock instead of making a copy of currently active one.
Exact steps for others to reproduce the error
Result: A new, empty datablock with the default name is created.
Expected: The existing datablock is copied under the number-padded name, like wit any other datablock anywhere in Blender.
As I understand it, geometry nodes should not copy the functionality of other parts of the blender, but it makes sense to ask again.
I don't think this is about GN itself but rather standardized behavior of datablock selector. What would be the justification for an exception here, compared to other datablock types (such as material nodes)?
Hi, thanks for the report.
Not completely true.
ICON_DUPLICATEis also used in image editor to create a new image (instead of copying the existing image).If I understand correctly, you're either proposing to replace the "new" with "copy" function from GN modifier or to assign a different icon for "create new" functions.
I'd suggest to discuss this either with devs or post it on RCS.
The issue reported here is a request for modified/improved behavior and not a bug in current behavior. Closing as this bug tracker is only for bugs and errors.
For user requests and feedback, please use other channels: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
No, you are not understanding this correctly. What I am proposing is that this decision was made in error, not intentionally. Otherwise it would not make any sense for the datablock selector in the Geometry Nodes editor, which selects the exact same type of datablock to do the copy instead of create new when pressing the exact same button.
There is just no other logical explanation for this other than this was made in error.
I wouldn't say the button is exclusively for copying data. Scenes and images have menu, masks use button to make new mask in VFX template, same goes for text.
Doesn't seem like terrible inconsistency to me, so will close.
Please use other channels for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests
For more information on why this isn't considered a bug, visit: https://wiki.blender.org/wiki/Reference/Not_a_bug
So should I open a new report that GN datablock selector in the GN editor makes a copy of existing datablock, when it should create a new one?
I am not saying, that it should create new one. Perhaps UI team would like to make this more consistent, or they may not care too much. In any case currently I don't see it being a bug or a mistake. This tracker is only for bugs, but you can discuss this issue on blender.chat or devtalk.