General Schema:
This workflow assists in the creation of the .JSON file which DynoBrowser needs to set up the presets avaliable to the Revit users.
It uses the three Dynablaster Package nodes:
DynoPresetInputGenerator, DynoPresetGenerator and Dyno.JsonGenerator.
The author of these nodes is no affiliated with DynoBrowser developer. Refer to http://dyno.arcprojects.ru/ for more information
This is the last of three nodes. See the first and the second before reading this.
Refer to the workflow post for further details.
This node gets a Preset or a list of Presets, and builds the content of the json configuration file.
The author of these nodes is no affiliated with DynoBrowser developer. Refer to http://dyno.arcprojects.ru/ for more information
This is the second node of a group of three. Go to the first one before continue reading.
Refer to the workflow post for further details.
As an input will take the preset name, and the input or inputs of that preset.
If more than one input is desired, they need to be grouped as a list and then connected to he “Preset Input(s) node port.
This custom node contains a python node inside.
The author of these nodes is no affiliated with DynoBrowser developer. Refer to http://dyno.arcprojects.ru/ for more information
This node is the first of a group of three nodes. They are meant to help with the creation of the preset file, which is a .JSON file.Refer to the workflow post for further details.
With this node, you define an input.
It has three inputs; Name, Value and Description. The node will look for the data type and write it accordingly.
The string creation is held by a python script node:
You can define more than one input, and lace them together into a list and pass it to the next node, which is DynoPresetGenerator.
The author of these nodes is no affiliated with DynoBrowser developer. Refer to http://dyno.arcprojects.ru/ for more information
In large models, Revit can be agonisingly slow to regenerate when trying to draw a new Section View (it is usually trying to detect the required view depth). This node was created to quickly make section views by selecting Line elements in Revit. Here’s how to use it:
1. Open a Plan where you can see Revit Lines
2. Open Dynamo
3. Place the Revit Section View at Line node
4. Set desired View Depth (Far Clip Offset)
5. Set desired View Height (the base of the section will likely be Floor Plan level, with top of the section based on this value)
6. Set FlipSection to true if you want to rotate the plane through 180 degrees (effectively flipping the section)
7. Use “Select Model Elements” or a similar element collection node or method to feed a list of Detail Lines and/or Model Lines into the revitLines input
This initial version has been set up for Sections intended to be visible on Plan views, and will not work in other planar situations (such as running from an Elevation). Future versions could look at working on any Line in any view, and possibly allowing any plane Rotation (such as 90 degrees for perpendicular sections).
Note: you may have to press Run twice to make it work, depending on your version and system?
This screencast shows the node in action:
https://knowledge.autodesk.com/community/screencast/e316f8ef-9bab-4857-be9d-8562191a0024
Running from a workshared model, this node will take an element list and a target parameter name, and it will get the Workset name for each element and write it to the target parameter.
Using a selection of nodes to gather the parents of given Parts in the Revit model, we can also get parameters or properties from the Parents and write them into the Parts themselves. For example, we could obtain the Level of the linked Parent Floor Elements for a set of Parts, and then write that into the Comments parameter of the Parts themselves.
The images below show this idea in action:
This node takes a list of Parts, and one string to search Link names for. It then gets the first parent from each part, and attempts to obtain the actual Revit element from either the current (host) model, or from the Link document matching the string input. With a bit more work, this node can be extended or replaced by a new version that handles parts from many different source Link documents.
This node takes two matching length input lists. It scans the primary list to clean for null values, and then attempts to replace those null values with matching items from the backup list used for null replacement.
This node will take a single Document object, and list of Element Ids, and attempt to get the corresponding Revit elements. It can work on the current Document, or for Linked documents.
Dynamo Nodes 