Best practice when importing geometry from Revit to Rhino with Rhino.Inside.Revit

Hello experts,

I’ve recently started using Grasshopper/Ladybug/Honeybee to simulate daylight as an Architect.
I’ve found the “” definition, which works like a charm to bring in my Revit geometry and bake it in Rhino so I can continue workflow in Rhino/Grasshopper.

However, I have recently experienced issues with the geometry being too complex and causing my Rhino and Grasshopper to become unreasonably slow. The simulations would time out and not return any results.

Upon inspection on the baked model I found that the Rhino.Inside.Revit definition had baked the grouts of each window. I suspected that was the culprit so I manually modelled all the windows in Rhino and that did resolve the issue. Needless to say, that is a very time-consuming task.

What are your experiences? Is there a better practice for importing Revit geometry to Rhino?

I have attached the Grasshopper definition I use to simulate, but basically it defines the geometry in Grasshopper by using Pipeline with a layer filter.

GH (541.4 KB)

I have read about Pollination, but I’m not sure I do enough daylight simulations to warrant the $200/month.

I hope one of you experts can point me in the right direction.