I have been running into issues with my dynamo node packages since I downloaded Orkestra for use in Civil 3D (2024). My Dynamo nodes have been looking like the snip below since I downloaded Orkestra. I was told on a post in the Dynamo forum that it is likely due to conflicting loading of the newtonsoftJSON (see that post here). Is there an easy way to resolve this? I have the most recent version of Orkestra (v1.8.3).
1 Like
Hi there @cdsouba ! Thank you very much for reporting this.
We were made aware that this was happening because of an interaction with the Civil Toolkit package. I does appear to be linked with the newtonsoft dependency.
Good news is that we got rid of that dependency in 1.9.0 which will be release in a near future. I’ll update this thread so we can check whether that solved your issue .
1 Like
Thank you for the reply and action! Is there an estimated timeline on this update?
Current target is sometime next week for 1.9.0 !
1 Like
I see the pre-release information for 1.9.0 on the Orkestra site. It looks awesome! Any updated on when this will be publicly available?
It’s already publicly available ! You can download it from the website and try it out. It would be awesome to see if our efforts have solved your issue and let us know.
We’re giving the pre release approximately one month before we push the “official” release.
I missed the assets tab on the bottom of the pre-release page. I will check that out and let you know if I run into any issues. Thank you!
1 Like
@m.elayoubi When using the new version of Orkestra, it is not loading in my Civil 3D.
hey @cdsouba ! 1.9.1 is out with a fix for the civil addin not loading.
Please let me know when you get a chance to try it out.
@m.elayoubi I downloaded it yesterday and it works much better! Thank you for your work on this. This is a great tool. I will let you know if I run across any issues with it as I spend more time using it.
1 Like
woohoo!! 
thank you very much for the update.
Hey @m.elayoubi! Someone we have set up with Orkestra is running into the broken nodes error that I originally posted about. This is causing the Dynamo script to not run in Orkestra or Dynamo. Civil3DToolkit version for the script is 1.1.32 and Orkestra is the latest version (1.9.8) for reference. This seems like a one off for this user, but I am curious if you have any thoughts on what could be causing this and if it could be a conflicting of a dependency.
Hi @cdsouba !
Is it still the exact same issue with duplicated inputs / outputs?
Which version of Civil 3D is this happening in?
We haven’t introduced any dependency ever since this was resolved (especially newtonsoft which was responsible for this in most cases).
It is the exact same issue as before with the doubled inputs and outputs.
He is using Civil 3D 2024.
There is a chance it is coming from another plugin but none of his other plugins interact with Dynamo. Could another plugin that has the newtonsoft dependency cause the issue even if it is not interacting with Dynamo?
I’d say yes. If another conflicting newtonsoft is loaded in civil 3ds appdomain then it might interfere with Dynamo, even if the functionality of that plugin is not in Dynamo.
I’ll double check with the setup and versions you shared though to make sure Orkestra is not interfering in any way though.