SketchUp – The Sacred Layer0
Layers – they seem simple enough. Place a SketchUp entity on a layer, turn off the layer, hide it. Each entity sits on only one layer.
What could go wrong?
Actually, quite a bit. When you model using groups and components (which all good modelers do), and start placing groups, components, or loose geometry onto different layers, things can get a little messy.
In this post, I’ll discuss the fundamentals of layer placement.
1. Create all loose geometry (faces and edges) on Layer0, never anywhere else.
2. Only move groups and components to different layers.
To illustrate the hows and whys, I’ll use this simple model of a kitchen set:
A perfect model consists entirely of groups and components – no raw geometry. But for purposes of demonstration, this kitchen set model consists almost entirely of groups and components. There is some loose geometry – some faces and edges that are not included in any groups or components.
The Outliner shows all groups and components in the model. I’ll focus on the table – the table components right now are just the four table legs. There’s no group or component for the table top or for the table as a whole.
The raw geometry consists of the faces and edges of the tabletop. If you can click a face to highlight just that face, you know it’s not part of a group or component. This is a modeling no-no.
With just one layer in the model to start, “Layer0,” all entities currently sit on that layer. But I’m adding three new layers – one for just the table legs, one for just the table top, and one for the entire table.
(Incidentally, the filled radio button to the left of “Layer0” means it’s the active layer. Which means anything you create sits on Layer0. While you canmake another layer active, DON’T DO IT. It’s very easy to accidentally leave a layer active, create more on it than you intended, and later try helplessly to figure out why your layers aren’t making sense.) Anyway. . .
Moving Entities onto Layers
As stated above, the best practice is to keep all loose geometry on “Layer0,” because it’s easy to make errors when raw geometry goes on other layers. (Remember, only groups and components should be moved to layers.)To show this, I’m selecting a few loose faces of the table top. No edges are selected, and a lot of faces that should be selected as part of the table top are not selected. (A common rookie error.) These selected, loose faces are (wrongly) placed on the “Table Top” layer, which is done via the Entity Info window:
The four table leg components are now selected and (rightly) placed on the “Table Legs” layer (because it’s OK to move components):
Now the entire table – legs and loose-geometry table top – are made into a group and placed on the “Table” layer:
Why Raw Geometry on Layers is Problematic
Now comes the test. If I hide the “Table” layer, the entire table disappears from view. Good so far.
If I hide the “Table Legs” layer, the legs are gone. So even though an object (table legs, in this case) is supposedto reside on only one layer, a group or component can actually reside on more than one layer if it’s nested inside a larger group / component. In this example, the table legs are on both the “Table” and “Table Legs” layers.
Finally, here’s what happens when hiding the “Table Top” layer. Some of the faces disappear, but the rest of the faces and edges are still showing. It’s a mess.
Clearly, this is an extreme example – you’d probably have the presence of mind to keep all loose table top entities in the same place. But it’s quite easy to select only faces and not edges, or vice-versa. So stick with the “Layer0 for raw geometry” rule to prevent any problems like this. When models become complex, it gets much easier to place things where they have no business being.
The Right Way
Here’s how this model should be handled. All loose geometry of the table top stays on Layer0 . . .
. . . and after you make a group of the entire table top, the group is moved to its layer.