Disabling collection in the outliner does not entirely disable all the calculations connected with that collection #99572
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#99572
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: Windows-10-10.0.22000-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1660 Ti with Max-Q Design/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 512.78
Blender Version
Broken: version: 3.2.1, branch: master, commit date: 2022-07-05 15:44, hash:
a2d59b2dac
Worked: 2.79
Short description of error
If you have a collection with some armature (say "Character" collection) and some other collection that has objects linked to that armature (say "Character's Clothes") and there are some heavy models there (lots of modifiers, faces, etc.), then the armature performance would be abysmal until you completely delete that collection from the Scene.
Exact steps for others to reproduce the error
Based on an attached .blend file.
1) Move any armature's bones with "Sides" collection ENABLED
2) Observe lag
3) Disable"Sides" collection
4) Move any armature's bones
5) Observe lag
6) Delete Hierarchy "Sides" collection
7) Move any armature's bones
8) There would be no lag
Which means that after you disable collection in the Outliner, the calculations that are connected to that collection's objects are not entirely disabled like it was with Layers in 2.79. So, if the objects in the second collection are really compute-intensive, the whole scene is going to lag.
I have attached a blend file and a video of this happening.
lag_example.blend
blender_vp_lag.mp4
Added subscriber: @LilyStilson
Added subscriber: @rocketman
IIRC, disabling collections in the Outliner (or layers in 2.79 for that matter) is meant to disable their drawing/rendering; not their logic. Objects can be used as parents, targets, etc for objects in completely separate collections, and disabling the collection does not disable the relationship.
But then what's the point in having that checkbox if you can just toggle visibility in viewport?
Good question. That checkbox disables rendering/drawing the collection on a per-view-layer basis, that is, you can enable the collection for one view layer and disable it on another for compositing purposes. I'm not sure of the extent to which disabling a collection disables simulation and other potentially expensive calculations; the only reliable method I know is to put that stuff in a separate scene entirely.
Here's a guide I made which covers the implicit rules for each toggle in the Outliner:
If you think this image is confusing, I agree. The workflow needs an overhaul. Developers, please let me know if you're fielding suggestions or mockups
It's actually not and is quite useful :)
But yeah... That problem with completely disabling collections is seriously bothering me right now as I can't just continue working on my project due to character having too much different clothing. For now, I can only separate all the clothes to a different
.blend
file and then re-import them for a final render.Added subscriber: @OmarEmaraDev
Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'
I can confirm the performance impact, unsure if it is expected for some reason.
Might be similar to #73199, #85614, and others.
Added subscriber: @exverxes
I recently had a problem, where I had a large scene with multiple animated characters. I to got to the point where if I wanted to play animation it was going at 3 fps with all collections disabled (so empty viewport). Even if I wanted to show only a single character to check how the animation looks it was not possible to do so. What Sam wrote is a valid concern, but at the same time you can set whole collection to not be displayed and rendered and will get the behaviour where calculations are being done, while objects are not displayed. When I'm disabling a collection I expect it to have no impact on the scene, not only to be not rendered. Please solve this.