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 …
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?
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
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.
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
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?
place instance.dyn (6.9 KB)
Here you are.
Please let me know if how it works. Many thanks to you
Your file works fine. Im unsure why you are having problems when closing & reopening the file between runs.
Maybe explain the exact process you are using or post a screen recording showing what you are doing?
You could try running the definition on a fresh Revit file and see if you get the same results.
Could you give me your email? I will send you a short video that show how I do. The dynamo forum do not allow to upload video file here.
I dont know why it is doing that on your machine. I do exactly as you are doing and it just places a new tree each time i close and reopen Dynamo. Works fine for me :s
Unless its an error with your install of Dynamo? Maybe try uninstalling and reinstalling Dynamo (most stable version) and see if that fixes it.
Not really sure what else there would be to check
It’s a popular request to have a ‘bake’ button or node in Dynamo. One current workaround besides reopening your DYN is to use it via Dyno (which seems to re-initiate Dynamo every time your DYN is invoked).
yes, it is so strange. I should reinstall Dynamo and see how it works again.
I think Dynamo should have an additional function that allows users to select start-over or to continue program.
Is your Revit file on Revit Server? We had this same issue and I tested everything including shutting down the computer and restarting after a weekend and it still removed the previous dynamo scripted work. What I found was I needed to wipe out the model history by detaching and replacing the model on Revit Server.
It still removes the previously-created objects. I do NOT use Revit Server, my revit file is simply a single file for only one user. So weird! my dynamo program is almost done and only getting stuck here, I am quite disappointed.
I also have been seeing this behavior. Similar behavior seems to happen when copying and pasting components, (that have been used to in a previous run). In my case, it is specifically, with the FamilyInstance.ByPoint component. The only way around is to restart dynamo, as previously suggested. Is this a known behavior or is there an alternative?
Have you tried this?