Thursday, 23 July 2015

Propagate Extents for Grids

An update to an older post...

PROBLEM: The Propagate Extents command in Revit for grids does not seem to work. Is it broken?
SOLUTION: Don’t waste your time changing grid bubble locations view-by-view!. The Propagate Extents enable to apply a consistent override of grid bubble placement across multiple views in the project.

But for this command to work, both the "source" view with the bubble override and the "destination" views should be parallel (i.e., horizontal level views, parallel elevations or sections), AND the cropping properties of the views should be disabled. The process is as follows:
  1. Prepare a single view with the grid bubble location as desired.
  2. Switch off the Crop View, Crop Region Visible, and Annotation Crop of the source view and all the parallel views you would like to apply the same grid bubble graphics:
  3. Select the grids in the "source" view, and in the contextual tab click Propagate Extents
  4. At the prompt of the dialog box, select the views to propagate the grid extents and click Apply.
  5. Return to the views and switch on the Crop View and Annotation Crop boxes.

Friday, 20 March 2015

Ensuring your families 'make the Cut'!

We all know family creation can be a tedious art, especially when you need an element (i.s. an under-mount sink) to cut into another object (i.e. a counter top), so here's a friendly reminder about how to set this up correctly:

In your family:


1. Ensure "Cut with voids when loaded"
2. Model the void extrusion(s) you need to cut the adjacent elements in the project
3. Load the family into your project


In the project:

4. select the element
5. Use the Cut tool (under Modify tab) and then
1st select the element to be cut
2nd select your cutting element (the family you just loaded)

And the result:




Tuesday, 20 January 2015

Troubleshooting Underlays in Revit

If you're experiencing problems displaying elements using the Underlay property of a Revit view, the feature just might be behaving as designed.

We recently had a team working on a high-rise project and they wanted to use the Level 8 plan as an underlay for the Level 5 design. In other words, using a level above as a reference for a lower level.

PROBLEM: The walls didn't show, but plumbing fixtures did. As a matter of fact, it seemed like anything that was supposed to be cut in plan view was not showing. We tried just about everything to fix the problem...changed the view discipline, checked the phase filters, and so on.

It turns out that the View Range settings are crucial to the behavior of underlays. If EITHER the host view or the underlay have the View Depth set so that the views 'cross' each other - cut object styles will not be displayed. This usually happens when View Depth is set to Unlimited.



While this seems to make sense for an upper level that uses a lower level as an underlay, it behaves the same way in the opposite. If the View Depth of the upper level includes the lower level within the view range, Revit thinks the elements are already being displayed and does not show them in the underlay.

Tuesday, 13 January 2015

Problem with Standardized Shared Parameters

It seems like a wonderful idea to develop an industry standard shared parameters file for Revit - but it all depends on how you develop the parameters and implement them. Should you set the standard without any special naming convention or identify parameters developed specifically for such a standard?

Antony McPhee provides some constructive commentary on the standardized shared parameters provided by the NBS (National Building Specification) in the United Kingdom over on the Practical BIM blog.

http://practicalbim.blogspot.com.au/2015/01/the-rudeness-of-uk-nbs-object-parameters.html

(Thanks to Cesar E. for the contribution)