when I update civil 3d from 2024 to 2025, a problem occurs. The nodes in Civil 3DToolkit are all missing (installed with the same Packge version Civil3dToolkit 1.1.32). So what is happening here and is there a solution? Please help me!!!
In civil3D 2025
yes, it does not work well with c3d 2025.1 and up due the expansion and rearrangement of the node library.
Lots of Toolkit nodes were adapted in some way, but lots are missing.
I suggest you to check The Civil Nodes from @Anton_Huizinga. That has some of the missing nodes.
@jacob.small @Anton_Huizinga
do you know this problem and you can help me?
Issues with civil 3d toolkit and civils 3d 2025 are know and posted on this forum, the main cause is that the package is now unsupported. This means it will not get any updates, this can be found from this post
Future of Civil 3D Toolkit and Camber Packages - Civil 3D - Dynamo
Therefore your only options are see if there is a OOTB node now, code something in python your self, create your own package or try to see if “The Civil Nodes” package could replace what you wanted.
@zachri.jensen
I have read about this issue and found that the change is too significant, causing some user packages to break. In my opinion, when Autodesk introduces major updates like this, it would be better to consult or notify developers in advance.
From Civil 2025 to Civil 2026, there seems to be no clear information on the changes, making it difficult for developers to keep up. This has a considerable impact, and as a user, I may be forced to revert to using the 2023 or 2024 versions just to keep my work running smoothly.
It’s regrettable.
Hi @v.v.khu,
I hear you. Change is hard, and there was a lot of change between Civil 3D 2024 and 2025, not only for Dynamo but also the transition to .NET 8 across the portfolio. It has been a pain point for many users that the Civil 3D Toolkit package was not updated to support these changes. Unfortunately I can’t assist further on that topic because, apart from a handful of packages maintained by the Dynamo team, everything else on the package manager (including the Civil 3D Toolkit) are third-party add-ons and are the responsibility of the respective authors to provide support and maintenance.
Regarding documentation, you can find that in our release notes (thanks also @kovacsv). Hopefully that helps:
If you’re not already registered, I would encourage you to participate in our beta program via feedback.autodesk.com. We provide information about upcoming changes so you can be in the loop and test them out in alpha/beta releases. Anything related to Dynamo is also included under that umbrella. There is also a weekly webinar series that you can sign up for to get near real-time information about what we’re currently working on.
I’ll close by saying that introducing so many new nodes in a point release is not ideal, and it wasn’t our original plan. Unfortunately there were some snags that prevented us from releasing them in the 2025 major version as originally planned, but that’s all the detail I can share on a public forum.
One more comment…
If there are some specific technical issues you’d like help working through, feel free to reach out via DM and I’ll help where I can. I’m optimistic we could get you up and running in Civil 3D 2025 or 2026 without too much hassle 
I would also suggest you see this too - Civil Infrastructure Roadmap - AEC Tech Drop
The .net 8 upgrade was indicated on the roadmap prior to 2025 release and was indicated in 2023 - https://portal.productboard.com/jepvxreqkffwuku66cnkvxke/c/429-civil-3d-and-extensions-net-8-0-port-2025-0?&utm_medium=social&utm_source=share
Just remembered that there was a post on the dynamo forum about the move to .net 8 and its impacts on packages.
