Friday, 27 September 2013

We're Hiring!


Are you a BIM expert with great leadership skills? The HOK buildingSMART Team has two openings available for a regional buildingSMART (BIM) Manager. One opening is for our Asia Pacific offices, with lead office in Hong Kong. The other opening is for our beautiful St. Louis, Missouri office.

Click either link below for the details and to apply online:


Tuesday, 17 September 2013

Phantom Keynotes

We have had several users report that some items in Keynote Legends could not be tracked down in any sheet view, even after verifying that keynoting default settings are correct. This issue had me scratching my head for a while until I figured out what was going on.
Here’s a typical scenario where this could occur: You have a core & shell project that was documented and under construction and the model gets copied as a new project for the Tenant build-out phase. As the model cleanup process commences, users start reporting that they cannot find some keynotes that are being reported on the legend.
While troubleshooting, I noticed that when enabling the view's underlay, the phantom keynotes showed up together with the tagged elements, which then led me to tweak the view range and ultimately discover how these project files were started and what the root of the problem was: when the view range was adjusted, keynoted elements were no longer visible, but still reported in the Keynote Legend. As you can see in the image below, a plumbing fixture was keynoted and properly listed in the legend:
Keynotes OkIn another view, the cut plane and top plane were lowered until the element and keynote were no longer visible in the view::
Keynotes NOT Ok
In the above image, you can also observe that right-clicking the family type also reveals that the object is not visible in the view, yet it reports in the legend. Note that hiding the element and/or tag in the view makes the legend update accordingly, but in the above example the legend is misreporting.
This has been confirmed as a bug and slated for a future fix. In the meantime, please be careful and use this example to help in your troubleshooting efforts.

Monday, 9 September 2013

Cut Representation of Slanted Columns

We have confirmed a bug with the cut representation of sloped Structural Columns in views set to a Coarse Detail Level (EDIT: the bug seems tied to the symbolic linework that shows only in Coarse). This issue occurs in Revit 2014 SP1 and in prior versions as well.
The Structural Column family in the following example was set to not show pre-cut in plan views. When the Detail Level of plan views is set to Coarse, the cut representation is inaccurate. In this example, the slanted column (End Point Driven) was modeled in an elevation view from Level 1 to Level 5 and later stretched past these extents. A view associated with Level 1 (Fig. 1) was modified to have the same cut plane location and bottom plane as another view associated with Level 4 (Fig. 2). We expect the cut representation to be unaffected by the view’s Detail Level, however as you can see the column cut representation is incorrect when this is set to Coarse:
Fig. 1
Fig. 1

Fig. 2
Fig. 2
Also slanted columns, stairs and probably other categories, are not respecting the view’s Depth Clipping settings and are shown in full projection below the cut plane. Until this bug is resolved, please use caution and avoid setting your plan views to Coarse Detail Level when locating interior objects and equipment around slanted columns.