Submitted Revit 2022 model to Forge. It accepted SVF format but returned PDF's - autodesk-forge

Submitted Revit 2022 model to Forge. Accepted SVF format but returned PDF's
acceptedJobs":{"output":{"formats":{"0":{"type":"svf","views":{"0":"2d","1":"3d"}}}}}}
snippet from manifest:
{"urn":"urn:adsk.viewing:fs.file:dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6aW5lcnRpYXNhbmRib3hfdGVzdC9pbmVydGlhc2FuZGJveDByMjIuemlw/output/Resource/Sheet/A101 - LEVEL 1 FLOOR PLAN 1420741/pdf/A101 - LEVEL 1 FLOOR PLAN.pdf"
Model works as expected in 2021 format, I used the same model upgraded from 2021 to 2022 and it changes from producing the expected svf to pdf.

UPDATE Feb 2023
Now we have an advanced option to control if the resulting 2D views will be converted as PDFs.
Please, refer to https://aps.autodesk.com/blog/advanced-option-rvtdwg-2d-views-svf2-post-job
...
When you trigger the conversion, 2D sheets for Revit file with 2022 and higher versions are exported as PDF.
2D properties are supported by GET properties.

Related

Revit model extraction fails to produce .json and .pf files

We have been using the Forge API for several years to extract model data from our Revit models. The change on November 7th 2022 has altered our data extraction results.
It appears that the extraction process no longer produces .json and .pf files.
extraction 1
extraction 2
We ran models that were successful in the past and now they fail extraction
We tailed logs to check progress and were unable.

Missing Autodesk.AEC.ModelData in model forge viewer

I am trying to access Autodesk.AEC.ModelData data in forge viewer.
I have two revit models.
so while consuming it inside the viewer for the first model have the Autodesk.AEC.ModelData but when I am trying to access Autodesk.AEC.ModelData in 2nd model it returns me empty.
After verifying in postman by calling api I found in the second model
there is no role with the name Autodesk.AEC.ModelData and I could not find any url with AECModelData.json
so I would like to understand where is it going wrong is it problem at translation level or is has to do it with revit software. do we manually need to add AEC data before exporting file to rvt or nwd ?
please let me know any other solution to access this data or the area where I can take a look
Only RVT saved with Revit 2018 and later will generate AecModelData. If you still cannot see it on files of Revit 2018 and later, you can try to translate it again with the x-ads-force: true request header.

Extract and download model to local machine in OTG format

According to https://github.com/wallabyway/OTG-client-sample, a new OTG format for the forge viewer has been released and it looks like it has siginificant improvement in performance as opposed to the traditional SVF format.
Currently,we are using model derivative API to translate RVT/NWD files to SVF and download it to our local machine using the extractor from the following link:
https://github.com/cyrillef/extract.autodesk.io
The question is that how do I to translate the model into OTG format and load it locally?
Thanks in advance!
As of now (end of August 2019), the OTG file format can only be obtained via a manual post-processing step through a series of unofficial API calls. However, we're planning on including the OTG output as part of the standard Model Derivative translation. Stay tuned to the blog and #AutodeskForge for updates!

3D Geometry missing in Revit File after model derivative SVF translation

I'm trying to translate Revit file that contains both 3D and 2D geometries. I've verified that the file contains proper 3D geometry, by opening it in revit 2019 and visualizing it through 3D viewing mode.
However, when I pass this file into model derivative process, it only creates 2D derivative.
Before translation process, I've tried to set default view of the revit file as '3D' instead of 2D drawing file, which didn't work.
I've also tried making a translation POST request with formats as 'svf', and views as both ('3D', '2D'), and ('3D' only), which both failed.
However, all these attempts didn't work, and when I inspected the manifest from the file translation, it seems like that 3D geometry is completely missing. I think that there is a unhandled exception in Model Derivative process that fails to extract 3D geometry in our particular forge model file.
If you need URN of the file / actual file, please let me know.
Thanks in advance.
- EDIT
UPDATE:
I've confirmed that the default 3D view is named as {3D}, default name set by Revit.
What is the name of your default 3D view?
The default name is "{3D}", I believe.
Maybe the translation process does not pick it up if it is named differently.
Afaik, the one and only way to specify the views for the translator to process is by using the Collaboration for Revit or C4R BIM 360 Team tool to select the views to publish to the cloud.

CNC Manufacturability Analysis Autodesk Forge

I would like to build a CNC manufacturability analysis app using Autodesk Forge.
Setting the computational geometry algorithms aside, what kind of geometrical data can I extract from CAD files using this platform? also, is there an existing app I am unaware of?
Thanks
Depending on the input file format you can convert to different other formats:
Supported Translations
Though it's not obvious from the above list, all input formats support conversion to OBJ format, which can also be done at subcomponent level - so you don't have to export the whole model to OBJ.
Here is a sample that lets you access your files from A360 and convert them into whatever format is currently supported for them:
Model Derivative API sample
Source code: https://github.com/Autodesk-Forge/model.derivative-nodejs-sample