There is no preview in Dynamo though the PolyCurves are correctly converted to Polylines in Civil 3D.
Creating a new graph and build it with these exact nodes result in a working graph. But I can’t use any graph created in 2.13. It is not the first time that an update breaks with previous versions :-
A bit deeper testing, I get a dialog when I open a graph. A message is shown that the installed Civil3DToolkit version differs from the one that is used in the graph. When I close the dialog without further action, I get these laces and empty Code Blocks issue. Also when I save the graph and reopen it, the laces and Code Block issue is still there (and still the warning about a different version).
When I explicitly check that I want to keep the installed version, save the graph and reopen it, then the graph is fixed.
I don’t think the issue is the Civil3DToolkit. Just tested, with any other package it is the same. If I don’t press the button to keep the current version, save the file and reopen it, the lacing and Code Blocks issues occur. It is weird that I have to reopen the graph before the fix is shown.
Also the message does not show the installed version:
I have to visit the Preferences dialog to find the Package Manager to find out that I have 1.1.32 installed instead of 1.1.30. It would be nice if the next Dynamo version will show that too in the dialog.
Another issue: Even if I don’t do anything in a graph, Dynamo claims that is has unsaved changes and wants to save it. I am not sure if that was always the case but I see it now.
Often just running a graph can cause a need to ‘save’, due to the way element binding works, though this may be different in Civil 3D, depending on how you have configured the setup.
Interesting… Something else marking the graph as ‘dirty’ when you open it. Could be a configuration or something unique top the graph… Certainly not a big issue but I’ll see if I can reproduce it later today all the same.
Start a new graph in Dynamo, add some nodes that refer to the document and run the graph
I know I shouldn’t do this, but normally Dynamo will show a red warning next to the Run button, now it only shows an orange warning. This error also occurs in earlier versions of Dynamo.
Another bug that only occurs in Dynamo 2.15 and Civil 3D 2023.2, I receive a Fatal Error when closing Civil 3D before Dynamo. In earlier versions Dynamo shows a save message on closing. Now when I close Civil 3D while there are unsaved changes in Dynamo, there is no such question but a Fatal Error instead.
Custom Nodes can’t be created anymore. If I start from scratch, I can save the Custom Node to a DYF file, but as soon as the automatic backup process starts, the Custom Node file name is replaced with ‘backup.dyn’ and from that moment it only saves to the backup file.
@Anton_Huizinga I am trying to reproduce this issue of the broken code blocks / floating connectors when you have conflicting package versions and so far - I cannot reproduce the issue.
Can you provide the graph, and supporting files you were testing and any info on any addins you had installed or still have?
Can you still repro the issue?
Also - what specific 2.15 version of Dynamo were you using here? I tried in 2023 -Dynmao 2.13 and 2023.2. with Dynamo 2.15.
Hi @Anton_Huizinga thanks for the files.
I can recreate the conflicted package situation, but cannot reproduce the visual artifact.
I have also enabled run preview to match what you are showing, but so far everything seems fine.
I will need more information on what addins you have installed. Have you reproduced this with only a single package installed or do you have multiple?
one thing I notice @Anton_Huizinga is that your screenshots display the Autocad logo - I have started up using Civil3d metric - I am not a regular ACad/C3D user - so I don’t know what to make of that.
Have you started directly in ACAD or modified your installation somehow etc?
Is there a specific way I should be starting up to reproduce your environment?
I only have C3DToolkit, Camber, Arkance Systems Node Library and Monocle installed as packages. I will test with only one package. It does not happen in other Dynamo versions (C3D 2022 or 2021), which are configured the same way as C3D 2023.
