Disabling/enabling in viewport a sub collection doesn't make the instances of the collection disabled/enabled unless you save and re-open the file #76279

New Issue

Manda Rajoelisolo · 2020-04-30T22:18:01+02:00

Manda Rajoelisolo commented

2020-04-30 22:18:01 +02:00

System Information
Operating system: Windows 10 Pro 64-bit (10.0, Build 18363)
Graphics card: NVIDIA GeForce 920M (Laptop)

Blender Version
Broken: v2.83.13 Beta, 2020-04-21

Short description of error
If you disable/enable in viewport a sub collection of Collection then the instances of the parent collection "Collection" is not disabled/enabled in viewport unless you save and re-open the file.

Wanted result
The wanted result is exactly like when you save and re-open the file, because for example if you enable/disable the cube which is child of child of Collection, then the instance of cube is enable/disabled. And just like that, SubCollection is child of Collection and if it's enable/disabled then the instance should be enabled/disabled too.

Exact steps for others to reproduce the error

SubCollection_ViewportEnableDisable_refresh_bug.blend

Open the provided file.
Disable in viewport the collection named "SubCollection" to unreveal it in viewport. Now the two collection instances "Instance of 'Collection' (1) & (2)" are not hidden.
Save the file.
Press Ctrl+N and click General.
Reopen the same file. Now the two collection instances before are hidden, but before they were not hidden, it's a bug about refreshing.
Enable in viewport the collection named "SubCollection" to reveal it in viewport. Now the two collection instances "Instance of 'Collection' (1) & (2)" are not shown.
Save the file.
Press Ctrl+N and click General.
Reopen the same file. Now the two collection instances before are shown, but before they were not shown, it's a bug about refreshing.

Steps for others to explain the logic of the viewport visibility of Collection and Collection Instance, this is not a bug, it's a useful feature that you should keep

Don't forget to enable the "SubCollection" if you didn't do it yet, you've already save and re-open the file.
Disable in viewport the collection named "Collection" to unreveal it (not SubCollection). Now the two collection instances "Instance of 'SubCollection' (1) & (2)" are not hidden. Now Enable back the "Collection", the enablement of the 2 collection instances "Instance of 'SubCollection' (1) & (2)" don't depend on the viewport enablement of the collection named "Collection".

Description of the last steps
It's very useful when you build a model in a .blend file at the origin (0, 0, 0), and its collection name is "MODEL", and you want to place a collection instance of it at other location (not origin), and you want to disable the model at the origin by disabling the parent collection of the collection named "MODEL", and you want to keep enabled (visible) the collection instances.

People will adapt the non-logic bug but they will see weird things
This is a big problem because if people don't know the bug then they think that it's the logic of viewport enablement of collection instances, and all their projects depend on that, but once they save and close and then re-open the file, they will see weird things.

**System Information** Operating system: Windows 10 Pro 64-bit (10.0, Build 18363) Graphics card: NVIDIA GeForce 920M (Laptop) **Blender Version** Broken: v2.83.13 Beta, 2020-04-21 **Short description of error** If you disable/enable in viewport a sub collection of Collection then the instances of the parent collection "Collection" is not disabled/enabled in viewport unless you save and re-open the file. **Wanted result** The wanted result is exactly like when you save and re-open the file, because for example if you enable/disable the cube which is child of child of Collection, then the instance of cube is enable/disabled. And just like that, SubCollection is child of Collection and if it's enable/disabled then the instance should be enabled/disabled too. **Exact steps for others to reproduce the error** ![SubCollection_ViewportEnableDisable_refresh_bug.jpg](https://archive.blender.org/developer/F8505369/SubCollection_ViewportEnableDisable_refresh_bug.jpg) [SubCollection_ViewportEnableDisable_refresh_bug.blend](https://archive.blender.org/developer/F8505348/SubCollection_ViewportEnableDisable_refresh_bug.blend) 1. Open the provided file. 2. Disable in viewport the collection named "**SubCollection**" to unreveal it in viewport. Now the two collection instances "Instance of '**Collection**' (1) & (2)" are not hidden. 3. Save the file. 4. Press Ctrl+N and click General. 5. Reopen the same file. Now the two collection instances before are hidden, but before they were not hidden, it's a bug about refreshing. 6. Enable in viewport the collection named "**SubCollection**" to reveal it in viewport. Now the two collection instances "Instance of '**Collection**' (1) & (2)" are not shown. 7. Save the file. 8. Press Ctrl+N and click General. 9. Reopen the same file. Now the two collection instances before are shown, but before they were not shown, it's a bug about refreshing. **Steps for others to explain the logic of the viewport visibility of Collection and Collection Instance, this is not a bug, it's a useful feature that you should keep** - Don't forget to enable the "SubCollection" if you didn't do it yet, you've already save and re-open the file. - Disable in viewport the collection named "**Collection**" to unreveal it (not SubCollection). Now the two collection instances "Instance of '**SubCollection**' (1) & (2)" are not hidden. Now Enable back the "Collection", the enablement of the 2 collection instances "Instance of 'SubCollection' (1) & (2)" don't depend on the viewport enablement of the collection named "Collection". **Description of the last steps** It's very useful when you build a model in a .blend file at the origin (0, 0, 0), and its collection name is "_MODEL_", and you want to place a collection instance of it at other location (not origin), and you want to disable the model at the origin by disabling the parent collection of the collection named "_MODEL_", and you want to keep enabled (visible) the collection instances. ![Monkey.jpg](https://archive.blender.org/developer/F8503925/Monkey.jpg) **People will adapt the non-logic bug but they will see weird things** This is a big problem because if people don't know the bug then they think that it's the logic of viewport enablement of collection instances, and all their projects depend on that, but once they save and close and then re-open the file, they will see weird things.

Manda Rajoelisolo commented

2020-04-30 22:18:01 +02:00

Added subscriber: @manda.3d.projects

Ankit Meel commented

2020-05-02 15:14:57 +02:00

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

Manuel Castilla commented

2020-05-30 21:37:16 +02:00

Added subscriber: @manzanilla

Clément Foucault commented

2020-06-30 15:35:01 +02:00

Added subscriber: @fclem

Clément Foucault commented

2020-06-30 15:35:01 +02:00

Without reopening the file, you can trigger the missing update by changing the viewport visibility of any Scene Collection object.

Open test file.
Disable SubCollection viewport visibility in outliner.
Change Sun (or any other object) viewport visibility in outliner to make the Instances of 'Collection' disappear.

Without reopening the file, you can trigger the missing update by changing the viewport visibility of any Scene Collection object. - Open test file. - Disable SubCollection viewport visibility in outliner. - Change Sun (or any other object) viewport visibility in outliner to make the Instances of 'Collection' disappear.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Disabling/enabling in viewport a sub collection doesn't make the instances of the collection disabled/enabled unless you save and re-open the file #76279