Excluding and then Including a collection in the Outliner resets object visibility #65730

Closed
opened 4 years ago by stevewarner · 7 comments

System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71

Blender Version
Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-09 21:43, hash: 030c7df19d
Worked: (optional)

Short description of error
If you click the checkbox to the left of a collection to disable/exclude it, then you click the checkbox to re-enable it, all of the hidden objects in the collection will become unhidden. This shouldn't be the case. If you disable a collection, when you re-enable it, it should be added in with the same object visibility as it had when it was disabled.

Exact steps for others to reproduce the error
Start a new scene. Duplicate the default cube 3 times. Put all three cubes into a new collection.
Set the visibility of one of the cubes to hidden by turning off the eyeball icon in the outliner.
Click the checkbox next to the collection to disable/exclude it.
Click the checkbox next to the collection to include it. The hidden object will no longer be hidden.

**System Information** Operating system: Windows-10-10.0.17134 64 Bits Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.71 **Blender Version** Broken: version: 2.80 (sub 74), branch: blender2.7, commit date: 2019-06-09 21:43, hash: `030c7df19d` Worked: (optional) **Short description of error** If you click the checkbox to the left of a collection to disable/exclude it, then you click the checkbox to re-enable it, all of the hidden objects in the collection will become unhidden. This shouldn't be the case. If you disable a collection, when you re-enable it, it should be added in with the same object visibility as it had when it was disabled. **Exact steps for others to reproduce the error** Start a new scene. Duplicate the default cube 3 times. Put all three cubes into a new collection. Set the visibility of one of the cubes to hidden by turning off the eyeball icon in the outliner. Click the checkbox next to the collection to disable/exclude it. Click the checkbox next to the collection to include it. The hidden object will no longer be hidden.
Poster

Added subscriber: @stevewarner

Added subscriber: @stevewarner
dfelinto was assigned by ZedDB 4 years ago
ZedDB commented 4 years ago
Collaborator

Added subscriber: @ZedDB

Added subscriber: @ZedDB
ZedDB commented 4 years ago
Collaborator

You can just open the default cube scene and toggle visibility of the cube and then uncheck and recheck the collection to reproduce this.

You can just open the default cube scene and toggle visibility of the cube and then uncheck and recheck the collection to reproduce this.
Owner

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
dfelinto closed this issue 4 years ago
Owner

This is by design.
The moment you exclude a collection from your view layer you are letting of of the bases as well (the information storing the objects visibility for that view layer).
If the object is also linked in a different collection its visibility state will be preserved.

This is by design. The moment you exclude a collection from your view layer you are letting of of the bases as well (the information storing the objects visibility for that view layer). If the object is also linked in a different collection its visibility state will be preserved.
1D_Inc commented 2 years ago

Added subscriber: @1D_Inc

Added subscriber: @1D_Inc
1D_Inc commented 2 years ago

In #65730#706896, @dfelinto wrote:
This is by design.
The moment you exclude a collection from your view layer you are letting of of the bases as well (the information storing the objects visibility for that view layer).
If the object is also linked in a different collection its visibility state will be preserved.

What is the point of such a design?
If you hide objects, it is supposed that they will remain hidden until you will not perform unhiding operations via visibility.

Hiding objects mean "I don't want to see that objects until I will not unhide them" - not via excluding, not via renderabilty, not via indirect only - unhiding only via visibility.
Unhiding caused by non-unhiding operations is a design flaw, causing workflow issues, and should be fixed as similar inconsistency was fixed .

> In #65730#706896, @dfelinto wrote: > This is by design. > The moment you exclude a collection from your view layer you are letting of of the bases as well (the information storing the objects visibility for that view layer). > If the object is also linked in a different collection its visibility state will be preserved. What is the point of such a design? If you hide objects, it is supposed that they will remain hidden until you will not perform unhiding operations via visibility. Hiding objects mean "I don't want to see that objects until I will not unhide them" - not via excluding, not via renderabilty, not via indirect only - unhiding only via visibility. Unhiding caused by non-unhiding operations is a design flaw, causing workflow issues, and should be fixed as [similar inconsistency was fixed ](https://developer.blender.org/T65730).
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/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
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/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
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
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
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 & Devices
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 Information 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#65730
Loading…
There is no content yet.