Just Camber and Civil3DToolkit.
I just recreated the issue again and generated the log below:
Ok - at this point the Dynamo log is indicating that Dynamo isn’t having any issues, which is expected when another add-in has loaded a conflicting version of a referenced library. Disable all your Civil 3D add-ins (i have no idea how to do this as I am not a Civil 3D or AutoCAD user, so you’ll have to google that and let us know what the successful process was) and see if that fixes it. You can also reach out to my colleagues in support and see fi they can give better direction or even do some remote troubleshooting with you by submitting a ticket at manage.autodesk.com.
Tried disabling all add-ins and Civil 3D 2024 crashes. I have done individual tests but it seems no matter what I try, Dynamo in Civil3D 2024 has this bug.
I tried running the exact same dynamo script on the same .dwg file using Civil3D 2022 and it works perfectly fine with no bugs, so I assume the issue lies somewhere within Civil3D 2024. Does this help at all? My team is transitioning to the 2024 version and I want to make sure the scripts run properly.
This indicates something is amiss with your add-ins or Civil 3D configuration. You’ve got to correct that before bothering with any Dynamo configuration as until that’s cleaned up Dynamo won’t work consistently. This will impact not only you but all others.
Only to confirm that you’ve got a setting issue in Civil 3D to deal with.
Time for you to reach out to support directly as indicated above as otherwise I’m at “start a brand new user profile” territory as troubleshooting add-ins is beyond me. Once the technician helps you get the add-ins disabled and stable they can help troubleshot the Dynamo issue.
I have submitted a ticket to Autodesk. Hopefully they know how to fix this issue, if they do, I’ll make sure to come back here and share the solution.
if they don’t myself and Zachary will likely be flagged internally. 