Page MenuHome

Geometry nodes. New/Copy button inconsistent behavior
Closed, ResolvedPublicBUG

Description

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: rBc4ef90f5a0b1

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 T86207)

Event Timeline

It is inconsistent with the other mentioned, not sure it is a bug though.

Workaround for making real copies of the nodegroups:

  • Outliner > Blender File view > Node Groups > copy / paste

Scene and View Layers also use this icon, but use submenu: New, Copy Settings, etc.

Vyacheslav (hitrpr) added a comment.EditedMar 4 2021, 2:05 AM

Workaround for making real copies of the nodegroups:

  • Outliner > Blender File view > Node Groups > copy / paste

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.

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Confirmed.Mar 4 2021, 9:50 AM
Philipp Oeser (lichtwerk) claimed this task.

OK, will confirm for now and check soonish

Dalai Felinto (dfelinto) changed the subtype of this task from "Report" to "Bug".
Dalai Felinto (dfelinto) moved this task from Backlog to Community Tasks on the Geometry Nodes board.

OK, since this is marked as good first issue for community contributions, will step down.

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?