![]() Is that a correct understanding? It's fine if so. The developers now need to understand the specs of the file type to export to. In short, the Revit API moved away from filetype-specific exporters. Löbel's export approach is much more code than using filetype-specific exporters. The flip side is that this class doesn't understand the output specifics of particular file types, so the developer has to handle that themselves. ![]() That used to be the case in the Revit API:īut FBXExportOptions is obsolete, so people now use CustomExporter. ![]() Just so I understand the current API a bit better, is this statement true? In Unity and several other apps, you can export a scene/view/etc to an FBX in a couple lines: I'm pretty new to the Revit API, but not to related tools, so thanks for the insight. It's more work than I thought it would be, especially after seeing the FBXExportOptions class. It's now on the developer to handle writing the output file with assistance from the helper methods.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |