BimorphNodes v2.0 released

Hi fellow Dynamo junkies

I’ve just released bimorphNodes v2.0. There have been some significant upgrades since v1.5.1 and new nodes added! In addition, I’ve created a dedicated user guide with example files to support the package here www.bimorph.co.uk/bimorph-nodes

New Nodes added:

Nodes with enhanced features and major upgrades:

All other nodes have been upgraded.

Here are some highlights: CAD.CurvesFromCADLayers The node has been upgraded to convert DWG or DGN Links or Imports in any view. In previous versions, only the XY plane was considered which meant section or elevation views were not supported. There is also a new input lineStyleMap which enables Lines Styles to be mapped to each layer during the conversion process for even greater workflow flexibility.

Curves.RemoveDuplicateCurves You can now remove duplicates from a list of Curves. This node supports Dynamo Curves, Revit Model or Detail Lines. Revit Curves have the optional inputs to delete any duplicates from the document and input LineStyle names can be used to retain the duplicate curve of that style.

To simplify model element selection in Revit when using the Dynamo Select Model Elements node, heterogeneous lists (any Revit element type) can be input as the node filters the list for curves before processing.

Sheets.DuplicateSheets DuplicateSheets has been upgraded significantly from previous versions. All view types are now supported, and if illegal characters are found in the view names (such as {3D} for example) they are cleaned to ensure the process doesn’t fail prematurely. In addition, any sheet annotations including dimensions, Symbols, Detail Lines and groups are also duplicated when the duplicateView input is set to true.

Lastly, the algorithm which controls the duplicate behaviour has been upgraded following this post. So in v2.0, whenever a dependent view is found, a new parent is created first, then the dependent is duplicated from this parent to maintain the existing view structure. It’s ‘clever’ enough to also check if the parent exists on subsequent runs to handle the possibility that it already exists should other related dependent’s be duplicated.

Check out the package and let me know if you spot any bugs, want to suggest improvements or have more node ideas!