
Displaced elements API – exploded views.Command API – launch macro, add-in and built-in.Schedule API – formatting, read-write data items.Project browser API – commands, macros, selected elements.Copy and paste API – within or between documents, incl.The shortest useful summary of the main new API features that I have been able to achieve is this: The complete flat ported source code, Visual Studio solution and add-in manifest for the Revit 2014 OBJ exporter. Probably some face normals are also wrong, or, equivalently, the polygon loop vertex ordering is inverted. Maybe the MTL file is not being properly processed. Here is a sample visualisation in Octane of a Revit 2014 model exported to OBJ:Īs you can see, the texture mapping is rather strange. Running the OBJ exporter on the RAC basic sample model generated these Some of that complexity could be removed by rewriting this using the Revit 2014 custom exporter API.Ībove all, the graphical properties could easily be better supported. The current implementation thus still traverses all the Revit model elements one by one, retrieves their solids, exports the graphics face by face, and determines some, but not all, graphical attributes as described last year: To fix the processor architecture mismatch warning MSB3270. Would like to try that as a visualisation tool instead.Īpparently, the only way to export a Revit model to Octane is via the OBJ file format.Īnswer: In order to provide something immediately, I simply flat ported the Revit 2013 OBJ exporter to Revit 2014. However, a request already came in for a Revit 2014 version: It would be nice to rewrite my OBJ exporter for Revit 2013 using the new Revit 2014 custom exporter framework. I also add some more background to the list of newįinally, to wrap up, we'll look at a surprisingly unbalanced distribution of Revit API

OBJ exporter for Revit 2014, so I discuss that below. Revit 2013 OBJ exporter to make use of it, a request came in for a version of the Funnily enough, after dealing with the new Revit 2014
