Is there any documentation for converting a JPEG file via Model Derivative API and viewing it as an underlay of another 2D PDF drawing, in Forge 2D Viewer?
JPEG files aren't supported accordingly to this page. PDF is supported and translating a PDF is not different from other file types. Here is a step by step documentation to do it.
Now back on JPEG, the Model Derivative API will not handle JPEG format, but you can still display JPEG in the Autodesk Forge Viewer using native THREE.JS API. All you need to do is to assign the JPEG to a THREE.JS mesh and add the mesh to the THREE.JS scene in the Viewer.
Related
translate fbx file, but viewer don't have any texture.
my fbx file(17MB) madeby contextcapture. ( LiDAR )
fbx file's texture is fine. i checked by windows viewer and navisworks.
Unfortunately, I believe Autodesk Forge Model Derivative API still does not extract material, nor textures for FBX files today (as the time of this post).
Please also refer the answer to this post at Texture of 3D model in FBX extension in Autodesk forge not visible
I want to import PDF file in Model derivative API and work with different layers. But it is not detecting layers in PDF models as it does in DWG files. Layer manager option is not visible. What to do?
In cases where the Model Derivative service isn't extracting enough information from your input files, you have a couple of options:
if your input file is a AutoCAD, Revit, Inventor, or 3ds Max file, consider extracting the additional information using the Design Automation service
if your input file is a PDF, consider:
viewing the PDF directly in the viewer (see this blog post for more details)
using a 3rd party library (e.g., pdf.js) to extract the additional info yourself
We need to create rvt file using mesh data, triangles (indices, vertices, normals, texture uv). So does revit design automation apis supports create mesh with texture and texture uvs? Any examples would be great help.
Thanks.
I would suggest you research the DirectShape functionality of the Revit API: DirectShape. It includes some ability to apply a Revit material (which is a color and/or texture) to the shapes you create. I don't know if texture UV can be specified for DirectShape faces.
If you have your own textures to create in Revit, then you'll want to read about Revit materials and Google how to create them.
Best,
Michael
Design Automation API for Revit (DA4R) could be considered as a Revit runs on the cloud, you can upload your own app bundle that contains your Revit exporter IEXternalDBAppplication Addin to help you export mesh data from the Revit models. Here is an example demonstrating how to export Revit elements into three.js meshes and scene:
https://github.com/va3c/RvtVa3c
But it came with UI, you have to convert it to pure IEXternalDBAppplication (remove UI codes) before uploading to Forge server as DA4R activity.
Hope it helps!
Cheers,
I've imported a DWG file into the 3D view of a RVT model, and am trying to convert and view it in the Forge Viewer. When I view that 3D view in the Forge Viewer the drawing does not display correctly. See links to screenshots below.
I've looked through the response JSON from Model Derivative and do not see any errors.
The RVT project file and the DWG I am trying to embed are also linked below. I am using the rac_basic_sample_project file, where I exported the site plan view to a DWG, and tried to embed that into the default {3D} view.
3D View in Revit
3D View in Forge
RVT File
DWG File
I have uploaded a model with texture in a folder on A360 in FBX extension. At the time of checking view of model in this link "https://dm.autodesk.io" the texture of model not showing only default materials color are available there.
Please suggest how can i upload FBX with texture ?
Unfortunately, Autodesk Forge Model Derivative API does not extract material, nor textures for FBX files today (as the time of this post). It might in future, but have no ETA on this. This has been a long time request since Forge came out. If the goal is to show textures in the viewer, you can take a look to this post for a workaround.