restoring orphan data #66086

Closed
opened 2019-06-24 22:38:14 +02:00 by scott · 3 comments

System Information
Operating system: linux 64-bit
Graphics card: nvidia geforce gtx-650

Blender Version
Broken: blender-2.80-953419c641a7-linux-glibc224-x86_64

Description

It is not documented afaict, perhaps it should be, but suppose a user does the following, it becomes very difficult to tell in how to restore their deleted object/s.

The issue is that it is difficult to "restore" orphan data.

The feature Ctrl-G to add a new Collection (Blender 2.8) prevents it from appearing on the Scene as expected, the issue arises later as a consequence of using Ctrl-G.

Instructions:

Take a new blender workspace, with its default cube selected and apply Ctl-G, and name its additional collection called 'Collection 2'.

The cube is now a member of two collections, 'Collection' and 'Collection 2', and this can be verified in its Object property-panel(orange square) under 'Collections'.

The Outliner (View-Layer) presents just one collection for the cube.

The Outliner orphan-data view presents 'Collection 2'.

Despite confusion, (I'm a bit new to blender), supposedly this is transitioning-development and this may change in the future so that 'Collection 2' at this point would not appear in the orphan-data view.

The problem arises now when a user performs the following::

In the object property panel (orange quare) for the cube, the removing of 'Collection' from the list now causes the cube to disappear from the scene.

The cube now appears under 'Collection 2' in the Outliner's orphan data view.

So here is the problem:

How does one "restore" 'Collection 2'/cube so that that the cube object can be placed(undelete) back onto the Scene?

The only way I could figure out how to do this after a long time of searching online, and checking any documentation on this was to create two Outliner views.

Have one Outliner view in 'View Layer', and have another Outliner view in 'Orphan data view',

Now drag and drop the 'Collection 2'(containing the cube -- from Orphan Data view), into the Outliner 'View Layer' with the heading 'Collections', and the object is now restored back fully into the Scene.

Perhaps there should be a new feature with a 'warning' or choice-box before blender sends the cube missing from the scene offering to set 'Collection 2' to the scene.

I don't see a bug, but I do see a lack of documentation on this, and believe reporting this might help another user or give an idea to development for improving this difficult task.

It's not documented and most users would not be able to figure out on how to do this as one would have to use two Outliners in order to properly restore the missing object. It is possible to use a blender file link and still access the marked 'fake user' orphan data from a new workspace(and that's another way to restore missing orphan data) but that is not the case i'm referring to, nor should it be the case..

Please improve this area or at least have this documented somewhere so that this problem can be prevented as it is extremely difficult to restore things this way.

thanks

**System Information** Operating system: linux 64-bit Graphics card: nvidia geforce gtx-650 **Blender Version** Broken: blender-2.80-953419c641a7-linux-glibc224-x86_64 **Description** It is not documented afaict, perhaps it should be, but suppose a user does the following, it becomes very difficult to tell in how to restore their deleted object/s. The issue is that it is difficult to "restore" orphan data. The feature Ctrl-G to add a new Collection (Blender 2.8) prevents it from appearing on the Scene as expected, the issue arises later as a consequence of using Ctrl-G. Instructions: Take a new blender workspace, with its default cube selected and apply Ctl-G, and name its additional collection called 'Collection 2'. The cube is now a member of two collections, 'Collection' and 'Collection 2', and this can be verified in its Object property-panel(orange square) under 'Collections'. The Outliner (View-Layer) presents just one collection for the cube. The Outliner orphan-data view presents 'Collection 2'. Despite confusion, (I'm a bit new to blender), supposedly this is transitioning-development and this may change in the future so that 'Collection 2' at this point would not appear in the orphan-data view. The problem arises now when a user performs the following:: In the object property panel (orange quare) for the cube, the removing of 'Collection' from the list now causes the cube to disappear from the scene. The cube now appears under 'Collection 2' in the Outliner's orphan data view. So here is the problem: How does one "restore" 'Collection 2'/cube so that that the cube object can be placed(undelete) back onto the Scene? The only way I could figure out how to do this after a long time of searching online, and checking any documentation on this was to create two Outliner views. Have one Outliner view in 'View Layer', and have another Outliner view in 'Orphan data view', Now drag and drop the 'Collection 2'(containing the cube -- from Orphan Data view), into the Outliner 'View Layer' with the heading 'Collections', and the object is now restored back fully into the Scene. Perhaps there should be a new feature with a 'warning' or choice-box before blender sends the cube missing from the scene offering to set 'Collection 2' to the scene. I don't see a bug, but I do see a lack of documentation on this, and believe reporting this might help another user or give an idea to development for improving this difficult task. It's not documented and most users would not be able to figure out on how to do this as one would have to use two Outliners in order to properly restore the missing object. It is possible to use a blender file link and still access the marked 'fake user' orphan data from a new workspace(and that's another way to restore missing orphan data) but that is not the case i'm referring to, nor should it be the case.. Please improve this area or at least have this documented somewhere so that this problem can be prevented as it is extremely difficult to restore things this way. thanks
Author

Added subscriber: @swtlkmtl

Added subscriber: @swtlkmtl

Closed as duplicate of #53662

Closed as duplicate of #53662

Added subscriber: @Emi_Martinez

Added subscriber: @Emi_Martinez
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#66086
No description provided.