Beams export problem

Replies to This Discussion

Permalink Reply by Jon Mirtschin on July 1, 2013 at 5:28am

I see you posted an image and IFC2x3 file, but if you're dealing with nurbs (and my revit importer) IFC4 will work more accurately and efficiently.  IFC2x3 doesn't have nurbs, so the plugin converts the path curve into a polycurve (arc and line segments).  In this member it seems the orientation vector is near parallel to the end segment, so a default orientation is assumed.

Your gh definition was saved in a state to generate IFC4 (right click on bake component).  But your path curves aren't "planar".  I've attached a definition that projects interpolated points onto a planed fit to 3 points.  Then I get a lot more members created in Revit (I've not seen you can create a non-planar path curve in Revit).  Revit does have nurbs capability, but not as functional as Rhino and you'll see few members out of position.  You could try building the curves with fewer points, but if you accept a generic model beam (difficult to edit but should represent ok in revit) then I've been working on a new workflow to generate non-planar or arbitrary elements in Revit by exporting the geometry to a .dwg or .sat (2014) file and then importing into a generic model family.  It's much slower but can achieve nurbs geometry transfer.  I'll demonstrate this soon (I need to check on the sweep I'm getting).

Note Revit 2014 seems to have gone backwards from Revit 2013 in depicting beams with nurbs profiles, so anyone creating similar should stick to 2013 until a patch (or 2015) comes out.  I'll monitor this.

Hope it helps, will post the alternate method ASAP.

Attachments:

• stadium_beams forced planar.gh, 31 KB
• stadium_beams gg planar.ifc, 104 KB