I was hoping I am missing out on something very obvious here. When creating geometry in Revit using any of the (light) blue components, Rhino.Inside will retain connecting to the resulting geometry in Revit. So, upon input change, the geometry will ‘update’ on the Revit side. That’s by design and I get it.
However, more often than not I want to be able to reuse the graph change the inputs as I go, and create many different geometries ‘reusing’ the graph sort to speak. At the moment I am forced to disable>copy>delete the creation component before changing the input value so I don’t lose the previous geometry. I apologize for the long-winded explanation.
Any ideas of how that can be achieved in a more-elegant fashion? Thank you in advance.
is there any update about the “element binding” feature? I have read in previous posts that unpinning the element could solve this issue, but it does not work anymore.
In any case, other suggestions to solve it would be more than welcome.
This is definition that creates then edit and finally release a type.
As long as you don’t press the Release My Type Grasshopper will update it.
Once you press it Grasshopper will forget it has created this type and will try to create a new one.
thank you very much for your answer. I have been checking your solutions and they definitely work for elements like simple walls from curves. However, I am trying to use this for DirectShapes and in those cases it that does not work with none of the two methods (the release element component or modifying the tracking mode in the DirectShape component). Is it something that I am missing? Which solution could I use for these cases?
I am using DirectShapes because the kind of geometry that I am trying to export to Revit is too complex to be created with Revit, but in my tests I am using more simple geometries like boxes and it is not “baking” the different alternatives.
It’s a little different in this case because you are creating a Element Tracked Direct Shape Type, then placing a instance of the type which is then released. The initial Type is not ‘released’
So with Element Tracking set to Update on both, this would need to happen.
