WISH: Native IFC export --> boost in user base


Writing this just after a meeting about this BIM infrastractural project.

In this world of infrastractural projects we are slowly moving towards BIM. Current state is that many disciplines just use autocad lt for documentation. Even with full autocad it is not possible to model lines (as cables) or boxes (as technological units) and attach attributes to them (key/value/unit).

If Rhino 8 included native ifc export with all key/value/units included as non-graphical info to the element i am sure there would be a surge of new users.

Another thing probably neccessary for ifc is to include units (third column) in key/values.

There is nothing easier than model boxes and lines in Rhino and add keys/values → problem is with easy export to ifc for coordination. 3dms are not accepted as common format in case of CDEs (trimble connect …)

1 Like

+1 also with adding IFC tags. For now, it`s needed to buy a whole VisualARQ plugin only for that single feature. Amazing VisualARQ is of course worth their price but I also think that the single IFC export (to Revit and Navisworks) feature should be bundled in a basic Rhino version without any additional plugins.

1 Like

i dont know what you mean by ifc tags but i think basic rhino user keys/values should be seamlessly transferred to ifc when exported. with plugins like visualarq those are separate tags (easy to use grasshopper to mirror keys/values to visualarq tags, but still some work).

1 Like

Hi -
I added this thread to feature request RH-52747.

1 Like

thanks. i think it should go from wish to “strategic” because now its the time when BIM is on the table and users are looking for actual tools to model and attach other information which is not possible in autocad.