? abt moving groups/components to different layers
-
Hi, Rose123:
I suspect that you are not taking advantage of the option to replace/ not replace selection with component. There is a check box on the Popup window at the moment of component creation, that in some circumstances is unchecked and in others is checked. If you really want the raw geometry to remain for further creation of modified shapes based on your first component then uncheck that box.
Many would say good workflow is always replace selection with component. And always assign components to named layers, so that only raw geometry is created in layer 0. The advantage is that you can then manipulate/ manage the layers in a number of ways. This isn't all, but it is a start. Others will fill you in, hopefully on what I didn't mention. -
Hi mitcorb, I DO replace selection w/component. Nevertheless, to put a component plus its geometry on a different layer, I have to highlight the component shell (is there a different name for it?) and put it on that layer. Then I have to open the editing box and put all the geometry on the layer, as well.
My question is, do I want to move the loose geometry to the different layer, or leave it on Layer 0? (and why?)
-
I don't think you want to move the loose geometry to another layer. The reason is because you will regret it....
Hard to explain how, but what sometimes happens is that in changing visibility of layers with loose geometry on any other than Layer0, you will have entities seem to disappear. You will have your faces visible but no edges. Things like that.
Layer use is just to be able to hide or unhide parts of the model. Moving a component or group does that. You don't need to move the loose geometry inside. Layer0 should remain the active layer that you draw in, then assign components or groups to other layers when you feel the need.
-
Thanks, pbacot! Ok, so it sounds like there's no good reason or purpose to move the component's geometry to a different layer even though it's possible? I just wondered that, since it was possible, there must be an occasional reason.
-
I think some users have specific reasons. They probably follow a technique that doesn't mess them up. I have not heard of a good purpose for doing it so far myself. I wonder why SU layers aren't designed to prohibit it, at least as a default.
-
Ok, thanks! Will keep my geometry on layer 0.
-
Rose, if you follow the "rules" from the Help files on Layers, you'll keep all geometry on Layer 0 as Tim and Peter advised and you'll leave Layer 0 active at all times, you'll find you have much less frustration with your models. Read.
Since Layers only control the visibility of entities and turning off the layer for component/group wrappers makes the entities inside invisible, there's no reason to move entities themselves to other layers.
-
Thanks, Dave, yes, I do keep my geometry on 0 (except for text), but again, since it's an option, I just wondered if anyone else found a reason not to do it.
-
There are rare reasons. One for instance: Twilight render can render geometry that is on hidden layers. Think of millions of grass blades which would definitely slow your modelling experience. Now with this kind of entourage, I usually put the geometry inside the component on a hidden layer - but from this example you can also realize that these are very special cases.
One further caveat however: If you have your group/component on a different layer but the geometry inside (correctly) on layer 0 and you explode the group/component, for some extremely frustrating reason, this geometry will be moved to the original layer of the group/component. I would call it a bug but actually it's rather a "feature" only.
When exploded, all the loose geometry is autoselected so you still have some chance to quickly move it back to layer 0. Or (after you have successfully messed up your model already) use this excellent plugin:
http://sketchucation.com/forums/viewtopic.php?p=47033#p47033 -
Ok, thanks, Gaieus! I figured someone would have a reason.
Advertisement