The shared nested elements also display in the project browser, while non-shared nested elements don’t appear at all. We can select the shared nested elements, tag them and schedule them. Setting them as Shared allows us to tag and schedule them in the project. Chairs and a table can be nested into the same family. On the other hand, regular (non-shared) nested families should be used to aid in the creation of repeated elements when creating Revit content.Ī good example of when it makes sense to use shared nested families is the one mentioned above: chairs and a table being nested in a furniture system family. The best way to think about it is that you should use shared nested elements when those elements could also be used on their own within the project. Families can be set to be shared in the properties dialog.
JANOD OWLY NESTING FAMILY FULL
By making the chairs and table as shared nested elements of the family, we get the best of both worlds: ease of placement within the project, and full functionality for the information contained within the nested families. This is where shared nested families come in. But if we do this by nesting chairs and table within a Furniture System family, we wouldn’t be able to count those chairs independently at a later stage. There are also situations where placing a set of families together would be very convenient, for example a table and its surrounding chairs. There are many use cases for nesting Revit content, such as use of repeated components or parametric elements in an array. Nesting in Revit allows us to place families within other families in order to display their combined geometries and make them behave like a single unit within a project. A look at the behavior and benefits of shared nested families in Revit and when it makes sense to use them.
0 kommentar(er)
