Per-Viewport Collection Visibility #61327

Closed
opened 2019-02-08 15:43:47 +01:00 by William Reynish · 40 comments

This is a follow up to D4011. We agreed to create a new design task for this.

For Collection visibility, we have two remaining unsolved problems still:

The ability to view different Collections in different viewports

  • This is useful for a number of workflows. Imagine creating a forest. It's useful to see the whole forest in viewport 1, but then only see a single tree in viewport 2.
  • Or, if you are making an animation: In viewport 1 you see the whole scene from the camera with everything visible. In viewport 2, you only see what is needed for the animation. Everything that would obscure your character is hidden.

The ability to set temporary viewport visibility, and then return to a previews visibility state

  • You may have set the scene visibility a certain way that makes your scene look correct. Then you might want to temporarily view certain Collections while adjusting something, and then return to the previous state.

It turns out that we can solve both these problems in a simple way: By bringing back 'unlinked' visibility. Adding this one option back allows us to kill two birds with one stone.

In Blender 2.79, we had the ability to override the layer visibility for each viewport, or return to the main scene visibility using this toggle:
Screenshot 2019-02-08 at 15.29.21.png

This actually solves both of the above issues: You can then set it up to only show a different set of Collections in your scene, and it also allows users to temporarily see a different set of Collections and return to the main visibility by toggling back off the override.

In 2.8, we have the Collections Visibility popover in the 3D view. Here we could add the toggle, like so:
Screenshot 2019-02-08 at 15.25.45.png

  • Overrides visibility per viewport
  • Let's you go back to previous state by disabling again

In addition, this toggle gives the popover a true reason to exist.

This is a follow up to [D4011](https://archive.blender.org/developer/D4011). We agreed to create a new design task for this. For Collection visibility, we have two remaining unsolved problems still: # The ability to view different Collections in different viewports - This is useful for a number of workflows. Imagine creating a forest. It's useful to see the whole forest in viewport 1, but then only see a single tree in viewport 2. - Or, if you are making an animation: In viewport 1 you see the whole scene from the camera with everything visible. In viewport 2, you only see what is needed for the animation. Everything that would obscure your character is hidden. # The ability to set temporary viewport visibility, and then return to a previews visibility state - You may have set the scene visibility a certain way that makes your scene look correct. Then you might want to temporarily view certain Collections while adjusting something, and then return to the previous state. It turns out that we can solve both these problems in a simple way: By bringing back 'unlinked' visibility. Adding this one option back allows us to kill two birds with one stone. In Blender 2.79, we had the ability to override the layer visibility for each viewport, or return to the main scene visibility using this toggle: ![Screenshot 2019-02-08 at 15.29.21.png](https://archive.blender.org/developer/F6549617/Screenshot_2019-02-08_at_15.29.21.png) This actually solves both of the above issues: You can then set it up to only show a different set of Collections in your scene, *and* it also allows users to temporarily see a different set of Collections and return to the main visibility by toggling back off the override. In 2.8, we have the Collections Visibility popover in the 3D view. Here we could add the toggle, like so: ![Screenshot 2019-02-08 at 15.25.45.png](https://archive.blender.org/developer/F6549633/Screenshot_2019-02-08_at_15.25.45.png) - Overrides visibility per viewport - Let's you go back to previous state by disabling again In addition, this toggle gives the popover a true reason to exist.

Added subscriber: @WilliamReynish

Added subscriber: @WilliamReynish

#68940 was marked as duplicate of this issue

#68940 was marked as duplicate of this issue

Added subscribers: @brecht, @dfelinto, @JulienKaspar

Added subscribers: @brecht, @dfelinto, @JulienKaspar

Added subscriber: @pablovazquez

Added subscriber: @pablovazquez

@brecht @JulienKaspar @pablovazquez any thoughts on that? It will effectively add another layer of invisibility for users to deal with it.

@brecht @JulienKaspar @pablovazquez any thoughts on that? It will effectively add another layer of invisibility for users to deal with it.

This is true, in a way.

But this was a fairly important option in 2.7x, and adding this one option actually makes it so we can avoid doing other more complicated things like saved visibility states etc.

And besides, I think we need to add this anyway, for the case where you just want to see different things in different viewports.

It also gives the Collection Visibility popover a reason to exist. Currently it's redundant.

This is true, in a way. But this was a fairly important option in 2.7x, and adding this one option actually makes it so we can avoid doing other more complicated things like saved visibility states etc. And besides, I think we need to add this anyway, for the case where you just want to see different things in different viewports. It also gives the Collection Visibility popover a reason to exist. Currently it's redundant.

I'd rather we focus on other improvements. I haven't seen many users ask about this.

I'd rather we focus on other improvements. I haven't seen many users ask about this.

Added subscriber: @moisessalvador

Added subscriber: @moisessalvador

Count me as one of said users, but there's no hurry ☺ I even made a thread in DevTalk describing a really neat use case that my friend uses it for. Now that Local Cameras are back, this would be the other last feature needed

Count me as one of said users, but there's no hurry ☺ I even made a thread in [DevTalk ](https://devtalk.blender.org/t/where-is-un-lock-camera-and-collections-previously-lock-camera-and-layers/4012) describing a really neat use case that my friend uses it for. Now that Local Cameras are back, this would be the other last feature needed

Added subscriber: @machieb

Added subscriber: @machieb

It would be great to have the abilty to have different collections vissible in different viewports! The way with the viewport vissibility override is great, an so it gives the Collection Visibility popover a reason to exist!

It would be great to have the abilty to have different collections vissible in different viewports! The way with the viewport vissibility override is great, an so it gives the Collection Visibility popover a reason to exist!

@dfelinto has done great work lately on visibility. Maybe he can have a look, if this task is hard or easy to establish?!

@dfelinto has done great work lately on visibility. Maybe he can have a look, if this task is hard or easy to establish?!
Member

To give my feedback on this as well: I like it!
But I think it would be more usable as a tab in the sidebar instead of a popup. There's a reason why the Ctrl + H menu was never used, and it's because it was harder to access if you have to first hit a shortcut (or in this case click on a tiny button).

I think the old "Layer Management" Addon is an interesting point of inspiration for this. I used it a lot in 2.7x and often kept it open on the side.

Selection_005.png

To give my feedback on this as well: I like it! But I think it would be more usable as a tab in the sidebar instead of a popup. There's a reason why the Ctrl + H menu was never used, and it's because it was harder to access if you have to first hit a shortcut (or in this case click on a tiny button). I think the old "Layer Management" Addon is an interesting point of inspiration for this. I used it a lot in 2.7x and often kept it open on the side. ![Selection_005.png](https://archive.blender.org/developer/F6561425/Selection_005.png)

Added subscriber: @tgarriott

Added subscriber: @tgarriott

@JulienKaspar: Well yes, but that is an entirely different issue.

However, I agree that the UI in the Collections Visibility popover is weak. The hierarchy isn't properly communicated, and the fact that it's a popover isn't so nice, compounded by the fact that the 3D view header is overcrowded now.

A mini-outliner view, with proper hierarchy, in the Sidebar I think is probably more useful here.

@JulienKaspar: Well yes, but that is an entirely different issue. However, I agree that the UI in the Collections Visibility popover is weak. The hierarchy isn't properly communicated, and the fact that it's a popover isn't so nice, compounded by the fact that the 3D view header is overcrowded now. A mini-outliner view, with proper hierarchy, in the Sidebar I think is probably more useful here.
Member

Added subscriber: @jendrzych

Added subscriber: @jendrzych

Added subscriber: @sebastian_k

Added subscriber: @sebastian_k

I think this would be a very welcome addition!
Actually I was expecting the dropdown menu in the 3d Viewport to be per viewport by default.
Overlays, Object Visibilty and Shading are per viewport, so it would only be logical to make the collections dropdown menu be per viewport as well. Or at least add the option to override it. I agree with @WilliamReynish that currently it is just redundant and adds no extra funcionality.

I am badly missing the option to setup objet and collection visibilty per viewport. I was hoping that maybe we could bind a Viewlayer or Scene to a workspace, but Per Viewport Visibilty would already be a step in the right direction.

I think this would be a very welcome addition! Actually I was expecting the dropdown menu in the 3d Viewport to be per viewport by default. Overlays, Object Visibilty and Shading are per viewport, so it would only be logical to make the collections dropdown menu be per viewport as well. Or at least add the option to override it. I agree with @WilliamReynish that currently it is just redundant and adds no extra funcionality. I am badly missing the option to setup objet and collection visibilty per viewport. I was hoping that maybe we could bind a Viewlayer or Scene to a workspace, but Per Viewport Visibilty would already be a step in the right direction.

Added subscriber: @zeauro

Added subscriber: @zeauro

I would prefer a viewlayer selector per 3D Viewport and overrides for visibility as other overrides.
I think that old demo from dalai about matcap overrides per objects was working well.

Now shading properties and overlays are per viewport properties.
If limitation is just about Rendered display method, I think that users could accept the fact to have only 3D Viewport in sync with properties able to be in Rendered mode.

I would prefer a viewlayer selector per 3D Viewport and overrides for visibility as other overrides. I think that old demo from dalai about matcap overrides per objects was working well. Now shading properties and overlays are per viewport properties. If limitation is just about Rendered display method, I think that users could accept the fact to have only 3D Viewport in sync with properties able to be in Rendered mode.

Added subscriber: @PetterLundh

Added subscriber: @PetterLundh

Added subscriber: @AlphaVDP2

Added subscriber: @AlphaVDP2

Added subscriber: @LeoMoon

Added subscriber: @LeoMoon

A few use-cases where this feature really helps:

Character animation: Animate in a clean and simplified viewport while viewing the result in context in another viewport.

Modeling: View a single item in one viewport while seeing it in context in another viewport

Layout: View a collection in one viewport while seeing the instance in context in another view.

Some Plugins: Some plugins like Blender Light Studio can not be ported if this option does not exist.

A few use-cases where this feature really helps: Character animation: Animate in a clean and simplified viewport while viewing the result in context in another viewport. Modeling: View a single item in one viewport while seeing it in context in another viewport Layout: View a collection in one viewport while seeing the instance in context in another view. Some Plugins: Some plugins like Blender Light Studio can not be ported if this option does not exist.

Added subscriber: @DanielPaul

Added subscriber: @DanielPaul

This is one of the main features we decided to use blender for our virtual production studio.
The ability to have a second output with (in our case is an alpha output)
makes it super comfortable to integrate realtime preview over greenscreen and vice-versa.
Mask out some objects or just bring CGI elements in front of people is really handy with multiple viewport visibility's.

Because we want to use 2.8 and eevee for our preview.
for now, do the alpha output with 2.79 at the same time :D

This is one of the main features we decided to use blender for our virtual production studio. The ability to have a second output with (in our case is an alpha output) makes it super comfortable to integrate realtime preview over greenscreen and vice-versa. Mask out some objects or just bring CGI elements in front of people is really handy with multiple viewport visibility's. Because we want to use 2.8 and eevee for our preview. for now, do the alpha output with 2.79 at the same time :D

Added subscriber: @Forshu-2

Added subscriber: @Forshu-2

Added subscriber: @mbutscher

Added subscriber: @mbutscher

Any update about this feature?

Any update about this feature?

Added subscriber: @lsimic

Added subscriber: @lsimic

Added subscriber: @RonHuber

Added subscriber: @RonHuber

Added subscriber: @HirotakaImagawa

Added subscriber: @HirotakaImagawa

I wrote about another feature of Collection. Please refer to #67985
https://developer.blender.org/T67985

I wrote about another feature of Collection. Please refer to #67985 https://developer.blender.org/T67985

Added subscriber: @ProHunterAllen

Added subscriber: @ProHunterAllen

Added subscriber: @zaiburg

Added subscriber: @zaiburg

Added subscriber: @vanvelt

Added subscriber: @vanvelt

In #61327#670092, @LeoMoon wrote:
A few use-cases where this feature really helps:

Character animation: Animate in a clean and simplified viewport while viewing the result in context in another viewport.

Modeling: View a single item in one viewport while seeing it in context in another viewport

Layout: View a collection in one viewport while seeing the instance in context in another view.

Some Plugins: Some plugins like Blender Light Studio can not be ported if this option does not exist.

PLEEEEASE! We need Blender Light Studio in 2.8!!!!!

> In #61327#670092, @LeoMoon wrote: > A few use-cases where this feature really helps: > > Character animation: Animate in a clean and simplified viewport while viewing the result in context in another viewport. > > Modeling: View a single item in one viewport while seeing it in context in another viewport > > Layout: View a collection in one viewport while seeing the instance in context in another view. > > Some Plugins: Some plugins like Blender Light Studio can not be ported if this option does not exist. PLEEEEASE! We need Blender Light Studio in 2.8!!!!!
Dalai Felinto was assigned by Brecht Van Lommel 2019-09-29 14:14:07 +02:00

This is in 2.81 already now after 92736a7b75.

Currently it can only show a subset of collections that are already marked as viewport visible in the outliner. I believe this is still planned to be changed to support overriding showing collections that are marked as hidden for the viewport in the outliner.

This is in 2.81 already now after 92736a7b75. Currently it can only show a subset of collections that are already marked as viewport visible in the outliner. I believe this is still planned to be changed to support overriding showing collections that are marked as hidden for the viewport in the outliner.

I believe this is still planned to be changed to support overriding showing collections that are marked as hidden for the viewport in the outliner.

Yup, this is on my desk.

> I believe this is still planned to be changed to support overriding showing collections that are marked as hidden for the viewport in the outliner. Yup, this is on my desk.

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Thomas Dinges added this to the 2.81 milestone 2023-02-08 16:48:11 +01:00
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
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
23 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#61327
No description provided.