Creating a linked duplicate of a linked collection, removes all empties on re-load #110744

Closed
opened 2023-08-03 09:39:23 +02:00 by Robert S · 4 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67

Blender Version
Broken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: edc1a09966a7
Worked: (newest version of Blender that worked as expected)

Short description of error
This is related to the UX disaster which is this:

#110717 (comment)

Imo, linking should be restricted to an experimental branch of Blender, as it does not seem ready for production.

Exact steps for others to reproduce the error

  1. Link a collection with a lot of hierarchial objects
  2. Override everything down to the materials (requires several steps?)
  3. Select the top empty in the outliner and choose "select hierarchy"
  4. Hit alt-d to create a linked duplicate and confirm
  5. Hit m to move the entire duplicated hierarchy to a different collection
  6. Unlink the previously linked collection
  7. Save the file and re-load

Result:

All empties are gone from the file, and only a flat list of objects remain
image

Expected:

The duplicated hiearchy should stay intact!
image

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: Quadro RTX 3000 with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.67 **Blender Version** Broken: version: 3.6.1 Release Candidate, branch: blender-v3.6-release, commit date: 2023-07-16 02:43, hash: `edc1a09966a7` Worked: (newest version of Blender that worked as expected) **Short description of error** This is related to the UX disaster which is this: https://projects.blender.org/blender/blender/issues/110717#issuecomment-991171 Imo, linking should be restricted to an experimental branch of Blender, as it does not seem ready for production. **Exact steps for others to reproduce the error** 1. Link a collection with a lot of hierarchial objects 2. Override everything down to the materials (requires several steps?) 3. Select the top empty in the outliner and choose "select hierarchy" 4. Hit alt-d to create a linked duplicate and confirm 5. Hit m to move the entire duplicated hierarchy to a different collection 6. Unlink the previously linked collection 7. Save the file and re-load Result: All empties are gone from the file, and only a flat list of objects remain ![image](/attachments/27a1abc9-6dfc-4369-82f4-29751e2555a2) Expected: The duplicated hiearchy should stay intact! ![image](/attachments/f9ebb2c6-120a-40da-a274-eccf0d9b5a94)
810 KiB
905 KiB
Robert S added the
Type
Report
Priority
Normal
Status
Needs Triage
labels 2023-08-03 09:39:24 +02:00
Author

A workaround is apparently the following (so far):

  1. Link the collection with the "instance collection" option OFF
  2. Select hierarchy and make library override for selected and data (optionally do this again on objects to override materials)
  3. Hit M to move the selected hierarchy to a new collection (this doesn't move it, it links it) 😑
  4. Unlink the previously linked collection

Any other procedure will result in LOSS OF DATA!

Even after doing the above, you need to save and re-load the file (or perhaps clean up unused data-blocks) before you're allowed to begin deleting things in the linked hierarchy...

I know developers don't care about UX, but holy crap working with links feels extremely fragile in Blender!

A workaround is apparently the following (so far): 1. Link the collection with the "instance collection" option OFF 2. Select hierarchy and make library override for selected and data (optionally do this again on objects to override materials) 3. Hit M to move the selected hierarchy to a new collection (this doesn't move it, it links it) 😑 4. Unlink the previously linked collection Any other procedure will result in LOSS OF DATA! Even after doing the above, you need to save and re-load the file (or perhaps clean up unused data-blocks) before you're allowed to begin deleting things in the linked hierarchy... I know developers don't care about UX, but holy crap working with links feels extremely [fragile ](https://projects.blender.org/blender/blender/issues/110742)in Blender!

Could you provide a simplified file where we can confirm the problem and forward it to the developers?

It's not clear to me what the hierarchy and arrangement of Empty and Non-Empties objects should be in the file to be linked.

Could you provide a simplified file where we can confirm the problem and forward it to the developers? It's not clear to me what the hierarchy and arrangement of Empty and Non-Empties objects should be in the file to be linked.
Germano Cavalcante added
Status
Needs Information from User
and removed
Status
Needs Triage
labels 2023-08-03 19:33:18 +02:00

Thanks for the report, but without a .blend file, or clearer steps it's hard to know where to start trying to replicate the problem here.

Unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem.

Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

Thanks for the report, but without a .blend file, or clearer steps it's hard to know where to start trying to replicate the problem here. Unfortunately the scenario described is too time consuming for us to track down, we require the bug reporter to narrow down the problem. Normally .blend files can be simplified by removing most objects and disabling settings, until the problem reveals itself more clearly.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed. Thanks again for the report. If the problem persists please open a new report with the required information.
Blender Bot added
Status
Archived
and removed
Status
Needs Information from User
labels 2023-08-23 22:48:38 +02:00
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
2 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#110744
No description provided.