Additional unwanted objects being created when asset browser asset is used #107180
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
FBX
Interest
Freestyle
Interest
Geometry Nodes
Interest
glTF
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 & 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
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
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
Asset System
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#107180
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
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.22000-SP0 64 Bits
Graphics card: NVIDIA RTX A4500/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.15
Blender Version
Broken: version: 3.5.0, branch: blender-v3.5-release, commit date: 2023-03-29 02:56, hash:
1be25cfff18bWorked: (newest version of Blender that worked as expected)
Short description of error
Additional duplicate (unwanted) objects being created when using assets from the asset browser.
Exact steps for others to reproduce the error
I haven't managed to consistently reproduce how I get this issue to happen. However, I have attached files which are guaranteed to demonstrate it.
The oxford-straps-demo.blend file contains the source meshes which are placed in a collection and marked as asset called "Source Asset"
The test-asset.blend file contains the "Source Asset" dropped in as Linked then Library Overridden. That itself is then marked again as an asset called "Test Asset". (This is my workflow - I would do this, then add materials at this stage).
Open a new blend file and drop in the "Test Asset" (with Append). You will see the appended asset plus two other unwanted objects which are duplicates of the objects contained within the sealed asset.
I have to delete these every time the asset is used.
Hi, thanks for the report. Are you using Append from File menu?
Or did you move these files to asset library and using the
Appendimport type from asset browser?Hi Pratik,
That’s correct. I put these files in an asset browser location and used only the asset browser to make use of the object (Link in the first instance and then Append in the second).
The purpose of this strange process is to reuse the same object (mesh) but with different textures.
Hope that makes sense.
Note that this normally works flawlessly. It's only in this particular case that the strange additional objects are being created. I can't figure out what is different in this case. I did manage to reproduce it with a test file and test objects but I can't seem to repeat what I did to identify the exact issue. I have a feeling it is something to do with the objects within the original asset having parent->child->grandchild relationships (but maybe it's not that at all!)
Thanks,
S.
Behavior indeed seems strange to me.
It looks like it brings in objects that belong in the hierarchy of a parent of an object specified as an object in a curve modifier.
So if I look at the override hierarchy of test-asset.blend :
I see a lot of duplicates (e.g. of
ox-short-strap-aligator-assetwhich is selected in the screenshot).Why do we see it duplicated so often?
Can only assume this is because it is the parent of an object specified in a curve modifier.
Now everything under that parent gets duplicated multiple times.
While this may still be expected behavior, when appending that whole stuff into a new file seems to somehow get confused and cant determine what has already been appended (and thus would not have be been pulled in again)
This is the original
oxford-straps-demo.blendfrom which the overrides were made:I am not sure if I can come up with a simpler file (I could try though).
@mont29 : does this ring a bell?
@lichtwerk #107111 ?
Might be related, replied there
@lichtwerk I do not understand your issue with the liboverride Hierarchy view... If an ID is used by several other IDs, it will appear under all of its users' hierarchies, that's the whole point of this view.
As for original report, I believe it's a combination of 'same thing as in #107111' (i.e. dependencies are brought in together with the linked/appended data), AND the old thing that we do not allow local objects that are not instantiated in some viewlayer (as a reminder, liboverrides data-blocks do bring in their linked reference data too).