Many Revit experts do not like to use this command because the end results can be very unpredictable. I figured it might be worth trying to make it more predictable by documenting its behaviour. But first, an analysis of why you might use this command instead of other methods of locking things in Revit - in particular Area Boundary Lines locked to walls:
Locking Area Boundary Lines in Revit
- When you first create an area plan, it asks if you want to 'Automatically create area boundary lines associated with all external walls?' - I always say NO to this because it almost certainly won't end up with what I want.
- Then when you start placing Area Boundary Lines, it assumes that you want to 'Apply Area Rules' - presumably these are USA based area measurement rules? It has a checkbox in the options toolbar that is always ticked. This drives me nuts as I always have to untick it, as I do NOT want my area lines locked to the centreline of walls
- I would normally use the 'Pick Lines' tool, so I can pick wall edges. At this stage you have the option to lock the lines to the wall edges so they will move when the walls move (in the Option Toolbar). Conventional Revit wisdom says that for Area Boundaries, you should not tick this box because you would end up with way too many explicit constraints in the model - any changes to the model have to check the explicit constraints, and if you have too many your model gets bogged down. In addition, any changes to the model that conflict with explicit constraints will evoke warning messages, and may even prevent you making the changes [the worst example of this is when sketch lines inside a floor or ceiling are locked to walls and impossible geometry stops you in your tracks].
- Using the 'Align Tool' and then locking Area Boundary lines to walls would have similar issues - way too many constraints, potentially hundreds for each area plan. Such locks should be reserved for a few very important constraints.
- 'Moves With Nearby Elements' is an implicit kind of locking - the relationship is controlled by a set of (somewhat mysterious) system rules, rather than a user defined relationship. However, the rules are not as simple as "moves with nearest appropriate wall" - it does depend on the order of placement or moving of elements, and also the timing of setting the 'Moves With Nearby Elements' property, so Revit must be storing some kind of information about "when" the implicit relationships came into being [it would be great if someone from the 'Factory' could comment]. I will try to explain this later.
But why not use the 'Moves With Nearby Elements' method? It could take care of the majority of updates without bogging down the model - making the checking process much faster. If you use this method, you need to understand the rules and bugs.
When to use 'Moves With Nearby Elements'Firstly, this functionality is wrongly named - it should be 'Moves With Nearby Walls', as that is what it does, and the Revit help file states:
"Use the Moves with Nearby Elements option to specify that lines and components near a wall move a corresponding distance whenever that wall is moved"
It is only available for certain Revit elements:
Revit help rather unhelpfully states that:
"Only straight lines that are parallel to a wall are affected by this option. It is not available for detail lines, sketch-based elements, and families" -
- what is the difference between components and families in this context?
- In fact it does work for parallel arcs (not just straight lines), as described in the next line of the help notes.
It does work for:
- some external families (components) - non-hosted only (but not all categories)
- model lines,
- Room separation lines,
- Area boundaries,
- Hosted external families (face-hosted, floor, wall or ceiling hosted etc)
- Work plane based external families
- Columns and structural column families
- Adaptive components
- System families (walls, stairs, railings etc)
- Sketch lines within system families
- In-Place families (even if they contain a reference plane), despite the fact that the properties palette has the check-box available (but option toolbar does not)
- Detail components or lines
- Annotation of any kind (symbols, tags, regions etc)
How to use 'Moves With Nearby Elements'
When placing an eligible component or lines, the properties palette will have a checkbox for 'Moves With Nearby Elements' - so you can set it before placing elements.
In addition to this there is a checkbox that appears on the options toolbar when you select an element that is eligible for this setting. In theory it makes no difference which checkbox you tick, it should apply the rules to the selected element(s). In reality there are some bugs to watch out for (see below).
To see what actually happens when you apply this setting, as well as my take on the rules that they follow refer to my post on The Rules
Bugs in 'Moves With Nearby Elements'There are three bugs in the software that I know of - each making this feature seem even more unpredictable in its operation:
In Revit 2013 and earlier, if you selected already placed elements and applied the setting using the checkbox in the properties palette (dialog box), then the setting just plain did not work. If you ticked the checkbox in the options toolbar, it did work. once applied there is no way of telling which checkbox was used. I reported this bug to Autodesk a few years back, and I notice that this has been fixed for most element types in v2014 and later.
I just discovered that in Revit 2015, the bug described above had still not been fixed for Area Boundary lines and Model Lines. I have reported this but it is not likely to be fixed for a while yet. The rule here is that you should either tick the checkbox before placing the Area Boundary lines, or else use only the options toolbar for selected area boundary lines.
Not sure if this is a bug or just a UI inconsistency - In-Place families have the checkbox only in the properties palette, not on the Options toolbar. Regardless of whether it is supposed to be there or not, the setting does not work.
For more information on this feature refer to other posts:
- Non-Hosted external Families
- Moves with Nearby Elements - The Rules