It seems that the bug preventing the drawing of area boundaries within an area boundary group has been resolved in the latest version of Revit. However, I’ve encountered a new issue that still makes the area boundary group somewhat unusable.
We are working with an organic-shaped building, which makes it difficult to trace the boundary multiple times for different area schemes. To address this, I created an enclosure area boundary group and copied it into three area plan schemes (Gross, Rental, Egress). This worked fine initially, but when I add a new boundary line to the group in, for example, the Gross area scheme,
- I encounter the following warning: "Highlighted lines overlap. Lines may not form closed loops. You can tab-select one of the overlapping elements to exclude it from the group instance."
- The newly added boundary line appears three times in the Gross area plan but is not visible in the Rental/Egress area schemes' group.
I believe this is due to area boundary lines being somewhat view-specific, as once they’re created, they are locked to the current view—similar to the behavior of linked CAD files with the "current view only" setting.
However, copy/paste can alter it's view specific value and it's my current workaround:
- Delete all the groups, leaving only one instance in Revit (get a lot of area not enclosed warnings for sure).
- Add boundaries to the group.
- Re-copy the group back to the other area schemes.
This process works, and all new created lines are visible in the group in the plan where they were copied to.
However, it's def not ideal. Every time I want to add a new boundary to the group, I have to Repeat this process, and if you can imagine, just when you completed the process and finished copying them back, you realize you need to add one more boundary.................all over again.
The area boundary group would save us a significant amount of time if we could avoid tracing the same boundary in each area scheme—especially in cases like this with complex building shapes.
Could Autodesk please look into this issue?
Thanks so much for your help!
Best,
Li