Here’s a quick note on the layer intersection group concept in our template. We use 4 numbers in most of our project layer settings:
- 0 is for layers that are hidden and should not intersect with visible items in a given layer combo
- 1 is for layers that are set to intersect, and should be the most common, especially among visible layers
- 2 is for layers that should not intersect with standard “1” group layers. Examples of conditions that may require a Group 2 Layer are:
- barge rafters or sloping trim that needs to run in to perpendicular and horizontal trim (this always results in a messy connection)
- walls being trimmed with SEO to a roof plan, whose trimmed portion is interfering with content above the roof
- there are defualt layers for these conditions already set up:
- A | ROOF – EXTERIOR.TRIM NON-INTERSECTING
- A | WALL – EXTERIOR ACCESSORY.NON-NTERSECTING
- AI | MOULDINGS.TRIM NON-INTERSECTING
- 999 is commonly used for module content placed from IFC files received from consultants.
- This is a variable not accounted for in our template, since IFC coordination is on a project by project basis
In 2018 I am revamping the WWABIM site with new quick tips. These will be short messages and tips to help improve your workflow, efficiency and general proficiency at modeling and documenting in ARCHICAD. This is the first tip of the year!
Use the quick layers palette! This palette will allow you to turn layers on/off, cycle through previous custom layer sets, and more with out the need to tediously sort through the layer settings dialog.
Options on the quick layers palette are to hide/lock/unlock a selections layer(s), or all layers not selected, and to switch back to previous/next custom layer combinations. This allows you to turn groups of element’s layers on at once, instead of sorting through the layer lists.
I recommend using the quick layers palette as a standard to your work environment. If you want to strip palettes and tool bars out of your w/e, you can also assign a shortcut to show/hide this palette, similar to how most have a shortcut for the solid element operations palette.
Walls can relate to each other, and other element types, based on several factors. First, layer intersection priority defines which layers will intersect. Second, building materials determine how different composite or custom profile skins interact with each other. Lastly, wall/beam junction order determines in which order walls or beams will intersect.
Layer Intersection Priority
Walls with different layer intersection priorities do not intersect in plan. Walls overlap to their reference line.
Building Material Priority
Walls with different core building materials will have a separator line at the core. Skins may be cut through by the core if the finish skins have a lower building material priority, even if the reference line is set to the wall core.
All walls have the same junction order (8)
Horizontal & angled walls have a higher junction order (10)
Vertical & angled walls have a higher junction order (10)
If you have two building designs for the same site, you can avoid multiple site models/building models scattered around your model environment by creating two new layer combinations.
First create two new layer combinations module option A & B, then three new layers. The first is the “modules layer” which contains all common hotlink elements.The next two layers are the toggle layers, one is only on with layer combination “A”, the other only layer combination “B”.
The last step is to assign hotlinks to one of the toggle layers (I learned something new about this today!). First select the hotlink to be assigned to toggle layer A, go to File > External Content > Hotlink Module Settings.
Change the Master Layer for this module to the correct toggle layer and follow these steps for each module which will be part of the option A or option B schemes.
Reading a Shoegnome post recently I came across a concept which I have integrated into our latest template version. That is a layer intersection group “0” for all layers not shown in the current layer combination. While I don’t normally recommend mass attribute purging for most projects, this suggestion for layer management has huge potential to improve the way your model views in 3d and elevation.
Layers that are not visible can have an impact on the model. For elements like the operators of an SEO this is a good thing. For things like roof only walls or trim elements that show up in one view but not all this can be problematic. You can end up with elements that are turned off which are interfering with the appearance of your model. By changing all layers which are off for a specific layer combination to intersection group “0” you reduce or eliminate the chance of this happening.