Dear Everyone, Is it possible to prevent dynamo from starting over? For example: if I use node “FamilyInstance.ByPoint” to firstly place an element at location A, then I additionally place an element at location B in the second run. The model now should have 2 elements at location A and B. But the final result shows that only location B-element exists and location A-element is removed. [image] [image] [image]

Dear Einar_Raknes I do as your recommendation but the previously-placed items are still removed. Do you have other solutions? Thank you very much

Not sure as to what exactly you’re trying to do. But assuming you want to create a second element whose location is determined relative to the location of the first element, you could try something like this … [image]

Dear Vikram_Subbaiah Maybe you misunderstand what I mean. You can be back to my question at very beginning. Firstly, I place an instance (called: instance 1) at location A (first run of Dynamo). Then, at the second run, I like to place another instance (called: instance 2) at position B with assumption of not knowing the instance 1 at location A. after the second run, the instance 1 is removed and remains the instance 2. My question: are there any way to remain the instance 1 after the second run of dynamo?

Hi Hoc, Are you looking for something like this: [image]

Hi Kulkul, I misunderstand what I mean. could you please give me your email, so that I can send you document to better express what I want to do. Thank you very much

Hoc As @Einar_Raknes mentioned. Running the definition once to place the object at Location A, closing Dynamo and re opening it and then running the definition again should place the second object without removing the first. I have a few definitions that i use to place objects and this is what i do when i want to add more objects without deleting the originals. Im sure i saw @Zach_Kron post something about this a while ago, think it is an intentional feature. Not sure of another way to get around it.

Dear Alisder_Brown, I did as @Einar_Raknes 's suggestion. But the first object was still removed. I am using Revit 2015 and Dynamo 1.0.0. I will be grateful if you can me some videos to show how it works. Thank you very much for your help.

This may be related to a problem I’ve discovered with Adaptive Components output by Custom Nodes (or any Family instance for that matter) - if you place multiple instances of the CN on the graph, only 1 object ID for the Adaptive Components is ever generated, resulting in a ‘last node wins’ scenario as Revit removes the previous output ACs from the first node and replaces them with the new! The behaviour described above seems to display this problem. EDIT: Not sure if this is useful/relevant, but click here for a link to the aforementioned problem on the Dynamo github

Hoc That is strange. I just tested it again and it is working as i explained. Could you post your Dynamo file you are using to test it out please? Just need the Dynamo file, not the Revit file. Just to clarify, this is exactly what i am doing: Set the points in Dynamo and Run the definition Close the Dynamo definition (so it takes you back to the home screen) Or close down Dynamo completely) Re open the definition, set the new points and hit run When i do the above, the original object is not affected as it is not part of the new definition. Unless you have something in your definition that deletes family’s?

Prevent re-running in dynamo

Uncategorized

Tomasz_Puchala September 5, 2016, 7:45am 24

Have you tried this?

Topic		Replies	Views
Place new family instance each run Revit	25	12303	December 9, 2016
Running Dynamo and keeping objects created FAQ	23	11391	November 29, 2021
How do I make dynamo "forget" what it did in a previous section? Revit	8	7758	December 11, 2020
Previously placed elements get overwritten when I try to place new elements FAQ	2	878	September 27, 2016
How can I prevent Dynamo from placing new families at each run? Revit	13	2853	February 7, 2018

Prevent re-running in dynamo

Related topics