Creating your own nested and shared families and using them within RevitHQ families is a simple process that requires only a basic understanding of the family creation environment. However, there are some important rules to follow to ensure the process is seamless. In this guide we will be using the RevitHQ door family as the example, however the same principle and process applies to any category within Revit. Please note that this guide assumes you know the basics of correctly constraining geometry to reference planes, and creating parameters to control these reference planes, it is not intended to be a tutorial on the family creation process. If you are still having trouble with the creation of your own custom families after following this guide, feel free to contact us and will endeavor to help you with the process.
|
|
|
|
Additional NotesIt is not essential that you constrain your custom family to the reference planes, this will of course mean that it is not parametric, but not all designs need to be, and very complex designs are difficult to constrain to begin with. The important factor to remember when not creating a parametric panel, is that the RevitHQ door family won’t be able to detect its size. If you set the family too small, the panel will protrude through the frame, and too big, the opposite. You will need to manually adjust the width and height parameters to fit the size of your new door panel.
Good Practice
|
Important Notes
- Never change the origin of a nested and shared family. Host families rely on the origin of the nested family to constrain its position. Altering this will lead to an error with the family 99.9% of the time.
- Never change or delete the instance parameters of a nested family, even if your family is not parametric or you don’t need them for your families design. All pre-set instance parameters in RevitHQ families have been linked in the host family. If a nested family without these parameters is swapped into the host, the association will be lost and will most likely end in an error.
- Be careful when switching the nested shared families in the type properties, if the wrong family is swapped in, your family will quickly result in an error. If this does happen, just cancel you changes and switch to the correct nested family.