Thanks for the direction on the trigger component. Am I correct in understanding that the trigger component is not currently compatible with Add Geometry by Direct Shape?
I’ll send you a download link to my Revit and Rhino file privately.
Hello,
How did it go with the Element binding for the Revit creating nodes Like “Add Beam”, “Add column” “Direct shape” e.t.c?
I see that you have fixed the Revit primitives like “Graphical elements” to remember what elements it created from precious sessions but the “Build” elements still duplicates.
That would be the last fix i need to make this the best tool ever created
I’m still getting duplicate elements. Has this binding issue been resolved? I am using clusters so maybe the issue is that the rhino for revit elements are inside a cluster?
I think I identified the behavoir that is producing the duplicates, its when I open up and edit the cluster. It seems to work as long as I don’t open the cluster, then whatever connection you worked out is broken and I get duplicate elements. Should I log this as a bug? Not sure where to do that.
Let me take a look at this tomorrow. Thanks for the suggestion. When I first create the cluster it does warn me that the link is broken, do i want to delete pinned objects.
Let me take a look at this article and see if it’s a user error, or if there is some unanticipated behavior related to clusters. I will let you know what I find.
I’ve confirmed the behavoir. If I don’t edit and save the cluster then element tracking works. I left it at the default which is update. Once I go into the cluster, and save it then Rhino.Inside will create the duplicate. I tested this with both clusters that are just native to the document and those that are created using the save and reference feature, so its technically a separate file. Both exhibit the same issue. Screen shot of the definition below:
I’ve uploaded a simple version of the script above to demonstrate the issue. The floor plate on the left without the cluster doesn’t create duplicates. Once you create a cluster you get the error message above. It works fine till you go in and then save the cluster. Then you get the duplicate.
I tried locking the solver before editing the cluster, then saving the cluster and unlocking the solver once I’m back outside of the cluster. This does not solve the issue.
Weird. Let me try it again. When I created that separate GH file all I had to do was open the cluster and close it to get duplicates. What version for rhino inside are you using? Maybe I need to update? Not sure how to check my version
It looks like I’m at the latest public release. Should I go with the release candidate or daily builds? I’m assuming you are using one of the latest daily builds and this issue was fixed but is not part of the public release?