We integrated Autodesk Forge in our platform to allow customers to view their models online. However, when customers upload IFC V4 Files (specifically V 4.0), there is an error message shown complaining over a missing model, although the file is valid. Other viewer such as BIM Collab Zoom render the model without problems. Question is (and I was not able to find this answer online) which IFC versions are supported in the Forge ecosystem?
If V4 is not supported, are there any plans in the near future to support it? The documentation at https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/supported-translations/ only generally mentions the IFC support, but no versions.
Related
At https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/supported-translations/ I can check the formats currently supported by Autodesk Forge. Are you working towards enabling expression of the datasets in Geopackage (see https://www.ogc.org/standards/geopackage) and RDF/Turtle (https://www.w3.org/TR/rdf-schema/ and https://www.w3.org/TR/turtle/)?
While there are a few exceptions (like the OBJ or FBX files that are very common for 3D data exchange), Forge is typically used with design formats used in architecture, engineering, construction, manufacturing, or media & entertainment. I don't know if the formats you mention fall into any of these categories, but if they do, I'd be happy to bring them up with the Forge team as a suggestion.
If the Geopackage or RDF files are meant to provide some additional context to other types of designs (like DWG drawings, for example), please note that you can load them yourself, and add their information into the DWG loaded in the viewer using the viewer's JavaScript API.
I'm building a cross platform 3D viewing application in C#/C++ and would like to add support for Autodesk SVF files.
I looked at Autodesk Forge but it has limited support for exporting to open formats such as OBJ, and Autodesk SVF does not appear to be the same format as the similarly named Simple Vector Format (http://www.svf.org/) as was stated here: https://forge.autodesk.com/blog/updated-little-more-detail-behind-autodesk-forge-apis-0
Is there a schema or specification available somewhere that details the structure of Autodesk's SVF format?
The short answer: no there isn't as it's a proprietary format (that has been breached in some country already and legal actions were needed to resolve the issue...)
The long answer and please view this as my personal rambling w/o any real authority or credibility:
I'd recommend to stay tuned to the official Forge website and see if they'd choke up more info on SVF(aka the Streaming Viewing Format) for public knowledge.
Does the Forge design automation AutoCad engine also support commands from the Civil3D and Map3D packages (which are a kind of extension of AutoCad)? Could not find any in the documentation, primarily looking for this because attached Object Data in Map3d does not seem to be extracted to the metadata when converting in the model derivative Api.
We are working on an integration of an external software with Autodesk Forge. Following openBIM, we want to focus on model data in IFC format. Question is (and I was not able to find this answer online) which IFC versions are supported in the Forge ecosystem? Would one have to be careful with using e.g. only IFC 2x3 or is IFC 4 Add4 also supported? The documentation at https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/supported-translations/ only generally mentions the IFC support, but no versions ... which would be a necessary information IMHO, as the format is still in active development.
(Just happened to see this thread)
As I know, there is no IFC 4 Add4, but IFC 4 Add2. See https://technical.buildingsmart.org/standards/ifc/ifc-schema-specifications/
Forge Model Derivative API currently has three IFC conversion methods: legacy, modern, and v3, which are the same as Navisworks IFC readers.
The legacy conversion method is under maintenance mode and doesn't fully support IFC4. So, it won't get updates anymore. For better IFC4 support, please use modern or v3 instead.
The modern conversion method is based on Revit technics. Currently, Revit supports IFC4 and IFC2x3. Its main features of exporting/importing IFC are provided by our open-source project Autodesk/revit-ifc. Model Derivative API uses Revit to export IFC from RVT files so that the supported IFC version will be the same as Autodesk/revit-ifc provided.
The v3 conversion method is based on the modern one but has some improvements (e.g. using file native distance units, not always feet)
Note. IFC4.x is not yet supported. For more details, please check out:
https://blogs.autodesk.com/revit/2022/02/09/now-available-revit-ifc-manual-version-2-0/ (Point Releases (4.x) already in the pipeline, including enhancements and new classes for infrastructure including bridges, railways, roads, ports, and waterways.)
https://technical.buildingsmart.org/standards/ifc/ifc-schema-specifications/ (BuildingSmart withdrew IFC4x1 and IFC4x2, and they are developing IFC4x3)
https://github.com/Autodesk/revit-ifc/releases/tag/IFC_v22.3.0.0 (Added additional generic support for IFC4.x files for 2022.1)
ref: https://forge.autodesk.com/blog/export-ifc-rvt-using-model-derivative-api
Is VRay currently supported or is there any plans to support this render engine in the Forge Viewer?
If not, is there currently any support for any other render engine than the currently supported Scanline render engine?
Thanks a lot.
VRay is supported according to our 3ds Cloud Engineering and they say there's even special, optimized translation workflow (translating the model to the SVF format for rendering by Forge Viewer) for VRay. Otherwise far as I know we don't have any official support for Prism just yet and there's no plan to add that for the near future.