This is somewhat of a broad question, hoping to get advice. I want to know the best way to transfer geometry from Revit to Rhino. The process I currently have is as follows:
Would the best strategy be that I would have to query each category/type individually (for examaple it seems that curtain walls have a specific way to be translated into a graphical element), or is there a more efficent way to obtain as much geometry as possible with a simpler approach?
For this process I am actually purely focusing on Revit to Rhino, and my primary issue is that when using the script (shown in previous post), some elements are not getting pulled through.
What I suspect is that I would need to query each element type individually, but that would be quite long and convoluted, so I’m wondering if there’s a better approach.
Yes, revit families can be a bit complicated to get down to the geometry. So if you want to send us the objects that are failing we can look. Curtain walls have an especially complicated implimentation
I believe the easiest way would be to follow the below… just setup a view in your project that will contain only the geometry you want to send and then use the below components and bake, this will get all elements including CW geometry in view and will also be able to get them organized in layers etc
@Muhammad_Saqlain_Awa that’s a great spot, I removed the limit, but I am still having an issue with the result bake (see video below, the same result occurs using the same script I created originally)
@M.Tarabishy that approach in principle works but it ignores many building elements as you can see from this example (using the template file attached above)
What’s currently working is if I Query each individual category, but that is quite convoluted, so I am wondering if there’s a cleaner and a more direct approach.
Hi again, so I checked the sample file as you mentioned and I see what you mean now… so as you mentioned in pricipal the workflow should work but it seems that while baking once one element fails the baking process stops.
So, through testing i figured some elements that don’t bake and cause baking to stop removed them from the list and now I am getting a bigger amount of baked elements as you can see.
So maybe @Japhy@kike can have a look at the bake option through graphical ele component?
Hope this helps a bit in figuring the issue with baking.
Aside from that, @diana.ofcg if you don’t care about the layers/colors you can use ‘element geometry’ after the ‘query graphical elements’, this will get you all the geometry and then you can bake that resulting in all valid geometry.
Thanks a lot for the troubleshoot @M.Tarabishy. I’ll give the example you gave a go for now. I am noticing though from your example it’s not baking walls, roofs, generic model families, groups? I wonder if there’s a way to trouble shoot why that is and how to fix any potential issues.
If you notice in my example I have a reverse on the list, if it is reversed it will start with the elements shown in the image, before reversing you might get the topo and initial set of elemnts from your first trial.
What I did is i sorted text to group similar elements together and then baked… selected the baked objects in the rhino view and check how many elements where selected, then graphical elements list at that index. That’s how I figured which elements were not baking (so when i selected any idividual element from the storefront wall/glazing etc these don’t bake any geometry).
As to why the walls for example are not baking although if you select just the wall in revit with a graphical element and bake it, the geometry will be baked just fine. Is (my guess) that the bake option when supplied with a list of elements would go baking the geometry one by one and once it finds an elements that fails to bake it would stop the whole process instead of skipping to try the next (just my assumption though).
I see. Baking this way seems to retrieve the most geometry but will not associate with layers/colours. Is it possible to make Element Geometry bake with the original Element Parameters?
If you bake each element to its category as layer along with its ElementID you can re-reference and drill into the particular Parameters you need for each Category, Element or Type.
That certainly could work. I am wondering though if it’s possible to retain the block definitions just like what you would get when baking the Graphical Element. It seems once the Graphical Elements get converted to Element Geometry it removes any associated block definitions.
There seems to be a limit set somewhere which is preventing all the elements to be baked as you can see from this example, it could also be that something is causing the bake to stop as @M.Tarabishy previously suggested. What would be ideal is to have the option to bake invalid objects, or simply skip bad objects whilst it continues to bake, additionally to give a report on what hasn’t been baked so the user can easily point that out. This may be asking for too much
Hi Japhy, just to add is that the ‘query graphical element’, does indeed actually query element dependents, although as Diana mentioned above right clicking and baking from the ‘graphical element’ component does stop at some element and doesn’t continue.
So it seems that this approach would be the quickest if baking process is some how resolved.
