Dynamo Bug: Addition of input/output connection nodes when reloading script

Hello!

Since installing Civil 3D 2024 I have come across a bug in some of my dynamo scripts which were working fine in earlier versions.

Some nodes are now subject to a bug where when I reload the .dyn script, a new input / output connection node is created, rendering the script unusable. For example, the “Structure Label Styles” node should only have 1 output: structureLabelStyle. When reloading, the structureLabelStyle output is duplicated, generating an error. See image below for the correct node on the left and the buggy node (After reloading) on the right with the error message (as a new user I can only upload 1 image).

image

For the script to be usable again, I need to delete that node with the error and re-create the node with one output and re-connect to script, defeating the purpose of automation.

If I reload the script yet again, there will be 3 instances of ‘strucureLabelStyle’ output, and so on.

I notice this happens with Civil3Dtoolkit nodes but not with Camber nodes (although I could be wrong, it may be some nodes for each package). Anyone come across something similar and knows a fix?

After doing some research I found these links:

Dynamo 2.0 duplicates ports of custom node when file is saved and reopened? - Developers - Dynamo (dynamobim.com)

But it is not clear to me how to fix this bug. Could anyone explain what I have to do?

Hi @paul.cerceau,

Do you have any other packages installed? Or any Civil 3D plugins?

@zachri.jensen

Thanks for replying, I have Civil3Dtoolkit and Camber installed.

The only Civil 3D plugin I believe I have is the Infodrainage import / export to C3D plugin.

One more question, do you have Grading Optimization installed?

No I don’t believe so.

Please see below a snippet of all the Application Plugins that are installed:

image

Can you restart the CPU, recreate the issue, close Dynamo and post your Dynamo log file? I’m guessing we’ll see a line in there about a conflict in newtonsoft or similar shared component somewhere.

@jacob.small

Thanks for replying. Restarted CPU and recreated issue. Logs included below:
dynamoLog_0a545c7c-307a-4844-95e9-f3840414d006.txt (8.6 KB)

See lines 23, 24, and 65 for the likely root cause. Revit packages aren’t likely going to play nice in Civil 3D, doubly so when they target a different .net version than what you have installed (which I can’t confirm but I am suspicious of due to the reference to 2025 in the log).

Also check your Dynamo Settings for “packages to uninstall” which don’t exist anymore.

Do you have any idea of how I can fix this issue then please? I installed the archi-lab package in question yesterday after seeing a post on here that suggested it, nothing changed so I uninstalled it.

I only have Civil3Dtoolkit and Camber installed:

image

Check your package directory.

@jacob.small

Hello, this is my package directory showing only Camber and Civil3DToolkit:

image

Can you post your Dynamo settings file?

Sure, it doesn’t let me upload a .json file so here it is in .txt
TraceDataConfig.txt (101 Bytes)

Edit - there is also a settings.dat file within *\AppData\Roaming\Autodesk\C3D 2024\Dynamo\2.19\EBWebView\Crashpad, but I can’t upload, if this is what you want to see I can upload it somewhere else and share it.

need DynamoSettings.xml which should be in your c3d 2024\Dynamo\ folder.

Sorry, that folder doesn’t contain the DynamoSettings.xml file:

Ah - sorry. C3D is the only integration which uses a different path so it’s hard for me to keep up.

Try in 2.19 perhaps? If not navigate to %appdata% and search the hole folder via ctrl + f.

I appreciate your help! Found it:

DynamoSettings.txt (7.0 KB)

Check this folder for any remnants of Archi-Lab:

C:\ProgramData\Autodesk\C3D 2024\Dynamo\2.19\packages

If that doesn’t clear it out then we are back at checking your Dynamo log as the Archi-Lab bit likely cleared out and now we get to pull the next threads.