Render refresh for large models in Forge viewer - autodesk-forge

I am experiencing slower render refreshing for a model in forge viewer, than for the same file in the BIM360 viewer. I am wondering whether it is possible to obtain the same performance in the forge viewer, and if so, how?
I have been looking through old posts on the subjected, where various settings are suggested.
The function viewer.impl.setFPSTargets, as suggested in an old post from 2018, was tested, but even though less objects visibly refreshed, it was on the expense of the graphical performance during view rotations. The viewer.impl.toggleVizBuffer, suggested in the same post seems to have been removed.
Are there any other options or settings I can test to improve my performance?
The object flickering experienced in the forge viewer can be seen here:
Forge viewer render refreshing
Whereas in the BIM360 viewer, the performance is much smoother:
BIM360 render refreshing

The difference in performance might be related to the new, significantly improved viewing format that Forge introduced not too long ago: https://forge.autodesk.com/blog/svf2-public-beta-new-optimized-viewer-format. BIM 360 has been using it for some time now.
If you'd like to give it a shot yourself, take a look at https://forge.autodesk.com/en/docs/model-derivative/v2/developers_guide/notes/.

Related

Is it possible to download SVF2 model derivatives for offline viewing?

We are currently translating, downloading and viewing models within our application using the derivatives API, forge viewer, and targeting the SVF format. I am exploring doing the same thing using the SVF2 format but I have found evidence that this is not supported (for various reasons).
https://aps.autodesk.com/en/docs/model-derivative/v2/developers_guide/basics/preperation/
"...This means that SVF2 derivatives cannot be downloaded for offline viewing."
Wondering if this documentation is stale and this is actually possible now, or might be in the near future. I am looking for a concrete answer on this before I explore this any further. Thanks.
Currently there is NO public sample code that demonstrates how to download and view SVF2 in Forge Viewer. Only SVF1.
For SVF2, once you have figured it out (it's not that hard to download the 1000's mesh pieces), you'll need to host these mesh bits statically via the web-socket protocol. Finally, point Forge Viewer to your new host.
Don't forget to cache the viewer3d.min.js file, to comply with the EULA (found in the header). Since it's a cache, you'll need to show that the device can pull this file directly from Autodesk servers, when a cache flush occurs.
That's how I would do it.

Autodesk Forge Viewer loading heavy models VS BIM360 Viewer

We have a large .nwd model (1.6GB) that we are uploading directly to forge. I have hidden some elements in the viewer so only some of the elements are translated in the view to make it lighter. I am still having issues with SVF and SVF2 times to fully load the models on Forge. However I did a test on uploading to our hub on BIM360 and noticed it was significantly faster to upload and also the viewer renders the model a lot faster.
My question: Is it better to directly upload to the OSS on Forge or are there benefits in terms of load and rendering times to take the files directly from BIM360 via the Plugin integration workflow? Note: I am only considering upload and rendering times in this question and not other factors that could be beneficial to the end user.
BIM360 is built on top of Forge and it uses the exact same stack to store, translate, and preview your designs, so there should be almost no difference in loading and performance.
If you do see a significant difference in rendering performance, try the following:
open the model in your custom Forge Viewer app, and run the following command in the browser console:
NOP_VIEWER.model.isSVF2()
This should tell you whether your model really uses the SVF2 format.
open the model in another sample app, for example, https://github.com/petrbroz/forge-simple-viewer-nodejs (there's a branch called test/svf2 that is configured to load your models in SVF2), and see if the performance is the same
This should rule out any potential issues in your app's own code that could be affecting the performance.

What need for an automatic design project? My project is very slow

After showing the house to the forge viewer using a Ravit file, the user wants to modify the contents of the viewer and receive it as a Ravit file again. What function should I use to implement the above?
https://learnforge.autodesk.io/#/
I referred to it.
my project
I make input data and transfer this to design automation and get output file and file to translate viewer (this is 2 minutes).
This process is very slow I want better then this process.
https://www.autodesk.com/autodesk-university/class/Its-Not-Too-Late-Automate-Using-Forge-Design-Automation-Inventor-2021#video
This video looks very fast on work process. How to get fast work process like this video?
Thank you
The Forge Viewer is a viewer, not an editor.
The Forge viewer displays the translated version of a seed CAD model, in this case, a Revit RVT BIM.
You cannot edit or modify the CAD seed file in the viewer.
To achieve such a modification, you have to either use the original modelling software, in this case, Revit on the Windows desktop, or you can use the Forge Design Automation API for Revit.
That is what was used to create the Inventor sample you refer to.
Oops... re-reading your question, I see that you are already using design automation yourself as well. Congratulations on that.
However, there is no guarantee on the turn-around time for this process. The video may very well have been edited to eliminate a waiting period, of the user creating the video may just have been very lucky to achieve a faster turn-around time.
I am checking for you with the Forge team whether they used any additional tricks to speed things up in the video or in the true real-time processing. They confirm:
For Revit, a basic DA job should take up to 30-40 secs for the processing time alone. The derivative job for translation to viewer format could take another minute. So, 2 mins is expected. The sketch it demo video has a timer on the side to indicate real time.

Autodesk Viewer Performance

I have problem with large model on Forge Viewer. Although i had translate it to SVF2 but it take so long to load and with any action it rerender all time (i known it a part of process). Are there any solutions like Proxy in 3Dsmax or when camera far from model it show low LOD and when scroll in it show higher LOD? What can i do to speed up model? Appreciate any solutions.
UPDATE:
Would you be able to confirm that you are really using SVF2 in the viewer? For example, do you see the viewer communicating via WebSockets in the Network tab?
So far we've seen major performance improvements across all projects switching over to this new file format, but it's possible that your model is so large/complex that even SVF2 isn't helping. In that case I'm afraid we won't have other solutions, other than perhaps splitting your design into multiple models, and loading only those that you really need. For example, Navisworks designs are often split by area and/or discipline, and the models are then loaded selectively by specific users. Check out this demo (specifically the checkbox matrix in the sidebar): https://forge-industrial-construction.autodesk.io/facility/montreal.

Autodesk Viewer problem and missing elements from translation to SVF

I've been trying to encourage some of our less Revit-savvy building services engineers to utilise the Autodesk Viewer product. Unfortunately though, I have encountered a couple of problems, one of which I think I have solved and one which I am guessing is more to do with the Autodesk Viewer Applications programmed interaction with the model derivative API.
Initially I uploaded our services model with supporting architectural and structural models but the phase the solitary 3D view created in the viewer was "Existing" with a filter of "Show All". I managed to get around this by creating a 3D view in each model just called "3D" and setting the phase and filter as I like. Happy days.
Could this also have been better solved by setting generateMasterViews to true during the POST job on a custom Forge viewer app?
However, I am only getting some elements from the services model come through into the Autodesk Viewer application. Most notably it's missing ducts, sanitary pipework, cable trays, radiators. In the "3D" 3D view I have created everything is phased correctly, no issues from worksets, visibility graphics, view discipline is coordination (doesnt work to change to mechanical) and everything looks hunky dory in Revit. In the viewer though it's a different story. Even if I upload the services model on it's own. Strangely, in the 2d sheet views all the equipment and infrastructure is there fine, just in 3D it is now.
So my knowledge of Javascript and the Forge API is quite rudimental but I'm guessing the problem is with Autodesk Viewer's implementation of the model derivative API for when the model is translated to svf.
Does this sound correct?
Could it a bug within Autodesk's viewer app? I'm not too sure what the best Autodesk forum to post in would be.
Could it be a bug within the model derivative API? Or is it a setting that is beyond my knowledge?
I guessing I'm at a place where what I'm really after is a custom Forge viewer application to design in the functionality I am after, in this case control of phasing in the .svf file output and ensuring everything is coming through in the view.
Not the most interesting post by any stretch and if you're still reading now, thanks. But I'm sure I can't be the only one experiencing this problem. While I'd love to share a model to demonstrate whats happening, it's commercially sensitive unfortunately.
If anyone can shed a more technical light on
Cheers,Pete
Hi please make sure those elements are visible in 3D views and those 3D views are chosen in the publish settings of the Revit UI. Otherwise, the Model Derivative API will translate the default 3D view called {3D} only that might not contents proper element visibility configurations.
If this issue still persists after setting this up, please consider providing a none confidential model to forge[DOT]help[AT]autodesk[DOT]com for investigations. Thanks!