we are experiencing errors in the latest version (7.55) of the forge viewer. When loading a Revit model, the following error displays in the browser console:
Failed to load model: New Construction. Error code: TypeError: e.target.clone is not a function
This is an SVF2 model that was translated using the generateMasterViews flag. New Construction is one of the master views names in this particular model.
I had a hunch this was due to the new update, so I downgraded our version from 7.55 to 7.54. After downgrading the issue no longer occurred. Was there a breaking change in 7.55 that we need to be aware of? I did not see anything in the changelog
Forge Viewer uses Semantic Versioning so none of the "minor" version updates should be breaking, but it could be some regression. In the call stack I see you're using AggregatedView. Have you tried loading your model in a simple Viewer3D or GuiViewer3D instance instead of that one? And could you share more details about how you're initializing the viewer and loading the models into it?
Related
We are using Autodesk Forge Viewer with DiffTool Extension to show the model differences between two versions of BIM360 models. Everything working fine except the count showing for the items that are Added/Removed/Modified. For the same model, the BIM360 compare tool shows different numbers compared to the DiffTool Extension. So, we are stuck with these mismatched numbers, any help on this issue is highly appreciated.
Thank you.
After investigating, this issue is addressed and resolved. The comments below for future reference:
ensure use the same model version urn
ensure load model with SVF2 data
const options = {
env: 'AutodeskProduction2',
api: 'streamingV2',
//getAccessToken: fetchForgeToken
accessToken: '<hard copy of token>'
};
ensure to specify the correct viewerable id (if not specified, viewer will load default 3D view, which might not be same to what are compared in BIM360).
We have a Revit model that doesn't seem to be running in Forge. It runs just fine in our local Revit Plugin, but it seems to 'hang' when trying it in Forge. After 3 hours, Forge just times-out...
The model isn't that big (less than 150MB), and we've handled many different (and larger) models before with success.
The logs from Forge doesn't tell us that much. It seems that the code from out plugin did not even run (we log the start of our code). Is there a way to get access to the journal file from Forge? Or is there an other way to see what might be the cause?
...
[05/03/2021 14:32:10] Initialize and get RCE: (VersionBuild) 21.1.20.44 (VersionNumber) 2021 (SubVersionNumber) 2021.2
[05/03/2021 17:31:52] Error: Revit Core Engine Core Console is shut down due to process time limit.
[05/03/2021 17:31:52] End script phase.
[05/03/2021 17:31:52] Error: An unexpected error happened during phase CoreEngineExecution of job.
[05/03/2021 17:31:52] Job finished with result FailedLimitProcessingTime
the workitemid:b27223519e824cdc90df80a1af6e718b
The issue is reproducible. So if you like we can send the model again and it will do exactly the same.
During loading 3d model, keep getting an error:
"Node that has both node children and fragment children! Not supported by flat storage".
Anyone know why? and how to fix this? ForgeViewer used to work without this error.
That error has been suppressed for recent versions (v6/7) - try upgrade to later versions.
If the error persists upload the model files to GDrive/weTransfer/Dropbox and drop the link to forge.help at autodesk.com so we can reproduce and check further.
I am trying to add customized geometry in forge-viewer, I am facing following issue:
The forge viewer I am using is 4.2.* , which uses THREE-R71. (All versions of forge-viewer uses THREE-R71).
The Customized Geometry I am trying to add in forge viewer is from THREE-R94. It throws exception:
THREE.Object3D.add: object not an instance of THREE.Object3D
I tried to upgrade the scene as : viewer.impl.scene=new THREE.Scene()
(THREE-R94)
But the renderer is still from THREE-R71, so renderer cannot render the scene.
Is there any way to add geometries and objects from latest threejs in forge-viewer?
You can't. Threejs has made breaking changes in many of its version upgrades, making them incompatible.
We have some forge articles that say otherwise, like this:
https://forge.autodesk.com/blog/how-add-newest-threejs-features-forge-viewer
It's possible to use different versions, depending heavily on which version, but almost all changes break the code compatibility.
I was unable to use different versions with the methods and objects I wanted.
If you don't want any trouble, stuck with r71 and extend the methods you need yourself.
We are experiencing troubles when using the model derivative API to translate and extract properties from a Revit Model.
As the screenshot implies, we have a custom property under Identity Data. But after translation its under Mark (the property on top of it).
It's a model created in Revit 2018.
Is this a bug?
kind regards
This issue has been logged as RVTLMV-4 in our internal case system to our engineering team to allocate time to investigate what happened yesterday and they're working on it. We will get back to you A.S.A.P. once there is any update. Apologizing for any inconvenience had caused to you.
I am seeing this issue too - custom properties appear to be coming through with "Cost" as the PropertyName. The ModelDerivative translation process seems to be the source of the bug. Happens on Revit 2018 or Revit 2019 model.
Is there any chance this issue can be escalated?
Our (live) Forge application relies on custom properties being correctly named and this current API release has broken our application when new models are uploaded.
Image of Model Derivative JSON
Image of Properties in Revit
#Eason Kang: FYI
I met this issue too. However, this issue happened when the translated field was not in the top of the Properties list. When this field was in the top, translation succeeded.
Hope this could give more information to your team.
I attached the image as below. First screenshot, it translated correctly. The 3 following screenshots, it translated wrong