How do YOU use layers?
-
I appologise; it should have been "Jakob"
-
oh yes, the intersect tool is definitely one of my favourites. sometimes (for example, if you have an imported terrain model) it is the universal cure to get all faces closed. especially the possibility of "intersect SELECTED" is great, for it gives you perfect control over what is supposed to be intersected.
-
jakob,
i do basically as you do. always draw on layer 0. as soon as i start drawing something i group it or create a component. when it is ready i assign a layer to it. layers work for me as visualisation tools.
it is like a mantra to me: layer0-group/component-put in layer,
layer0-group/component-put in layer,
layer0-group/component-put in layer,
layer0-group/component-put in layer,
layer0-group/component-put in layer... -
Draw everything in Layer 0.
Create groups and components.
Use Layers to control visibility. -
great, it seems that working like that
(draw in layer0 - group/component geometry - put these into different layers)
is the "right" or most sensible way - if you all use to stick to that procedure.now I am reassured that it is a good thing to hammer that "modus operandi" into my colleagues
-
When I start a project I first create a folder in my Components library with the projects name, then I open two instances of SU. One instance is labeled with project name and other is untitled. I use the untitled instance for building components in layer 0 then saving as a component in the project folder that's in the Components folder, I do not copy + paste into project instance I rather import from Components into project instance and assign a layer when imported.
-
I also try to keep myself to the same rules as you, Jakob.
There is one important thing (that I would not call a bug but rather an illogical and annoying feature) that you should always keep in mind not to mess up your model: when you model something on Layer 0 > then group (make component) and move to another layer (the primitive geometry within the group/component still being on Layer 0) > and then for some reason you need to explode the group/component, all the primitives will remain on the layer the group/component was (i.e. NOT on Layer 0 where they used to be).
A workaround is: when having exploded the group/component, all its geometry is still selected. Now quickly right click > Entity info > and assign everything back to Layer 0.
I hope keeping this in mind will help to prevent annoyances in the future.
-
@unknownuser said:
Draw everything in Layer 0.
Create groups and components.
Use Layers to control visibility.ditto
-
@gaieus said:
...and then for some reason you need to explode the group/component, all the primitives will remain on the layer the group/component was (i.e. NOT on Layer 0 where they used to be).
A workaround is: when having exploded the group/component, all its geometry is still selected. Now quickly right click > Entity info > and assign everything back to Layer 0.
very useful. i had not noticed it yet. perhaps this is the origin of some baffling problems in the past.
-
thanks Gaieus. that did really confuse me lately, when I suddenly found primitive geometry in the wrong layer. now I know, that it was not (or at least only indirectly) my fault
-
It is possible to change all the layer colours to textures.
So, using 'colour by layer' option in styles it is possible to retexture the whole model without touching a single polygon.
Taking it further, coincidental groups and components (with different textures) can be swapped in and out using layers and scenes.
This technique allows a quick comparison of appropriate textures.
Smiley
-
I usually model everything in the default layer 0, but always put cars, people, and trees in their own layers so they can be turned off while modeling other things.
-
@daniel said:
I usually model everything in the default layer 0, but always put cars, people, and trees in their own layers so they can be turned off while modeling other things.
ditto
Advertisement