Geometry nodes. New/Copy button inconsistent behavior #86208
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#86208
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-8.1-6.3.9600-SP0 64 Bits
Graphics card: GeForce GTX 660 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40
Blender Version
Broken: version: 2.92.0 release, 2.93.0 Alpha, branch: master, commit date: 2021-03-02 07:40, hash:
c4ef90f5a0
Short description of error
New/copy button work different, accordingly materials or particle systems for example.
It do not create copy. Also there is no direct way to create copy (duplicate) of GN-tree (and indirect have a bug now #86207)
{F9861009 size=full}
2021-03-02_23-25-53.mp4
Added subscriber: @Vyach
Added subscriber: @lichtwerk
It is inconsistent with the other mentioned, not sure it is a bug though.
Workaround for making real copies of the nodegroups:
Added subscriber: @GregoryS
Scene and View Layers also use this icon, but use submenu: New, Copy Settings, etc.
Already tried.
Direct copy-paste have a bug.
Copying from Blender file structure creates grouped node instead tree. And ungrouping will ruin input and output
So, actually no workaround, that will give exact same result.
Changed status from 'Needs Triage' to: 'Confirmed'
OK, will confirm for now and check soonish
OK, since this is marked as good first issue for community contributions, will step down.
Added subscriber: @ab_stanton
Hi, I have a working fix for this, but I have a question about how it should be implemented. I was wondering if I should implement a new operator that copies the active tree in the geometry nodes modifier, and keep the old NewGeometryNodeTreeAssign. Then assign the new operator to the relevant button, or if I should just change the functionality of NewGeometryNodeTreeAssign to copy the active tree if it exists?
This issue was referenced by
ae650b016f
Changed status from 'Confirmed' to: 'Resolved'