Its easy and it only takes 2 nodes but the naming found within each node could be very confusing. So first add a Family Type selection node, select the family type, and then wire that to either the FamilyInstance.ByFamilySymbol or All element of Family Type node and click run...
THATS IT!...Well...there is still the issue of the naming....
This process is summarized in the image below and notice... from the image it is clear that the nomenclature used in DynamoBIM is very confusing because two different words could mean the same thing...
The question is....why is DynamoBIM like this? I have no idea.
Stay tuned to this blog....
I will try my best to help clarify confusing naming conversions, in future posts, as I encounter them.
2 comments:
Normally the names of the nodes you see reflect the names of the objects and methods in the Revit API.
This may help clarify:
http://help.autodesk.com/view/RVT/2014/ENU/?guid=GUID-26DDC06E-9E66-467A-AF71-23DF24666C16
I understand but at the very least the naming should be consistent.
If its called Family Symbol because of the Revit API so be it...
then call it Family Symbol everywhere in every OOTB Dynamo node....
If it was changed to Family Type then call it Family Type everywhere in every OOTB Dynamo node...
Same with instance and element
just my two cents
Post a Comment