Regression: Append/Link of Object can create extra Scene #99166

Closed
opened 2022-06-25 15:35:39 +02:00 by Sybren A. Stüvel · 13 comments

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40

Blender Version
Broken: version: 3.0.1, 3.1.2, 3.2.1 releases, and 3.3.0 Alpha, branch: master, commit date: 2022-06-24 21:39, hash: 12bde317f4
Worked: 2.93.9

Caused by 3be5ce4aad

Short description of error
Appending the one object Bottom from the attached file doesn't add it to the current Scene. Instead, it creates Scene.001 that contains the appended object.

Exact steps for others to reproduce the error

  • Open a factory-default blender.
  • Erase all the objects from the scene, just to have a clean slate.
  • Append the Bottom object from the attached file.

Expected behaviour: the Bottom object appears in the scene.
Observed behaviour: a new scene Scene.001 was created, which contains the Bottom object.

bugreport-append-from-this.blend

**System Information** Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 516.40 **Blender Version** Broken: version: 3.0.1, 3.1.2, 3.2.1 releases, and 3.3.0 Alpha, branch: master, commit date: 2022-06-24 21:39, hash: `12bde317f4` Worked: 2.93.9 Caused by 3be5ce4aad **Short description of error** Appending the one object `Bottom` from the attached file doesn't add it to the current Scene. Instead, it creates `Scene.001` that contains the appended object. **Exact steps for others to reproduce the error** - Open a factory-default blender. - Erase all the objects from the scene, just to have a clean slate. - Append the `Bottom` object from the attached file. **Expected behaviour:** the `Bottom` object appears in the scene. **Observed behaviour:** a new scene `Scene.001` was created, which contains the `Bottom` object. [bugreport-append-from-this.blend](https://archive.blender.org/developer/F13229110/bugreport-append-from-this.blend)
Author
Member

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

Added subscriber: @antoniov

Added subscriber: @antoniov

I can confirm the bug on Windows in 3.3 version.

I can confirm the bug on Windows in 3.3 version.
Antonio Vazquez changed title from Append of Object can create extra Scene to Append/Link of Object can create extra Scene 2022-06-25 15:43:25 +02:00
Member

Added subscriber: @EAW

Added subscriber: @EAW
Member

Changed status from 'Needs Triage' to: 'Confirmed'

Changed status from 'Needs Triage' to: 'Confirmed'
Member

In #99166#1380239, @antoniov wrote:
I can confirm the bug on Windows in 3.3 version.

I’ll set this to confirmed then.

> In #99166#1380239, @antoniov wrote: > I can confirm the bug on Windows in 3.3 version. I’ll set this to confirmed then.
Member

Added subscribers: @mont29, @lichtwerk

Added subscribers: @mont29, @lichtwerk
Member

Caused by 3be5ce4aad

CC @mont29

Caused by 3be5ce4aad CC @mont29
Philipp Oeser changed title from Append/Link of Object can create extra Scene to Regression: Append/Link of Object can create extra Scene 2022-06-26 15:36:21 +02:00

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'

Weirdly enough, this is actually expected behavior, since your object has a driver (in its Solidify modifier) that uses the Scene ID of the 'library' file. So linking/appending the object also brings in the scene from that file, and since that object is therefore already instantiated in said scene, it is not added to the current scene. You can of course always add it to the current scene manually...

Weirdly enough, this is actually expected behavior, since your object has a driver (in its Solidify modifier) that uses the Scene ID of the 'library' file. So linking/appending the object also brings in the scene from that file, and since that object is therefore already instantiated in said scene, it is not added to the current scene. You can of course always add it to the current scene manually...

@lichtwerk btw, we only systematically consider regressions as high prio if they are from previous version, not when they have been around for over an year. ;)

@lichtwerk btw, we only systematically consider regressions as high prio if they are from previous version, not when they have been around for over an year. ;)
Member

In #99166#1382841, @mont29 wrote:
@lichtwerk btw, we only systematically consider regressions as high prio if they are from previous version, not when they have been around for over an year. ;)

For now, I was considering everything "post-2.93" with a "seems important" feel to it a regression in that sense (high prio), commit is "only" 9 months old btw..
https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook

High - Most crashes and recent regressions.

Brings up the question what is meant by "recent" here, but if there is consensus that "recent" is only meant to say "since previous version", we should change the playbook (to make this more clear).

Thx clarifying the case/issue here btw. makes sense now.

> In #99166#1382841, @mont29 wrote: > @lichtwerk btw, we only systematically consider regressions as high prio if they are from previous version, not when they have been around for over an year. ;) For now, I was considering everything "post-2.93" with a "seems important" feel to it a regression in that sense (high prio), commit is "only" 9 months old btw.. https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook > High - Most crashes and recent regressions. Brings up the question what is meant by "recent" here, but if there is consensus that "recent" is only meant to say "since previous version", we should change the playbook (to make this more clear). Thx clarifying the case/issue here btw. makes sense now.
Author
Member

In #99166#1382837, @mont29 wrote:
Weirdly enough, this is actually expected behavior, since your object has a driver (in its Solidify modifier) that uses the Scene ID of the 'library' file. So linking/appending the object also brings in the scene from that file, and since that object is therefore already instantiated in said scene, it is not added to the current scene. You can of course always add it to the current scene manually...

That is rather unexpected indeed, since I append only the object -- that is my focus. I think this should at least cause some warning so that users at least know where to look.

> In #99166#1382837, @mont29 wrote: > Weirdly enough, this is actually expected behavior, since your object has a driver (in its Solidify modifier) that uses the Scene ID of the 'library' file. So linking/appending the object also brings in the scene from that file, and since that object is therefore already instantiated in said scene, it is not added to the current scene. You can of course always add it to the current scene manually... That is rather unexpected indeed, since I append only the object -- that is my focus. I think this should at least cause some warning so that users at least know where to look.
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
5 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#99166
No description provided.