It is still possible to turn layers OFF in both Model and Layout/Detail views at the same time. This is called the global visibility.
To control the visibility of a layer globally, right-click on a light bulb and pick “Layer Off Everywhere.”
The light bulb will change to a new color - red.
Changing the Global State
What happens if you click the red global off icon? The behavior will depend on where you are. If you click on a red “globally off” light bulb, the layer will be turned ON in the view you are working in and nowhere else. This is helpful because it will not affect any views you cannot see.
Adding Details and Legacy 3DM
In addition, new details will be created with the global layer visibility settings by default.
Rhino 7 or earlier versions 3DM files will open in Rhino 8 displaying the global visibility state.
Saving your Rhino 8 model back to Rhino 7 or earlier versions will also utilize the global visibility state.
Give it a try and let us know if it works for you.
I think that this an amazing feature. A workaround that I’ve been using instead was putting sheets in separate files and outputs of make2d command (to get vector in PDF prints) in separate files and linking them on the sheets. This has an advantage on larger projects with many drawings/sheets, but when keeping everything in one rhino file this feature is a real game changer.
I can confirm it’s broken in the latest downloadable WIP (8.0.22347).
I’m a little worried that this new implementation could be a bit more complicated than necessary.
Trying to make sense of these menu entries - how can a layer be on ‘in this detail only’ and at the same time in ‘all layouts’? Can a detail occur more than once in multiple layouts? Even if: ‘in this detail only’ and in ‘all layouts’ sound like a contradiction.
Anyway, looking forward to this feature very much, so thanks for finally taking care of this! I use the plugin ‘SafeLayout’ too in R7, but there are quirks and bugs all over the place.
Ok, thanks… still, a few things don’t make sense here.
Following the logic of what you said - if there are menu entries “Layer on/off in this Detail only” with submenus “This/All layouts”, shouldn’t there be also menu entries “Layer on/off for all Details” with submenus “This/all layouts”, instead of “Layer on/off everywhere”?
Regarding the red lightbulb:
Red means “off everywhere”, right? But what about “on everywhere”, which is a different thing?
The way I see it: the left lightbulb can be in 4 different states. “model space on, global on”, “model space off, global on”, “model space on, global off”, “model space off, global off”.
In fact, it’s 8 states, because sublayers can have this icon when their parent is turned off.
So, 8 different states packed into one icon. No matter how you colorize it, it will be hard to read at a glance.
Test this ambiguity: create a sublayer, turn off the parent. Go to layout, RMB-menu “layer on everywhere”. Now the bulb is just regular yellow. Then, LMB-click the bulb to turn it off, then again back on. It’s the half-yellow icon again. Shouldn’t it still be “on everywhere”?
Btw., there’s a bug with layer panel settings: column positions/widths are not remembered.
Repro: go to a layout, change the columns, go to model space, then back to layout space. Columns are reset.
Thanks for testing the WIP.
We made this quick and rough video to explain these settings before the holiday weekend. I will do a better video in a few weeks.
Here is the model that I am using in case you want to try it. solids.3dm (452.0 KB)
Here is a summary of the settings:
Globally OFF: Is OFF Everywhere, model and layouts. There is no option for an ON when the light blub is RED or globally OFF. This is the nuclear option.
When ON globally the Model viewports and the Layout/Details to control their own visibility. The light bulb is gray when OFF locally, and Yellow when on locally.
You get control over OFF in ALL details on the current Layout, or OFF in ALL Details on ALL Layouts except the current Detail.
You also get ON in ALL details on the current Layout except the current Detail, or OFF in ALL Details on ALL Layouts except the current Detail.
On everywhere you can turn the layers on in ALL Model and Layout/Details. If Layers were off, previously then will be returned to their locally off visibility.
Finally the Parent layer can be Globally OFF, or Locally OFF or ON in a Detail or viewport, not affecting the other Detail or Viewports…
We logged this issue: RH-72219 “Layer on In this Detail” Works When Parent is OFF.
Hopefully that will be working soon.
I can not duplicate this on Windows. Check the next release and see if it is fixed for you. Otherwise, please send a screen capture videos showin showing how you get to the issue.
Complicated can equal powerful. This is a significant change. So it will take some time to get used to and work out all the special cases that were not anticipated. And “test drive” to see how it works for your modeling process.
The latest WIP (8.0.22361.13135, 2022-12-27), for the first time, acutally worked as advertised.
So, sincere thanks for going in and fixing this long standing issue! It was one big puzzle piece why many people avoided Rhino for any serious layout work.
Just for clarification:
In the video you posted, in layout/detail space, there’s just one column of bulbs visible:
I assume this is the “Layout/Detail on” column. What’s strange is, where did the model space “On” column vanish to?
For those unaware: layout/detail have those 2 columns of bulbs, and the one you are using is usually kind of hidden to the far right in the panel.
Is it possible that the model space column has been removed in layout/detail space in your latest build (not publicly available yet)? That would make sense, since it’s independent of layout/detail anyway, and only leads to confusion which column to use.
Anyway, let’s continue 2023 (which half the globe is in already).
Happy new year!
Hello! Of course, I forgot this filter is there…
Actually, since the model bulb column does not have any influence now on the layer visibility in layout/detail, maybe it’s best to remove it (and the filter icon ) completely? Or at least make it hidden by default?
Here’s a veeeery importand wish: detail/layout layer settings of files attached as worksessions should be remembered in the .rws file! I just tested this, and they’re not.
But please consider the issue with worksessions and layer visibility! When working on bigger architectural scenes and/or in a team, it’s common practice and a necessity to split up the scene in parts like building design options / urban model / all kinds of 2D plans etc… Since Rhino does not yet support a “true” collaborative workflow (one central file, many users, like in Revit or ArchiCAD), at least worksessions should be supported as logically and consistently as possible. Creating layouts with worksessions is needed. When I open an .rws file, I’d expect the layouts/details to look exactly like I saved them.
Having watched the video on this, I find the new workflow rather confusing and convoluted. I really dislike that you have to right click and use submenu items to change the visibility globally.
In principle, detail views could get the global on/off and local changes treatment. That would be fine by me, but now I feel like I would need to do more work (click more) to get visibility sorted out.
There is a reason why Blenser has 3 (!) visibility icons, one for on/ off globally (when turned off, a layer isn’t even computed) , a second for viewports and a third for renders. I would much rather have 3 of these lightbulb like buttons available to use (I could always hide the layouts one when I don’t need it for a while) as opposed to cramming everything into a single lightbulb and having to use rmb as a result. But, instead of showing 3 lightbulbs, make it an eye (global) , a monitor (for viewport) and a lightbulb or so (for layout).
I personally very much prefer the old way of doing things where you have a button for model space and one for layouts. Though, I certainly do get the wish to contdol detail views individually, which is nice.
Alternatively, I can imagine you want to tie layout and viewport visibility together, in which case you would select the layers you want to behave the same on model space and layouts, click a paperclip (like button at the top of the layer panel button row) and you’d see a paperclip icon appear over both model and layout icons. The “paperclip mode” could even be the default for all I care, but at least you can easily tell from the layers panel whether you have layer set to not show in prints, in the viewport or just for the active detail. Basically, the layout visibility should show layout visibility globally when there is no active detail view. It should show the detail view state when one is currently active and there should be a dedicated viewport button. You should be able to tie viewport and layout changes globally (reflected in both layout and viewport buttons) and any overrides in details should show as a red icon when disabled in detail, but not for layouts. Or green when enabled locally for a detail, but disabled globally for layouts
E: for accessibility and colour blind people, maybe use a red cross or green checkmark overlaid on the layout visibility icon. Would make it clrear what it stands for too.
That would be much more insightful and straightforward to me too. It would also just expand upon how everyone is used to work and streamline the workflow, as opposed to obfuscating it for everyone.
Worth thinking it through. Will do that later.
Anyway, here’s a suggestion I made 3 times already (and sadly never got a reaponse):
Just add a second bulb column to the model space, which works as the local visibility override in model space only! Like what layout/detail already have. In other words, all spaces (model, layout, detail) have 2 columns then.
The left column will always be the master switch. When turned off, layers are off everywhere, period (Like what the red bulb does now). When turned on, the second column will be considered as the local override (logical AND).
The whole point of this thread is: model space layer changes must not mess up layout/detail space, right? This would be the case when in model space only the LOCAL (new) bulb is used per default during editing, and the master bulb only after careful consideration.
The commands that change layer visibilty would need to be changed in a manner that they work both globally/locally. They already do in layout/detail (OneLayerOffInDetail, all these…)
Does this make sense?
I agree with Intuos: let’s not pack too many functions/variants into one bulb.
I haven’t tried out this functionality yet but I also don’t remember having the need for this. Perhaps I might love it in the future but for now I can only think this will make it cumbersome to right click on the bulb every time I want to turn it off globally. I also vote for solving it in a different one-click way.
Edit: Thinking more about it, for me it also makes more sense to right-click to another menu to turn off the layer for one perticular view instead of changing the behaviour everybody is used to.