View Ranges (and TOLERANCES) Explained *REPOST*
Things like –
Walls shorter than 6 feet (approximately 1.83 meters) are not cut, even if they intersect the cut plane, and
There are a few categories for which an element located above the cut plane but partially below the top clip is shown in plan. These categories include windows, casework, and generic model. These objects are shown as viewed from above.
Most of us use the old Reference Line with angular dimension method to control rotation in our vanilla Revit families.
However, Marcello Sgambelluri has posted three alternative methods to control rotation and angular dimensions, with full step-by-step instructions, at his blog Simply Complex.
Marcello says: I have given three rotation rig methods that do not use the angular dimension parameter in these last two postings. These methods are the Ride the Rail method, the Open Reference Circle method, and the Revolve method.
Here is what we want – you select an in-place family and click ‘Convert to Component Family‘ on the Ribbon. Through API Wizardry, the following happens without any further user interaction:
The family is edited in place
All objects in the family (including reference planes etc) are selected
A ‘group’ command is triggered
The group is saved (as a file) to a temporary location (it will be an RFA)
This family is loaded back into the project
The family is placed in the correct location (XYZ) in the project
The original in-place family is deleted from the project.
This can all be done manually of course, using the workflow described here.
I’m sure that many users would find this tool helpful, and for some of you advanced Revit API programmers, this utility should be a piece of cake!
Also: if you release this utility for free, just think of the Revit API street cred that would give you.
Finally, if you want to take it to the next level – make a Batch Convert option, that allows the user to ‘pick’ which In-place families (from the current project) that they would like converted, after which the Batch tool goes ahead and does steps 1 to 7 above on each and every in-place family you selected.
Nice tip on formulaic materials: How do you parametrically change a material parameter in a family if the material itself depends on factors outside of each type designation? After all, it’s impossible to control materials through formulas. Our approach (when the number of ‘stacked’ geometry instances is few) is to model separate pieces of geometry, apply their unique material and then control their on/off visibility through parameters.
How to provide error messages to the family user: One solution to this perplexing problem is to include 3D text displaying a message to the user when a non-existent configuration is selected.