Dynamo Crash 'Manage Node and Package Paths' ?! :-S

dynamo

#1

Hi,

Dynamo (2.0.2) and Revit (2018) keep crashing when I add packages with ‘Manage Node and Package Paths’
Settings -> Manage Node and Package Paths -> (Select Folder)

Testing on two different computers, I have tried to regroup the packages into subfolders and adding them one by one and them removing the crashing package. When I bundle the packages into a single folder and try again Revit and Dynamo crashes. -.-*

Here’s the initial list of packages I’m trying to add:

archi-lab
Bakery
bimorpNodes
Clockwork for Dynamo 2.x
Data-Shapes
DiRoots
Duct Tape
DynaTools
EvolveLAB-Beaker
MEPover
MeshToolkit
Orchid
Rhythm
spring nodes

Does anyone have any suggestion what to do?


#2

Confirm all packages were originally written for 2.x. Check the file format (json vs xml) as a starting point.


#3

@Thomas_Perkov,

Try also to add one package at the time to see which package fails…

You should also verify that you dont have more paths than expected. Example do I have all packages dedicated to Dynamo 2.0 in one folder and all non-dedicated packages (for 1.3 and 2.0) in a “common” folder.

image


#4

Hi Jacob and Erik,

Thanks for the quick replies.

I didn’t check the format (jsom/xml) though I specific looked out for 2.x so that should have done the trick I guess. I also tried to ad packages one by one on two different computers in parallel…

I found a solution earlier, just before I went out the door, sorry for not posting it:
- Close Revit and Dynamo and changed paths in the DynamoSettings.xml file manually.
- Reopen Revit and Dynamo and now it just works :slight_smile:
(note you can create a generic xml file with /%username%/)

I have no idea why I can’t use the UI to add the path without Dynamo and Revit crashing. :blush:
After the crash, Dynamo would have the old paths again.
Maybe Dynamo just became overwhelmed #tooManyNodes :stuck_out_tongue:


#5

Editing the XML file manually should not play any role… if it does that, then I think it is a completely other problem.


#6

I worked on two different computers that otherwise crashed loading the packages using the UI. :smile:


#7

This method doesn’t for an update to the nodes inside the packages while the UI is open (you’re not forcing an update of nested nodes). You may have missing or broken nodes this way, but I haven’t been able to reproduce so I cannot say. Best to confirm they’re all 2.x compliant first by checking the format.