Page MenuHome

Unlink objects/collections also disappeared in different scene
Closed, InvalidPublic


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?

Event Timeline

tokenyet (tokenyete) renamed this task from Unlink objects/collections in different scene is broken. to Unlink objects/collections also disappeared in different scene.Jun 4 2019, 6:29 PM
tokenyet (tokenyete) added a comment.EditedJun 5 2019, 8:35 AM

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

Brecht Van Lommel (brecht) changed the task status from Unknown Status to Unknown Status.Jun 6 2019, 6:28 AM
Brecht Van Lommel (brecht) claimed this task.

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.

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.

Right now, as tokenyet states very correctly, the Unlink simply means Delete.

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.