On the other hand, if you want to export as IFC, you don’t need to use Rhino.inside.Revit for that. You can just tag the Rhino Geometry with the corresponding Ifc type (VisualARQ objects have the Ifc type defined by default), bake it and export it to Ifc.
Here you have an example of how to tag Rhino geometry with an Ifc type using the VisualARQ Grasshopper components:
If you use the VisualARQ.inside.Revit Grasshopper definition I told you about in my last post, Rhino geometry tagged with an Ifc type in Rhino will be automatically transferred to Revit, so you will not need to export to the Ifc format and then import it into Revit.
Thats all great, my only issue is that in the script I gave you ideally I want to be able to automate my bake using a bake from the Human plug ins- I understood this one should work but I get the error in image attached? its the same as in the script I gave you before.
Cheers for all the help, I think the tool is very powerful for our office moving forward.
Sorry, I forgot to speak about this in my first post. This Human component doesn’t accept VisualARQ objects in the “geometry” input, but you can use the “Bake Objects” component in the “EleFront” plug-in instead.
We have run into an issue, we have found that when we create slabs in grasshopper and add styles we can now bake those out with elefront.
Out issue is now we can not set or create parameters to one of these slabs without baking them out first, then importing the slab back into grasshopper and then assigning a property and rebaking the slab element bake out.
Are we missing something? because ideally we don’t want to have to bake multiple times, we would rather have the slab, add the parameter value and then bake out all in one hit.
The EleFront component cannot bake just the style, it needs to bake the slab object and, at the same time, it will bake the style. As for parameters, you don’t need to bake the slabs first; I have made an example to show you how you can create a slab with parameters and bake it all in one hit:
Yes, it looks like there is a problem with that since we found two issues related with it. I don’t know if they are related it yet, but they probably are. Please, if you find any other problems, let us know. I’ll keep you updated about this.