Make Single User doesn't work correctly between Linked Scenes #66276

Closed
opened 2019-06-30 13:21:38 +02:00 by mantissa · 5 comments

System Information
Operating system: Linux-4.19.51_1-x86_64-with-glibc2.9 64 Bits
Graphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.14

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-29 20:58, hash: be060c3990
Worked: 2.79b

Short description of error
When using two or more scenes in the same file, the Make Single User command produces unwanted results.
After copying the current scene as a linked scene, hitting Make Single User hides the original object and replaces it with the new one in both scenes.
The mesh data is still linked between the two in both scenes as expected, but the original object is no longer linked to the original scene.
Additionally, moving the new object out of the default collection causes it to disappear from the original scene's outliner entirely.

Exact steps for others to reproduce the error

  • Create new Scene by using the linked copy command
  • Select Cube and hit Make Single User ("Object" tested in this case, others might be bugged too)
  • Move Cube.001 to a new position in Scene.001
  • Go back to original Scene, Cube has been replaced by new scene's Cube.001 and has been moved
  • Additionally, move Cube.001 out of Collection in Scene.001
  • Cube.001 disappears in original Scene
**System Information** Operating system: Linux-4.19.51_1-x86_64-with-glibc2.9 64 Bits Graphics card: TITAN X (Pascal)/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.14 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-06-29 20:58, hash: `be060c3990` Worked: 2.79b **Short description of error** When using two or more scenes in the same file, the Make Single User command produces unwanted results. After copying the current scene as a linked scene, hitting Make Single User hides the original object and replaces it with the new one in both scenes. The mesh data is still linked between the two in both scenes as expected, but the original object is no longer linked to the original scene. Additionally, moving the new object out of the default collection causes it to disappear from the original scene's outliner entirely. **Exact steps for others to reproduce the error** - Create new Scene by using the linked copy command - Select Cube and hit Make Single User ("Object" tested in this case, others might be bugged too) - Move Cube.001 to a new position in Scene.001 - Go back to original Scene, Cube has been replaced by new scene's Cube.001 and has been moved - Additionally, move Cube.001 out of Collection in Scene.001 - Cube.001 disappears in original Scene
Author

Added subscriber: @Mantissa

Added subscriber: @Mantissa

Added subscriber: @Pinus

Added subscriber: @Pinus

Maybe this bug is also responsible for the problem with SaplingTree Addon?
See here: https://developer.blender.org/T66252

According to Cansecos commentary I found two cubes in the Properties (green triangle icon), a 001.cube and a 0 cube.
I only saw and deleted one cube in my scene before, then came the error message from SaplingTree
"cube 001 not in view layer ..."
When clicking on the 0 cube, a cube with boolean operations was displayed (!?)
I do not know how this cube came into the scene, I did not create it, and there was no fake user in the properties panel either.

As I said, that's just a consideration ...

Maybe this bug is also responsible for the problem with SaplingTree Addon? See here: https://developer.blender.org/T66252 According to Cansecos commentary I found two cubes in the Properties (green triangle icon), a 001.cube and a 0 cube. I only saw and deleted one cube in my scene before, then came the error message from SaplingTree "cube 001 not in view layer ..." When clicking on the 0 cube, a cube with boolean operations was displayed (!?) I do not know how this cube came into the scene, I did not create it, and there was no fake user in the properties panel either. As I said, that's just a consideration ...
Bastien Montagne was assigned by Sebastian Parborg 2019-07-01 16:06:35 +02:00

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

that's kind of totally expected, since collections are shared between scenes in this scenario.... Everything you do in one scene is reflected in the other one. No bug here.

that's kind of totally expected, since collections are shared between scenes in this scenario.... Everything you do in one scene is reflected in the other one. No bug here.
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#66276
No description provided.