Page MenuHome

Excluding and then Including a collection in the Outliner resets object visibility
Closed, InvalidPublic

Description

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: rB030c7df19da9
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.

Event Timeline

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.

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

Dalai Felinto (dfelinto) changed the task status from Unknown Status to Invalid.Jun 25 2019, 7:34 PM

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.

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.