Rhino and BIM

I really like VA and use some of it’s features daily (levels, sections, section hatches, plan/section views, ifc im/export, parametric objects, also grasshopper-powered, etc ).
But yes, it’s not perfect, and there’s a lot to be desired. For now, I use it for the design phase, not executional planning. My hope is that VA3 will be the big step forward to make it a convincing drafting and BIM solution as well.
Just some examples:
You cannot rotate space labels, which is a dealbreaker in all projects not aligned to exactly project north (which are practically all).
Creating schedules/lists (the purpose of BIM) is still too… awkward. Features are there, but this could be simpler.
(Both examples will be improved in VA3 as Asuni tells us.

My conclusion up until now: it’s quite useful, but if you try to use VA for more than it is capable of, you will be disappointed. It’s not a Revit replacement - yet.
That said, I truly hope it will become one, and better sooner than later. The way Autodesk is milking their customers is… unsavory.

Something else: most manufacturers in the building industry offer 3d versions of their products, for BIM planning (windows, doors, facades, furniture, electrical, lighting, plumbing, …). Of course there are commercial interests behind this, but still it can be helpful.

Although some objects are available as 3dm, the big players usually offer Revit, ArchiCAD and DWG. Some example:

VisualArq is still flying (far) under the radar here, so we need a proper way to import such data. This would be another loose end to tie if VA wants to become a serious player in the BIM game (for good or bad…)

3 Likes