It sounds like another namespace clash. Try uninstalling all packages - only install SpringNodes…and it should work. A similar issue was reported here:
Its most likely caused by a namespace clash between DesignScript and an external library. Unfortunately, fully-qualifying the class in DS doesn’t solve the problem. Instead, try un-installing your packages and it should work as expected:
https://github.com/DynamoDS/Dynamo/issues/7697
FYI @Zach_Kron @Aparajit_Pratap The issue of namespace clashes with packages had cropped up a number of times recently and appears to be on the rise
opened 06:05PM - 09 Mar 17 UTC
closed 05:08PM - 29 Nov 18 UTC
priority
tracked
## Dynamo version
1.2.1
## Operating system
Win 10
## What did you d… o?
Ran a script with approx 2k lines of Imperative DesignScript.
## What did you expect to see?
The script to execute (its been in use successfully for months)
## What did you see instead?
The graph is completely unresponsive and the cause is a clash with Archi-labs `List` class. This is what I narrowed it down to, and so I added DSCore.List to all `List` objects in my DS. It still doesn't solve the problem. My only option is to completely uninstall Arch-lab package, but its distributed across my clients office and relied upon by a number of their users so I can't use this as my solution.
Considering these clashes cripple Dynamo graphs, the purpose of reporting this issue is to suggest a more robust approach to DesignScript libraries and third-party libraries to prevent this from happening.
If you need the example DYN to run tests, I can provide one.
1 Like