It is impossible to add updated GN Node Group asset from the Asset Library to the scene #120134

Open
opened 2024-04-01 11:15:04 +02:00 by Ludvik Koutny · 5 comments
Contributor

System Information
Operating system: Windows-10-10.0.22631-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.76

Blender Version
Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: 40a5e739e270
Worked: (newest version of Blender that worked as expected)

Short description of error
It is impossible to add updated GN Node Group asset from Asset Library to the scene. Whenever the node group asset is added for the first time, some invisible ID match is used by asset browser to not overwrite existing asset under any circumstances, even after renaming it. So no matter what changes user makes to the original asset in the library, there is no way to bring it to the scene through asset browser.

It appears that the "Append (Reuse Data)" mode is broken, because it keeps reusing the data even after datablock name in the target scene was changed. If the name of the datablock was explicitly changed by the user to turn it into new, unique datablock, Asset Browser will still disregard it, and reuse data from the datablock which no longer has same name,

Exact steps for others to reproduce the error

  1. Create a GN Node Group asset in existing asset library, let's call it "Asset Group" for example.
  2. In a new scene, drag this asset from Asset Browser into GN node tree
  3. Modify this asset in the new scene (change something inside the "Asset Group" node group)
  4. Drag and drop the asset again from the Asset Browser
  5. Notice the drag-dropped version is not the asset from the Asset Library but the local modified one.
  6. Rename the node group to avoid conflict, for example to "Local Group"
  7. Drag and drop "Asset Group" from Asset Browser to node tree
  8. Notice that the dropped node group is not "Asset Group" from the library but "Local Group"
  9. Right click the "Asset Group" in the Asset Browser and click "Open Blend File"
  10. Modify the "Asset Group" in the original library Blend file, save it, and close the Blender instance opened from the Asset Browser.
  11. Back in the new scene, drag and drop "Asset Group" onto node tree. Notice that it's still not the "Asset Group" but the "Local Group"
  12. Completely close Blender, reopen it, and try the same action again.
  13. Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file
    Result: Once GN node group is added once to the target scene, it's no longer possible to get new updated asset from the asset library if it changes.
    Expected: There is a way to manually remove the link Asset Browser keeps between the scene and imported asset so that user can actually put updated asset into the scene.
**System Information** Operating system: Windows-10-10.0.22631-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 551.76 **Blender Version** Broken: version: 4.1.0, branch: blender-v4.1-release, commit date: 2024-03-25 20:42, hash: `40a5e739e270` Worked: (newest version of Blender that worked as expected) **Short description of error** It is impossible to add updated GN Node Group asset from Asset Library to the scene. Whenever the node group asset is added for the first time, some invisible ID match is used by asset browser to not overwrite existing asset under any circumstances, even after renaming it. So no matter what changes user makes to the original asset in the library, there is no way to bring it to the scene through asset browser. It appears that the "Append (Reuse Data)" mode is broken, because it keeps reusing the data even after datablock name in the target scene was changed. If the name of the datablock was explicitly changed by the user to turn it into new, unique datablock, Asset Browser will still disregard it, and reuse data from the datablock which no longer has same name, **Exact steps for others to reproduce the error** 1. Create a GN Node Group asset in existing asset library, let's call it "Asset Group" for example. 2. In a new scene, drag this asset from Asset Browser into GN node tree 3. Modify this asset in the new scene (change something inside the "Asset Group" node group) 4. Drag and drop the asset again from the Asset Browser 5. Notice the drag-dropped version is not the asset from the Asset Library but the local modified one. 6. Rename the node group to avoid conflict, for example to "Local Group" 7. Drag and drop "Asset Group" from Asset Browser to node tree 8. Notice that the dropped node group is not "Asset Group" from the library but "Local Group" 9. Right click the "Asset Group" in the Asset Browser and click "Open Blend File" 10. Modify the "Asset Group" in the original library Blend file, save it, and close the Blender instance opened from the Asset Browser. 11. Back in the new scene, drag and drop "Asset Group" onto node tree. Notice that it's still not the "Asset Group" but the "Local Group" 12. Completely close Blender, reopen it, and try the same action again. 13. Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file Result: Once GN node group is added once to the target scene, it's no longer possible to get new updated asset from the asset library if it changes. Expected: There is a way to manually remove the link Asset Browser keeps between the scene and imported asset so that user can actually put updated asset into the scene.
Ludvik Koutny added the
Status
Needs Triage
Priority
Normal
Type
Report
labels 2024-04-01 11:15:05 +02:00
Iliya Katushenock added the
Interest
Asset Browser
label 2024-04-06 12:16:56 +02:00

Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file

Can't confirm. I rebot blender and now i am able to get original (updated) asset:
image

> Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file Can't confirm. I rebot blender and now i am able to get original (updated) asset: ![image](/attachments/5e5ee613-d6b9-4499-9c67-af04115f1916)
Author
Contributor

Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file

Can't confirm. I rebot blender and now i am able to get original (updated) asset:
image

You probably missed some step, or this is not reliably reproducible, but it does happen quite often.

> > Notice it's still not the new, modified "Asset Group" from the asset library but the old, outdated, modified "Local Group" from the file > > Can't confirm. I rebot blender and now i am able to get original (updated) asset: > ![image](/attachments/5e5ee613-d6b9-4499-9c67-af04115f1916) You probably missed some step, or this is not reliably reproducible, but it does happen quite often.
Member

Does the behavior change for you if you change the Import Method ?

image

I did notice an inconsistency, just checking with you first if the above makes a difference (it does for me)

Does the behavior change for you if you change the `Import Method` ? ![image](/attachments/157718aa-1d0e-453b-aa1d-572525e8c7cb) I did notice an inconsistency, just checking with you first if the above makes a difference (it does for me)
Philipp Oeser added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2024-04-16 14:46:51 +02:00
Member

poke

poke
Author
Contributor

poke

Sorry, I am in a middle of a job. I will test it as soon as I can. Hopefully before end of this week.

> poke Sorry, I am in a middle of a job. I will test it as soon as I can. Hopefully before end of this week.
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
3 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#120134
No description provided.