It is common to have openings in walls that are not of a consistent width all the way through the wall. An example of this is when a door is recessed into a brick wall and the brick opening is wider than the stud/masonry wall opening or the door. The following illustration shows a door opening in a stud and brick wall with the brick opening wider to allow brickmould casing around the door.
Revit doors and windows, by default, have an opening that goes straight through the wall with a completely rectangular opening. If you just use the default Door.rft or Window.rft with the default opening to create your doors and window families, you will not see the above jogged offset opening.
The secret to getting the walls to cut as you desire is to NOT use the Opening Cut that is in the family template, but use Voids instead.
Revit has three Detail Levels that can be assigned to a view, which are Coarse, Medium, and Fine and these control how much detail is shown for model elements in the view. When assigning the Detail Level, everything in the view gets assigned that Detail Level by default throughout the view. However, there are times when you want to have different Detail Levels for different categories of model elements in the same view. There can be various reasons for this, but a couple of examples are:
You want some information to display more detail than others to accent certain items, such as only wanting walls to display the outer wall lines (Coarse display) while information such as furniture in the room shows a high level of detail (Fine display).
As a consultant and trainer, I work with many people that are currently working with AutoCAD or transitioning to Revit. I am constantly amazed at the number of architectural users of AutoCAD that are not aware of detail components within AutoCAD Architecture. These components can be an important part of drafting the many details that are part of an architectural design office. Over the years, I have spent many hours drafting details for construction documents and I think of the advantages of having pre-made components available to me for detailing.
I was recently asked about instance parameter grips for a Revit family that was placed in a Revit project file. The family had an instance parameter in it for a dimension and the user was expecting to see grip arrows so that they could manually adjust the size by dragging the grips. The arrow grips did not exist and the user was curious why that was the case.
The answer to the user’s question is actually very simple. When creating a dimension that will be referencing an instance parameter, it is important to dimension between two Reference Planes for the grip arrows to appear.
Occasionally, you need to create an arc in a Revit family and you know 3 points of the arc, but not necessarily the radius, and you need it to be flexible. It is common for windows with a radius top to have this situation. You know the chord length (width of the window) and the distance from the top of the straight sides to the top of the window arc, but not the radius of the arc. Revit requires you to specify the radius and center point of the arc to allow it to be flexible, so it is important to determine that information.
Anyone using Revit realizes that families are a key component to effectively using the software. Creating quality families are very important to a good quality Revit project, and an important part of a family are the parameters. Parameters within the family can control information and flexibility of not only the family, but also “nested” families. A nested family is another family that is inserted into the primary family in which you are working. It is common in some families, such as door families, to utilize a nested “profile” family to control a sweep for something like a door frame. Passing parameter values to a nested profile family is different than other nested families, so this article specifically addresses passing parameter values to a nested profile family.
Autodesk Revit contains both Reference Planes and Reference Lines, but it seems that most people do not understand or utilize Reference Lines. While Reference Lines are used as control lines for information within a family similar to Reference Planes, they are not a type of Reference Plane. It is its own type of object designed for a separate purpose. Basically, you should use Reference Lines instead of Reference Planes when you need defined endpoints for a work plane. A prime example of an important Reference Line usage is for allowing for the rotation of objects within a family. A general rule is that if you want something to rotate, use a Reference Line to control it.