Unlink objects/collections also disappeared in different scene #65495

Closed
opened 2019-06-04 18:26:33 +02:00 by tokenyet · 7 comments

System Information
Operating system: Win 10 1903
Graphics card: GTX 1660

Blender Version
Broken: 2.80, 87207df7222a
Worked: Not sure, before Feburary or March

Short description of error
Deleting an object shared between scenes, meant unlinking it from that scene (It is still existed another scenes). With the new version deleting it means losing it from all scenes.
Am I missing something? How can I just unlink the object
Related Article

Exact steps for others to reproduce the error

  1. Open default blender.
  2. Add new Scene (with Linked Copy).
  3. Unlink a cube
  4. Switch to another scene, and It should be also unlinked. (Only see in OrphanData)

I'm wondering If this behavior is normal or I just miss something else?

**System Information** Operating system: Win 10 1903 Graphics card: GTX 1660 **Blender Version** Broken: 2.80, 87207df7222a Worked: Not sure, before Feburary or March **Short description of error** Deleting an object shared between scenes, meant unlinking it from that scene (It is still existed another scenes). With the new version deleting it means losing it from all scenes. Am I missing something? How can I just unlink the object [Related Article](https://blenderartists.org/t/blender-2-8-unlink-object-from-scene/1146034) **Exact steps for others to reproduce the error** 1. Open default blender. 2. Add new Scene (with Linked Copy). 3. Unlink a cube 4. Switch to another scene, and It should be also unlinked. (Only see in OrphanData) I'm wondering If this behavior is normal or I just miss something else?
Author

Added subscriber: @tokenyete

Added subscriber: @tokenyete
tokenyet changed title from Unlink objects/collections in different scene is broken. to Unlink objects/collections also disappeared in different scene 2019-06-04 18:29:43 +02:00
Author

I researched for whole day and finally found out that this feature is really unintuitive to use.

First, Unlink is only working on collections, but sometimes not. How could this happen?
If you add a collection(a) in a LINKED COLLECTION(b) that linked by before scenes (shallow copy), then change back to another scene and unlinked It(a), and the unexpectable tragedy happened! (a) gone for All scenes, what I expected was just unlink from certain scene.

This seems to be logical on programming, but there is NO tag (remark) on Collection that showed as LINKED, so If you had a bunch of scenes and collections mixing together (and use shallow copy), the unlink method is marked as useless to use.

I thought this feature should mark as, ex. Collection Weapon(L) or Collection Weapon(L-SceneOne). I prefer the last one, because If there is just L, you have no idea, where It derived from.

Or this is unexpected behavior or Bug, don't care what I'm explaining above :(

By the way, Objects unlink in difference scene is no possible to use since the Collection is linked and the algorithm is only binding Collection. For now, Unlink an object means throw It in to OrphanData (Or call It the second Delete button).

I researched for whole day and finally found out that this feature is really unintuitive to use. First, Unlink is only working on collections, but sometimes not. How could this happen? **If you add a collection(a) in a LINKED COLLECTION(b) that linked by before scenes (shallow copy), then change back to another scene and unlinked It(a)**, and the unexpectable tragedy happened! (a) gone for All scenes, what I expected was just unlink from certain scene. This seems to be logical on programming, but there is NO tag (remark) on Collection that showed as LINKED, so If you had a bunch of scenes and collections mixing together (and use shallow copy), the unlink method is marked as useless to use. I thought this feature should mark as, ex. Collection Weapon(L) or Collection Weapon(L-SceneOne). I prefer the last one, because If there is just **L**, you have no idea, where It derived from. Or this is unexpected behavior or Bug, don't care what I'm explaining above :( By the way, Objects unlink in difference scene is no possible to use since the Collection is linked and the algorithm is only binding Collection. For now, Unlink an object means throw It in to OrphanData (Or call It *the second Delete button*).

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Brecht Van Lommel self-assigned this 2019-06-06 06:28:53 +02:00

This is how it was designed. While docs are still being worked on and there may be ways to make it more clear, I don't think there is a bug to fix here.

This is how it was designed. While docs are still being worked on and there may be ways to make it more clear, I don't think there is a bug to fix here.

Added subscriber: @AdamPreisler

Added subscriber: @AdamPreisler

I am afraid this is one of those "This isn't a bug" while in reality it's a massive and scary Scarabeus. It's the sort of bug that acts like it isn't one from the technological viewpoint but from the user perspective you delete your stuff.

There should probably also be Make This Object Appear only in the current Scene under the menu:

I think there should be a better way to manage which scenes link which objects and the "Unlink" in the Outliner should only unlink that object from that specific scene.
image.png
Right now, as tokenyet states very correctly, the Unlink simply means Delete.
FOR ALL SCENES!

Honestly why would we want this functionality in the way it's designed now? What if I want multiple scenes to share certain data but some objects would be only unique for their specific scene.
Now if I add such unique objects into a scene, they appear everywhere.
Likewise if I delete specific objects from some scenes, they disappear everywhere.

I have to say this is borderline useless way to go about it.

I am sure that technologically it's amazing and awesome but there are some behaviors that are quite unexpected and definitely should be more polished. After all, the foundations are there.

Extra work to get this into a more usable state would be very welcome.

I am afraid this is one of those "This isn't a bug" while in reality it's a massive and scary Scarabeus. It's the sort of bug that acts like it isn't one from the technological viewpoint but from the user perspective you delete your stuff. There should probably also be **Make This Object Appear only in the current Scene** under the menu: I think there should be a better way to manage which scenes link which objects and the "Unlink" in the Outliner should only unlink that object from that specific scene. ![image.png](https://archive.blender.org/developer/F7869251/image.png) Right now, as tokenyet states very correctly, the Unlink simply means Delete. **FOR ALL SCENES!** Honestly why would we want this functionality in the way it's designed now? What if I want multiple scenes to share certain data but some objects would be only unique for their specific scene. Now if I add such unique objects into a scene, they appear everywhere. Likewise if I delete specific objects from some scenes, they disappear everywhere. I have to say this is borderline useless way to go about it. **I am sure that technologically it's amazing and awesome but there are some behaviors that are quite unexpected and definitely should be more polished. After all, the foundations are there.** Extra work to get this into a more usable state would be very welcome.
Sign in to join this conversation.
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
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#65495
No description provided.