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.
Goos 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.