There is a colossal movement behind the scenes to move the AutoCAD and Civil 3D platform to a modern-day framework. I love this! The APIs and systems need work. However, there needs to be a curator for existing nodes. I am thrilled that the new Civil 3D 2025 has added (700?) nodes. However, Dynamo is broken if you refuse to document existing nodes adequately or update outdated nodes. Users and engineering teams require consistency. Updates should absolutely not break ‘agnostic’ code. The strength of Dynamo is to relate to the database from an outside standpoint, DWG or Dynamo versioning should not come into play here. The instance of Dynamo has enough data to recognize the env and adapt if required. I see architecture teams embrace Dynamo through the BIM systems of Revit, Civil 3D is not Revit. A consistent, repeatable programming language is what the typical engineer is looking for. 2024 vs 2025:
Hi @bearle,
It looks like the node shown in your example is from the Civil 3D Toolkit package. Am I correct in assuming that this is mostly what you’re referring to in your comments above about backward compatibility between versions?
That is a node sorted under Autodesk \ Civil 3D Toolkit \ AutoCAD. Correct. The crux of the complaint is that core functionality for a Toolkit node has been sunset without notification.
Compatibility and documentation.
The package has not been actively maintained for several years, and last I heard the original authors have moved on to other projects and no longer support it. You may consider reaching out to them for more information. Here is the feedback thread:
Regarding nodes available in the core product, there are a handful of nodes that are planned for deprecation in the future. When placed in the workspace, they currently show an Info message with a recommendation for a replacement node (example below):
The full list of nodes planned for deprecation can be found in the documentation here.
This blog post may also be a helpful resource regarding new features and changes for Dynamo in the Civil 3D 2025.1 release.
No need to reach out. The statement here sums it up: Future of Civil 3D Toolkit and Camber Packages - #39 by Paolo_Emilio_Serra1
Thanks - forgot about that one.