Recently I had a look at RhinoInside (it’s been a while) and I was trying to figure out the best way to export/transfer geometry from Revit to Rhino (using GH of course).
As such, I’ve been wondering if there is a concensus as to what a correct or best way to do this is?
Specifically I was trying to figure out a way export a somewhat complex model (visible geometry in viewport) , in one go, from Revit over to Rhino while retaining category as layers…
But ended up completely throttling the computer.
As to why im not sharing an image of the spaghetti;
I’m not at the office and the conundrum is still itching my brain.
A complex Revit model will be need to be taken in smaller bites. If the goal is to have it all in Rhino, using worksessions for the various disciplines might be prudent. The mechanical files can get rather large, as can structural or others depending on the size and detail of the project. I would also consider baking bounding boxes for elements where you don’t need the detail (structural?)
this is more or less the script template that I use to export geometry from Revit to Rhino automatically and classify it in layers/categories. From here I have done multiple variations depending on the needs of the designer.
This script is also considering the hidden elements to avoid exporting them. But I am sure that there are other ways of doing it.
When it comes to the size limit I have seen several cases. First it depends on the computer (I mainly use a laptop and I can see that there is a huge difference when I use a desktop, as it is faster and I can work with heavier files). If the Revit file is around 500 Mb and it has links (like any regular file), I would recommend you to export the main file and the links separately as @Japhy said). However, if the file is smaller (around 100 - 200 Mb) you can actually try to import everything in one go, but use a desktop .
That script worked really well Fernando!
I must have messed up mine somewhere along the spaghetti…
I’ll play around to try out some tweaks and variations on it next week i think
.
