Forge model with texture translation issues - autodesk-forge

I am using the steps detailed at this link -- https://forge.autodesk.com/blog/show-revit-custom-texture-map-viewer
to translate and view the Revit model with texture. But textures are not reflected in the Forge viewer.

Apologizing for any inconvenience had caused to you. This is a known issue logged as RVTLMV-1097 by our engineering team, and they are still evaluating it currently.
Therefore, please remember the RVTLMV prefixed id for future reference, and you're welcome to track updates anytime in the future via sending an email to forge[dot]help[AT]autodesk[dot]com with this id.
We appreciate your understanding and patience.

Related

Autodesk Forge Data Viz components work with an SVF model but not an SVF2 model

Our team participated in the forbidden city forge accelerator and the forge developer team helped us create our own version of a digital twin. We had a large model so we decided to test the SVF2 model derivative. The model did load in the viewer but the data viz sprites did not appear.
When we tried the SVF version everything worked as expected.
So we are unable to determine what the problem is or how to resolve it and any help would be appreciated.
Thank you.
Update 2021-05-14:
SVF2 is supported now, please refer to:
https://forge.autodesk.com/en/docs/dataviz/v1/developers_guide/quickstart/replace_model/
https://github.com/yiskang/forge-dataviz-iot-reference-app/commit/efdee567819d8e98bd0351aa4ac6590d79768075
During Forbidden City forge accelerator, we found the SVF2 is unsupported and reported it as HYPER-260 to let our engineering team allocate time to evaluate the possibility and explore the root cause. This means that the DataViz extension doesn't SVF2 currently, so please stay tuned with us. We appreciate your understanding and patience.

BIM 360 Compare documents

is there any way to revive data about what has been changed between versions (remove and add and modify):
via forge Model Derivative API, now I am able to get all the metadata of any Revit files but in total so I am not sure what elements added or .....
the problem we have a lot of files, and it's really hard to run a test to compare modes for each object
thank you :)
I am not aware of any built-in BIM360 or Forge functionaloity for obtaining that information.
I would suggest that you very clearly define exactly what information you wish to keep track of and determine how that can be obtained from a model, e.g., as you suggest, via the Forge Model Derivative API.
Then, you can create a snapshot of that data yourself and implement the functionality to track changes in it as you wish.
The Buiilding Coder discusses and shows how to solve the exact same task for Revit BIMs using the Revit API on the Windows desktop:
Tracking Element Modification
Implementing the TrackChangesCloud External Event
Those articles provide ideas and guidelines on some aspects to take into consideration addressing the same task in Forge.

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!

Forge Viewer AR

We have eagerly and daily been watching this blogpost for any update on the source code. Our team are really interested in looking into AR technology similar to that integrated with the Forge Viewer. Does any of the Forge developers happen to know whether there's any updates coming or if there's any other AR material to look into at the moment? Thanks a lot.
Pex. That blog post should have a reference to the 'beta sign up' page. I'll update it now.
You should start with the signup page to give you a feel for the toolkit. Unfortunately, we have found an issue with load performance for large scenes we are addressing. This has delayed that blog post and release of that source code.
Here is the beta sign up page: beta.autodesk.com/
and then select: 'AR|VR Toolkit'
There is a downloads section and tutorials as well as a beta-forum to add your feedback.
Let me know if you have trouble with the signup.

Obtaining room/area information from Forge api

I need to get room/area objects with the hierarchy of linked objects from the Revit model via Forge. Right now I am using this project as a starting point. Unfortunately, the room information is lost. As far as I understand, it is removed during the translation process. There are some workarounds like this one, but it doesn't seem to work for our case. Is there any straightforward way to retrieve room information from rvt in Forge?
Although there is not directly way to get room information via the Forge translator, there are still some workarounds to archive this:
Open Revit project with room elements only via the Navisworks, and upload to Forge for translation, use this result as the secondary model of your viewer app as well.
Extract room info. and object relationships via Revit API, and use external mapping feature of the Forge Viewer to rebuild partial relationships between elements and rooms, if room geometry info. is not required.
Hope this help.
Unfortunately room information is not exposed through the Forge translation at the moment. We have a change request pending about it because several developers have been asking this feature. It will be provided in the future but at the moment the best workaround is the link that you pointed out. Sorry for the bad news.