Small Improvements to Markers

This update to ARCHICAD went unnoticed by me. This was actually fixed in AC 21, but I just saw it in ARCHICAD 22. In AC20 and before, when you created a split in a section or elevation marker, then realigned the elevation marker, you ended up with a lot of extra points the section line.

AC 20: Elevation Cut Line Has Broken Continuity

AC 20: Elevation Cut Line Has Been Realigned, But Still Includes Extra Nodes

Now, when you realign a split marker (section, elevation or interior elevation), the section/cut line heals back up properly!

AC 21/22: Elevation Cut Line Has Broken Continuity

AC21/22: Elevation Cut Line Has Been Realigned and “Heals” Properly!

Advertisements

Another Case for the Element ID Manager

I know I have discussed the need for unique element ID’s several times. Today I came across a great use of the Element ID Manager to assign unique ID’s and track down elements with degenerated polygons.

The project had an error report showing 4 elements with degenerated polygons, all using the element ID CASEWORK.

The problem came when doing a find and select for elements using that ID, I found that there were 1,147 non-object based elements with that ID. From the report, I know that the elements are not objects. They would include object name.gsm before the (ELEMENT ID) in the report if they were object based errors. This allowed me to refine my find and select criteria to elements that were not objects only.

Once the Element ID Manager set unique ID’s for all elements previously called CASEWORK, I was able to track down 2 unique problem elements in the report (2 in the hotlink module, 2 in the building document model).

Using the same Find & Select criteria, I pinpointed the problem to 2 slabs with less than 3 nodes; basically 0 width slabs. Since these were remnants of an edited (probably split or resized) slab; the solution was simply to delete these slabs.

 

Tracker & Working Units

Recently we have seen inconsistent levels of precision between different work stations. One computer, using the Measure Tool, will show a wall at 10′, another will show it at 10′-0 1/64″ (for example). After a little testing and digging around, we found that Working Units, unlike Dimension Styles and Calculation Units & Rules, are not project specific. However, just like Dimension Styles, Working Units should be set to the highest level of precision possible; that is to the nearest 1/64″.

To check and modify your working units, go to the ARCHICAD menu > Project Preferences > Working Units.

Model Units Need to be Set to 1/64

If Model Units are set to anything other than 1/64″, there is a high likelihood of dimensions not reflecting intended design dimensions.

Dimensioned Length Shows 120 1/64″,  Measured Length Shows 120″

Beyond the input precision; be sure you are using actual tracker input, rather than just clicking when the tracker shows the desired length. You can tab through the tracker options with the “tab” key, or direct input short cuts are:

• ‘r’ = Distance (radial distance)
• ‘a’ = angle
• ‘x’ = x distance
• ‘y’ = y distance
• ‘z’ = z distance

Use the Shift key before the input to lock direction/angle. It should be second nature at this point to type Shift + R before putting in a distance. You can adjust your work environment to give higher levels of angle. I recommend setting it to every 15º, then use the angle input in the tracker for any angle at smaller increments.

Work Environment Input Constraints, Set to 15º

 

Cadimage Roof Covering Flicker

We have all seen surfaces that are too close together creating a flickering appearance in ARCHICAD and BIMx. The easiest solution is to move element incrementally farther apart until the flicker disappears. With coverings, moving the covering up and away from the roof can create a disassociation between the roof and the covering; meaning the covering will need to be rebuilt with any change in roof design.

There is a solution that keeps the covering associated and eliminates the flicker.

The roof shows an uneven appearance that changes depending on camera angle and movement.

Edit all roof coverings to have a minimum 1/4″ dimension at ‘Allow Space for Framing’

Flicker does not appear with 1/4″ spacing

It is also helpful to note that this setting is not required for all covering configurations. Corrugated metal, for example, does not have the same issue, since it has a natural depth that pulls most of the covering away from the roof. Standing seam or battens have large areas of flat planes that create the flicker, so they may require adjusting the framing thickness setting to get them to show as intended.

3d Style

In ARCHICAD 21, we were introduced to 3d Styles; a new view setting which allows customization of the view style in ARCHICAD. With the introduction of ARCHICAD 22, there are some new 3d Style effects that customize the smoothness and efficiency of 3d navigation and views. These are settings that existing in 21, but we are starting to see an effect of model appearance in 22.

This is especially prominent in high polygon models.

model while viewing 3d

model while navigating (explore) 3d

In the examples above, the same model has content “disappear” when using the explore feature of a high polygon model. This is presumably a feature of AC22 to improve navigation and 3d performance.

To prevent content from vanishing, the advanced settings in the 3d styles options need to be tuned. Click the Gear icon in the 3d styles setting next to the 3d Engine fly-out.  In the Advanced > OpenGL Options, cut the frame rate to the lowest setting (1), and the display radius to the highest setting (328′-1 1/64″, for whatever reason).

Advanced Open GL Options for ideal 3d viewing in AC22

These settings are not new to 22; in fact they are the same defaults out of the box as AC21. But the defaults need to be adjusted to work well with the changes or improvements made to AC22’s 3d processing.

 

Door and Window Markers

When working through process, it is important to not use the “no marker” setting in the doors and windows; unless a door or window will never have a marker attached to it; for framed openings, shutters, shower doors, etc.

Door and window markers are library parts, that have default settings. So when a marker is set to “no marker” to hide, then turned back to W Marker 21/22 or D Marker 21/22, the settings go back to their default. These defaults do not match our graphic standards for pens, font, marker type, or any other setting. Markers switched off at the element level, then turned back on need to be meticulously realigned with the projects graphics and our office graphic standards.

The proper way to hide door and window markers throughout the entire plan is through model view options. Either a temporary “custom” MVO can be used to turn markers off, or a dedicated MVO (such as our template 00 | Presentation Plan) can be applied.

 

The Wrong Way!

1. Place Doors & Windows from Favorites:

2. Door/Window Marker Settings from Favorites (correctly showing D Marker 21)

3. Set Marker to No Marker… Nope! Don’t do it!

4. When Marker is reset to D Marker 21(22), it comes back looking like this; and it takes a lot of time to rebuild to the correct settings defined by the favorites.

5. Turn markers off using the Model View Options instead!

Note: in ARCHICAD 22, there are no “Custom” MVO’s. If Markers are turned off for the 02 | Construction Documents they will be off for all views using that setting. But unlike turning markers off at the element level, turning them off & on in the MVO will retain the default settings for the marker from the favorites.

Custom Door Leaf Origin

We often need to use custom door leafs and window sashes. But as with any custom object or element, model primitives need to be saved with attention to project 0,0,0 (xyz relationship to project origin).  With custom objects, they should be saved at 0,0,0; centered or justified to an edge. Custom door and window leafs need to be saved relative to the Z axis, or at least relative to the model primitive’s home story.

The important thing to note on locating elements to be saved as doors or window sashes is they need to sit above project 0 or home story. Typically, door and window components are built form slabs to be saved as a leaf or sash. The easiest way to ensure the door aligns correctly with the plan symbol is to set the reference plane to the bottom of the slab, and set the slab’s elevation to 0′ to home story (or project 0).