Thursday 12 May 2016

The 8 Worst Things You Can Do In Revit

The 8 Worst Things You Can Do In Revit

1. Never leave inserted AutoCAD DWGs in a Revit model. Although you can insert a block or drawing into Revit it can cause severe performance and stability issues. DWG files bloat the model by using far more memory than pure Revit entities. If the AutoCAD file is necessary as a background, linking the file in rather than importing it can prevent and reduce some of these issues.

2. Don’t let unresolved Revit warnings languish. Large numbers of unresolved warnings can seriously degrade model performance and stability. Resolve warnings as they occur to keep them from building up in the model. Periodically check the “Warnings” tool on the “Manage” ribbon to see what warnings (if any) have built up in the model.

3. Don’t use Revit Families from Manufacturers without checking them first. Building Product Manufacturers are responding to your requests for Revit content by having families of their products created in Revit. These families may look great when viewed, but if they contain too much detail they can quickly bloat your model.

4. Don’t over-model. One of the most common mistakes among new users of Revit is to put too much detail in the model. Determine how much detail is really necessary to convey your design intent, and then monitor your team to prevent over-modeling.

5. Don’t use in-place families too often. While it is inevitable that you will have to use in-place families in a typical project, be selective in their use. If you create an in-place family and later decide that it should be a component family, there is absolutely no way to convert it. If you must use an in place family, do not duplicate it. For example, if you have to use in-place families to create light coves in several rooms, create them all in one in-place family; don’t create a different in-place family for each room. 

6. Don’t over-constrain model geometry in a project file. Dimension and alignment constraints add overhead to the file and increase the potential for the dreaded “constraints not satisfied” error message. If you’re not absolutely sure that you should constrain something, then you probably shouldn’t.

7. Don’t lose control of your views. Exercise good view management. Don’t create unnecessary views and don’t leave views unnamed. During the course of a project, the project browser can become populated with a large number of unnecessary views that add to file size.

8. Don’t over-use Groups. An inordinate number of groups in a project can impact performance and bloat the model. Make sure to purge unused groups from the model regularly and turn off the “Group and Associate” option when using the Array tool. 

I found #5 :-)


  1. Very true.
    But I was wondering what happened to no. 5? Was there a no. 5 of is it supposed to be "The 7 worst things"?

  2. I dont know what happened! I'll look for #5.