It seems that some Revit elements cannot be baked in Rhino8, and I hope it is possible to do the same in Rhino8, as it worked fine in Rhino7.
I’m using v1.22.
A little dirty elements tend to be unbakeable.
When there is an element that cannot be baked, subsequent elements in the list are not baked either. It is possible that the process stops there.
Please check the attached sample for reference.
thanks,
directshape_import.gh (8.4 KB)
Breb_import.gh (12.7 KB)
Maybe these can help u get these objects into Revit, as a family
The suggestion you gave is one way to pass Rhino objects to Revit, but what I want to do is to Bake the Revit elements to Rhino.
I asked this question because what I was able to do in Rhino 7 is not possible in Rhino 8.
Sorry if my words are not clear enough.
thanks,
Try connecting the elements with the ElementGeometry node and then baking, maybe it will help. I can only bake some objects using this.
Hi Hiroaki,
Can you post a small file with the geometry that is not working for you? Thaks
Sorry for the late reply.
I understand that it is possible to Bake via ElementGeometry.
The question is about Bake of Revit Element without ElementGeometry (not converted to Brep).
Hi Japhy,
Can’t you check with the Revit file already attached?
I am attaching in this reply a file with objects with Revit Element baked through ElementGeometry, but there is not much of an issue there.
I think the issue is when you Bake Revit Elements into Rhino without going through ElementGeometry.
sampleRH8.3dm (200.7 KB)
I have made a video of the behavior of the issue for reference.
The element with “id 279346” seems to be doing something bad.
The elements after that list are not baked. I understand that the creation procedure is messy and the elements are close to invalid elements, but I was still able to bake them in Rhino7 with no problem.
This issue occurs in Rhino8.
Sorry for the confusing English.
Thanks,
Thanks for the video, that is very helpful in showing the issue you are experiencing. It’s typically the other direction where we see issues… Rhino to Revit
Our company has found it very useful to have a two-way data exchange between Rhino and Revit users using Rhino.Inside.Revit.
For example, a Revit user may create a building outline and import it into Rhino, and another Grasshopper specialist may model the exterior.
Other times, we draw a wall core in Rhino, use it to create walls and rooms in Revit, and then feed the room elements back to the Rhino side as hatches.
Part of the reason these are needed is that not everyone is a Revit specialist, and for those who lack Revit skills, we occasionally come up with workflows that reference Revit elements into Rhino.
So we believe that Revit to Rhino is a very important flow.
