I am experiencing difficulties with an old Dynamo definition I’ve used previously for generating rough massing and street layouts from OSM data. Although the masses appear in Dynamo, they are not transferring into Revit.
Could someone please review the definition and identify any potential errors?
Since I am a new user I cannot upload the definition. I have attached a screenshot. With no luck, I tried changing the categories to Generic Models, so it is not set to Mass.
This Dynamo definition works in Revit 2019, which leads me to wonder if there’s a change in the mass family (rtf) in Revit 2024 that affects its usability with this definition.
I successfully imported the geometries using “ImportInstance.ByGeometries,” but they are non-editable in Revit. Could someone provide insight on this issue?
I found a relevant discussion here: DynamoBIM Forum. So I apologize if this is a duplicate, that user never finalized his response.
First open all preview bubbles going into the node that writes the content to Revit.
Next change the group color of the section with the write out which is failing to something unique, and change the name to ‘doesn’t work’.
Zoom in to the node which fails so you can clearly read the title.
Use the export canvas as image button in the upper right hand corner of your Dynamo instance. This will export an image of the entire graph at the current zoom state.
Common reasons for behavior like this are custom nodes (dyf) which use invalid input names (object classes cannot be names anymore, but could around Dynamo 2.0 which was in use in 2019), and an incomparable ItonPython2 engine (meaning the engine for Dynamo 3.0 instead of one for 2.0).
What version of IronPython2 did you install?
If you double click the node which writes out the families do you get a warning?
Which version of that package? This can be found in your Package Manager of your Dynamo preferences.
The node is telling you the issue - you have duplicate node names. Try swapping out Number To String with a code block of “”+numbers. Or add a random value to all numbers - Math.RandomList can help there.
I believe it’s working now! I had to halt the operation initially due to an error on my part, but it seems to be functioning as it did previously. I will provide a full update once the operation is complete.
Now if you really want to simplify thing, change it to ”building “ + (1..List.Count(solidsList)); and you can get rid of the List.Combine and ListCycle and the proceeding code block.
Might not work back in 2019, but you shouldn’t be using anything older than 2022 at this point.
