A couple of months ago I’ve made a Sneak peek into Dynamo 2.0, showing you some of the upcoming changes to the “Next gen Dynamo”. And now that Dynamo 2.0 has finally arrived, you can do the following:
- Read the official release notes here: To Dynamo 2.0 and Beyond.
- Download Dynamo 2.0 release version from the official repository @ DynamoBuilds.com
- Back up your existing Dynamo library:
- Completely uninstall Dynamo 2.0 pre-release build if you have one.
- Install Dynamo 2.0 release version and play with the new features.
Please note that there are still some issues with this release
(see this page @GitHub for reference: dynamo known issues):
- Node library search may not work properly (GitHub issue 8757 & GitHub issue 8769)
- Dynamo 2.0 has a conflict with Revit 2018.2’s and 2018.3’s (GitHub issue 8768) implementation of P&ID Modeler (thanks jmmkm for the tip in the comments section below) resulting in the library/browser now showing. This issue is not present in 2018.1
, or Revit 2019 . If you want to use 2.0 with Revit 2018.2 or 2018.3, you will need to remove the the manifest file
C:\Program Files\Autodesk\Revit 2018\AddIns\PnIDModeler\PnIDModeler.addin
- For custom nodes, using dot-notation in node Names or Categories will result in additional nested sub-categories. The “.” will work as a delimiter to determine the additional hierarchy. This is new behavior in the library for Dynamo 2.0.
- If the network drive pointed to by “Manage Node and Package paths” is > 1TB in size loading Dynamo may take a minute or more, irrespective of actual package size. We recommend drive size of 100GB or smaller.
- Toggling the freeze state can cause a node to be executed twice after editing a Code Block Node.
- Installers fail to prompt for missing VC++ components which causes Dynamo to silently crash at load time
- Packages that deliver DynamoServices.dll may have corrupted multi-output port nodes; instead of multiple output ports, they will be collapsed into a single output port.
- Some JSON graphs may open and erroneously appears to have unsaved changes as shown by the asterisks in the workspace tab.
- If your workstation contains multiple major versions of Dynamo, e.g, Dynamo 1.x and Dynamo 2.x, Dynamo Player will start with whichever version you select for Dynamo for that session.
- Custom node libraries that contain the same category and node names result in unexpected library organization.
If this list of known issues is not critical for you, feel free to be an early adopter.