Detail in forge viewer vs A360 - autodesk-forge

I made a query about this previously but with further investigation I still have a problem. The two screenshots show the same component in A360 and in our Forge viewer. The behaviour in A360 is what we want with only the external geometry of the component visible. This used to be the case in our webapp but a change made to the Forge viewer at some point means all the detail in the component is now visible, including internal details. How can we replicate the behaviour we see in A360 in our forge viewer?A360

What you need to do is to force The viewer at startup using
options.isAEC = false
This will make the Viewer go back to the Highlight view that A360 is using at the moment.

Related

Bring REVIT Areas to FORGE VIEWER

I wanted to know if there is some quick way to have the 'Revit Area items' available at the Viewer, via the self Viewer API or Model Derivatives preferably, or any solution that you have in mind of course will be aprettiated too. Thanks in advance.
To see the Revit area in Forge Viewer, you will need to include the area plan view in either the active view set of the Publish Settings.
Here are snapshots of my research.

How to use the BIM 360 Web Viewer (Autodesk Forge)

How to use the BIM 360 Viewer mentioned on this article (https://forge.autodesk.com/blog/bim-360-viewer-vs-forge-viewer)?
I tried to find on the autodesk forge documentation, but didn't get anything.
I'm already use the "normal" viewer on my application.
The BIM 360 Viewer is not for 3rd parties and is only used inside BIM 360, but it's built on the public Forge Viewer and apart from a couple of BIM 360 specific functionality the difference in behaviour would come from the profile settings used and the extensions loaded - as also mentioned in the article you pointed out.
You said that the issue seems to be with positioning/orienting when loading multiple models. By default, the Viewer automatically sets placementTransform and globalOffset to bring the models to the center, but you can override that when loading a model, see
https://forge.autodesk.com/blog/loading-multiple-models-forge-viewer-v7
Hopefully, using that should help solve the problem.

How to Export Multiple 3D Views

My Revit project contains multiple 3D views.
By default only the {3D} View will be translated. I would like to know how to choose which 3d view to upload.
I found this post where a solution to the problem is described. Export Multiple 3D Views
The plugin is no longer available, but this function will surely still exist.
When I upload the Revit project to BIM 360, I only get a small part of the created 3D views displayed.
I only want to visualize a small part of the project in AR.
My current solution is to display the part in the {3D} view via section box, save the project, upload it and then prepare it for Unity with the AR/VR toolkit.
Started Revit 2017, it got renamed as Publish Settings, please check this page: https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/CloudHelp/cloudhelp/2017/ENU/Revit-CAR/files/GUID-09FBF9E2-6ECF-447D-8FA8-12AB16495BC3-htm.html
Please select views you want to see in Forge Viewer in view sets of the Publish Settings before uploading to Forge for translation. Afterward, save the modified RVT to your hard disk, then upload it to Forge OSS.

Mass models from FormIt do not render in Autodesk Viewer

Autodesk Viewer doesn't seem to render Mass models that were created in FormIt and converted to RVT. I can only see the level delimiters.
I've tried both https://viewer.autodesk.com/ as well as a basic viewer app I built using the Forge tutorials. This is an important part of a system that I'm trying to put together using a few of the Forge APIs.
If Mass type elements cannot be seen in the Viewer, is there a modification I could do using Design Automation v3 that would make the models visible?
Per Eason's advice I added the 3D view to the view set and that enabled the model to fully render in the Autodesk Viewer. This config option can be found under Collaborate->Publish Settings. All models that I imported from FormIt started off with all their views deselected in the view set.

Position/orientation of model in Forge Viewer

I have set a specific orientation for my model in Revit, but as it gets loaded in the Forge Viewer is appears that the viewer overrides the coordinates of what I've set in Revit.
Where/how can I edit the "home-screen" for my model in the viewer?
There are two ways to do this in my experience, one is using Set current view as Home in the Revit ViewCube, another is using Viewer3D state API in the Forge Viewer.
In the Revit part, you can do this in this ways:
Open a 3D view, then duplicate it with an new name. Don't use the default name {3D}.
Set a specific camera orientation in this 3D view, then click the Set current view as Home in the Revit ViewCube to save current view as the default view.
Pick this 3D view in the Publish Settings to tell the Forge Model Derivative service to translate this for viewing in the Forge Viewer, then click save button to assign this 3D view as the Web view for the Forge.
Save this Revit project and upload it to the Forge for model translation. Forge Model Derivative service will use the camera position in the Home view you set in the above steps as the default camera position of the Forge Viewer.
In Forge Viewer side, you can do this:
Set a specific camera orientation in your viewer app, then call viewer.getStatus( { viewport: true } ) to get current camera state (One time only).
Remember this camera state somewhere.
Restore this camera state after all geometry is loaded via the viewer.restoreState( thisCameraState ) every time.
If you want to override the default Home view of the Forge Viewer, you can simply call viewer.utilities.autocam.setCurrentViewAsHome() after the step 3.
==== Update ====
If you still have some problem related to this issue, you can consider providing a reproducible case demonstrating that, I will gladly analysis for you. Those following items should be in the reproducible case:
A short exact description of what you are trying to achieve. The behavior you observe versus what you expect, and why this is a problem.
A complete yet minimal sample source model to run a test in.
A complete yet minimal Forge app that can be run and debugged with a simple procedure to analyze its behavior lives in the sample model.
Detailed step-by-step instructions for reproducing the issue, e.g. which element to pick, what command to launch etc.
If your reproducible case could not be posted here publicly, please send it to the forge.help#autodesk.com and remove sensitive data or information before you send.
Hope this help.