I’ve learned how I can use layers so that if I have multiple variations of a design, I can put those variations on different layers so I avoid setting up multiple files of the same basic item. I realize I can use sublayers to put things under a specific layer, but sometimes that doesn’t allow the flexibility I’d like to have. I would like to be able to group layers after the fact. Maybe this comes under a wish list sort of thing. Or is there a way to do it already? Or is there a way to set up multiple layer books to do what I want? Anybody with experience at doing this?
Hi @Joe4
I don’t think you can merely group layers in Rhino, Layer books always seemed to me to merely be a clever and convoluted way to turn on and off layers but maybe there is something there. Layers are hard coded meaning one state where objects can reside.
The only way to kind of group layers is to make a block out of those objects and then insert the block wherever you want or on a new layer. Though the old layers will still be able to turn on and off the parts of the block and the insertion layer can as well.
I use sublayers for layer grouping…
I create a layer but don’t put any objects on that layer
Then I create the sublayers which might also have sublayers
Then I can turn on and off all sublayers easily by turning on and off the parent layer.
I would try the layer states panel, this way you can save different layer states turned on or off with other settings. But beware I have had this command completely forget the states so be careful.
RM
Thanks. I like the suggestion of making a layer that doesn’t contain objects but has its contents in sublayers. I can work with that and see how it goes.
If McNeel is listening, I’d like to put on the wish list the ability to group layers after the fact similar to how you can do this in a program like Krita.
i encounter this issue frequently.
my workflow is to, first, create a layer tree (layer book?) for the variations, and, second, a layer tree for all the layers each variation uses. when you finish working on a variation, you block it with the base point at the world origin, and place it on a new layer inside the variation layer tree. if you need to work on a variation, you explode the block, work on it, then block it again at the world origin and place the block again on its layer.
EG: for creating a set of massing models in architecture, each massing model uses ~2-3 layers - solid, void, ground- which are in the second layer tree. each massing model you do is then blocked and placed on its own layer in the first layer tree.
looks something like this:
Variations (this is the first layer tree)
…Variation 01
…Variation 02
…Variation 03
Stuff in Variations (this is the second layer tree)
…Solid
…Void
…Ground
all the geometry and objects in each variation are in the second layer tree, while the block object of the variation is in the first layer tree.
using this method it’s easy to turn on/off variations and to keep track of what is in each option. the most obvious drawback is that it relies on blocks, so be careful when purging, and texture mapping can be unpredictable with blocks if you start linking the file into a larger file.
Thanks. I can see how that might work. What I’m going to have to do is try to think ahead on how to divide the project. Most of mine has been shop drawings for driveway gates. I get drawings from architects or designers and have to turn them into producible iron or aluminum work that meets code and can be produced within budget. The biggest problem I run into is the changes that sometimes drive me a bit crazy. Sometimes what is wanted can’t be done for one reason or another and we start a round of “how about this” . Recently I had one stair railing that ran to 8 different variations in style. But I’ve got enough experience now to maybe divide things up in sections. Not sure I want to use the block method but it is a possibility.
Hi @Joe4
I forgot one more thing that might help might be to use worksessions.
This way you can link and view multiple Rhino files in one Rhino file.
Worksessions makes it easy to turn on and off one entire model. Maybe this will help if you need to see all eight models at once but they are in different files. I have had troubles with worksessions and materials but you might not run into that. I think the layer states tool works on worksessions offering you more ways to view and present multiple models. Maybe layer books work with it you’ll have to test.
The one big caveat show stopper for me is that you can’t move a worksession file, (which I’ve requested many times) unless it is active. Makes creating things a lot harder or impossible if two models are in the same space and you want to see them both at once.
RM
Thanks. I’m going to keep it simple for a while. I’ve also had problems with materials as the Rhino render physical things doesn’t seem to match other surface treatment tools. But I digress. I will look into worksessions, but sounds more involved than I want to get.