This page will be updated as more content is added to DynamoNodes.
You can find a detailed change log here.
Select Elements (ordered)
Select Linked Element
Select Linked Elements
Select Linked Elements (ordered)
Select Linked Face
Spring Nodes’ main focus is to improve Dynamo’s interaction with Revit. It’s wider goal is to explore any and all means that can help accelerate BIM focused work-flows. Many of the nodes use either IronPython or DesignScript and can be a good starting point for learning the specific syntax and finer points of both.
The package repository is posted on GitHub under the MIT license. You will also find all the sample files and brief descriptions there, that can further demonstrate how some of the nodes work.
Nobody likes squeaky springs. Therefore your recommendations and ideas on how to improve this package further are always welcome. Please be sure to report any issues or feedback directly to the repository.
Some of the nodes provided in this package have been sprung by existing content, such as the wonderful SteamNodes, archi-lab.net, Clockwork and LunchBox, because every great mechanism could use a spare spring from time to time. The aim is to always improve upon the original content either by enabling additional functionality or opening up new uses. By giving it a new twist, we avoid affecting the original content’s goals and direction.
This is a version of ‘All Indices Of’ that can handle null values in the inputs.
This node will get elements from a Link Instance given the instance object and a Category. It also reports a ‘coordinate transform’ for the Link Instance itself.
You also have the option to simply pick the linked instance with the “Select Model Element” node:
This node converts a Dynamo surface, poly-surface or solid into a Revit family. It then places an instance of that family inside your project, reflecting the geometry position from inside Dynamo. It currently supports Revit 2014 to 2016.
The most important inputs are:
- The geometry objects
- A file path to a family template (It is crucial that the family template version matches your Revit version)
- A unique family name for each geometry object
The optional inputs are:
- Category. The default value is Generic Model. Some templates, like the conceptual mass, do not allow changes to the family category. In those cases the built-in category will remain in force.
- Material of the family, provided as a string. The material must be pre-loaded into the template for this option to take effect. If a material with such a name does not exist in the template, the default “By Category” material will be used.
- Void switch provided as a Boolean ( true / false). The default value is set to false. If you provide a true value, the newly created family will act a void cut element and will be able to perform cuts on structural elements, generic model elements and host elements.
- Subcategory provided as a string. The default value is null – meaning that this option is ignored. If you provide a subcategory name, it will be generated inside the family document, applied to the family and added to the project together with it.
Do note that by default, the node works in “longest” lacing. That means that if any of the optional inputs are less than the geometry objects and the family names, the last input will be used for all remaining families. In the above image, the families at  and  will belong to the “Generic Model” category and will act as void cuts.
You can download this sample and others from the Spring Nodes repository:
Currently the node does not place multiple geometries into a single family. There is a partial workaround described in the following discussion:
A node for such cases might be developed in the future.