In the new Docs 360, there is the phase view on the left side.
Phase image
In this project, the phases are bounded together on a single document, but on other project, the phases are created as a seperate revit document which I assume to be related to the size involved for each view(is this true?). On testing , these seperated revit phase document are not viewable on forge web-api (the error i received is GET /api/manifest call failed Not Found). The question is, Would it be possible to replicate the phase view in Forge? And if no How do I open the seperate revit phase document created when uploading to cloud.
And in previous question I've asked about the possibility of getting room information in forge which I've been told to be impossible. Upon inspecting the phase view in docs, I've come to notice that there is the Room element exist (clickable etc etc). Is this a bug ? If no, does bringing phase view to the forge web app will allow me to click on room element?
Room Image
I have talked with our engineering team, and learnt that the room/space are exported by Revit extractor now. But currently, they are only supported in BIM360 Docs, not in Forge Viewer unfortunately.
Related
https://github.com/Autodesk-Forge/forge-revit.ifc.scheduler
I want to build same app, I have cloned it on local path.It is not working.Kindly help, or give another solution or give some idea.
I have tried Dynamo revit files stored in Bim 360.It takes too much time to open and close files in batch process.Make research and get Idea about forge .cloned project
https://github.com/Autodesk-Forge/forge-revit.ifc.scheduler
But not working.
I did it according to the example on the official website, but the model couldn't be loaded。I don't know why, I followed the tutorial, and I checked the API should be open normally，I think I need help. Here's a screenshot of the error；
I see two possible explanations for this type of error:
The model is coming from A360 or Fusion Teams. If that's the case, please note that models uploaded to these applications are not translated automatically by the Forge Model Derivative service (hence the viewer error stating that there are no "viewables" to load). You have to open the designs in their owning application first to initiate the translation process, and then you can try accessing them from your own Forge application.
It's possible that the sample application is having issues with some of the characters used in the file names. Check if the same error happens when you name your files using English alphabet.
I have created a web application for viewing models using the AutoDesk Forge Viewer, and I want to be able to add this onto a website. I used this tutorial: https://learnforge.autodesk.io/#/tutorials/viewmodels (using node.js for the language option).
The goal is to have the user access the viewer application from the website. I have been using VS code live server for testing. However, when I link the page that has the viewer into my own website, the viewer does not load the buckets or allow for creation of new buckets. It is just stuck on a loading symbol like below:
[Loading screen][1]
Could I please have the following questions answered:
What is the proper way to embed this application onto a website in the manner I have described above?
What part of the code controls where the buckets are loaded in?
Thank You.
[1]: https://i.stack.imgur.com/4Xlfv.png
LearnForge tutorial is an example on how to work with Forge API. As a web app, it depends on how the developer(you) designs the user interface, workflow, and data management.
e.g. you can remove the panel of bucket & object lists ,keeping the viewer only in the UI. while you will need to design how to provide the object id (urn) which will be loaded in the viewer. Normally, you would need to setup your own users management, logging process etc, and set your own user permission. Then the user logs in, the web app lists all files (objects) he has permission to check, and when one file is selected, get the urn and load the model in Forge Viewer.
if the end user of your app is BIM360 users, you could take advantage of BIM360 data management workflow, which follows the same permission specified with BIM360. Then the other tutorial will be a good start.
https://learnforge.autodesk.io/#/tutorials/viewhubmodels
In any case, the workflow and UI are defined by yourself. I hope this explains. If you have any further questions that need a meeting call, please feel free to check the calendar of our team:
https://calendly.com/autodeskforge
I've been following this tutorial to successfully upload Revit & AutoCad files to Bim360 Docs using 2-legged tokens. I am also using the 'x-user-id' header.
The problem I'm having is after the model is published to Bim360 docs, it’s not viewable in the browser and derivatives are empty (see below). It appears that the model translation job never occurs. Isn’t this supposed to happen automatically for Bim360 Docs files? Could the 2-legged token be hindering this process? Is there another step I'm missing?
I've even tried to manually kick off a translation job after uploading the file by calling this API with NO success.
This image is the result of calling the manifest API.
empty derivatives
Thank you for reporting it to us. Our engineering team is investigating the problem. But you should see the progress status 100% now, please haveing a try, thanks!
We have integrated AutoDesk Forge Viewer. We are sending a request to the Forge API's for conversion (using Model derivative API). After closing the Viewer, If we need to show the same file again, Currently we are posting the dwg file again for conversion to view it.
Instead is there a way so save the svf file in my local system so that I need not call the Forge web service twice for the same file.
According to the pricing, for every simple conversion job, its going to cost 0.2 credits.
Please suggest how I can avoid this same conversion second and n number of times.
Thank you,
Shiva Kumar
Unless the DWG file has changed, you do not need to upload the DWG file again and/or POST a translation again. If you do this, you will effectively consume 0.2cc. Instead, just reference the URN you had received after upload/translation when starting the viewer. The 'bubble' or SVF persists on the backend depending of the storage policy you chose. For example, if you create a transient bucket, the file and bubble will persists for 24h, temporary for 1 month, and persistent forever.
I have found a reference to how to iterate through the bucket and see the files which are present in the bucket.
We can login in the below live demo using the forge credentials.
Live Demo
Source Code
Thanks.