Linking the instance of a collection crashes Blender #61683
Labels
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#61683
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: elementaryOS 0.4.1
Graphics card: GTX 1080
Blender Version
Broken: 2.80,
aed631fa47
Worked: 2.79b
Short description of error
I have two blendfiles, Scene_A and Scene B.
In Scene_A I added a monkey and moved it to a new collection, called "Suzanne".
Then I added a collection instance of Suzanne to the scene, called "suzanne_instance".
Then I saved the file.
Now, in a new file, I try to link in the object "suzanne_instance" -> Blender crashes.
Exact steps for others to reproduce the error
Download Scene_A: scene_A.blend
Download Scene_B: scene_B.blend
If you open Scene_B and try to link in the object "suzanne_instance" from Scene_A Blender crashes.
In theory you could also just use the default startup file instead of Scene_B.
If I try the same but instead of a monkey I try it with the default cube I do not get a crash. I assume it is because the mesh "Cube" is already present in the default scene, hence it is present in SceneB, and so Blender finds a mesh with the same name it tries to instance, is happy and does not crash.
Added subscriber: @sebastian_k
Added subscriber: @WilliamReynish
Are you even supposed to be able to instance an instance?
Why wouldn't I be? It works just fine in 2.79.
Usecase:
Usually I have my main scene with main geometry for the building etc., which instances objects like furniture and props from single files.
Now I want to have a second file with a variation of that scene, but some props should be linked from the first scene to the second scene, so that those objects are always in sync and share the same position, rotation etc. . It should actually be not a big deal to do that.
Added subscriber: @ZedDB
Backtrace:
This issue was referenced by
cba447966e
Changed status from 'Open' to: 'Resolved'