Page MenuHome

Full Copy Scene produce Orphan Data objects
Closed, ResolvedPublicBUG

Description

System Information
Operating system: Linux-4.15.0-70-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce 610M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 390.116

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3
Worked: (optional)

Short description of error


i was working on some big animation multiplate takes but because of NDA i can't uploud the full file however after deleateing all stuff from file.. and just adding cube and makeing full copy of scene with single cube the issiue happens. The file is broken.. a fresh new file works fine. i am not sure what made this file to sudenly not work correctly.

Exact steps for others to reproduce the error
make FULL COPY of scene. and as u will see all items in it will have user count 0 and will apear as ophran data.

EDIT//
I it seams that the automatic Scene collection that is created on each new scene.. is loosing links.

Event Timeline

Just made full copy of the default scene in 2.81. No new orphan data appeared.

@Stanislav Blinov (radcapricorn) yes the default works fine. try on the file i have attached. read description

SOLVER: U have to make new collection and put all objects in to it. before doing full copy of TAKE_2. Is this kind of a bug? or just strange design workflow case.

Yes, thanks for the clarification. Looks like objects in 'Scene Collection' indeed lose both links. 2.80 seems to behave correctly.

Jacques Lucke (JacquesLucke) changed the task status from Needs Triage to Confirmed.Jan 8 2020, 1:25 PM
Jacques Lucke (JacquesLucke) triaged this task as High priority.

Steps to reproduce a crash:

  1. Open file.
  2. Do a full copy of the scene.
  3. Delete the cube in the new scene.

This crashes, because the cube has zero users, while the cube in the old scene now has two users.

Bastien Montagne (mont29) changed the subtype of this task from "Report" to "Bug".

that’s yet another glorious demonstration of how much of a pain those 'IDs that are not really IDs' (the master collection here) are in current Blender… will check on how to fix that bug…