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
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).
Please be patient, I'm new to Forge, C-language, and web-apps, so I'm going to misuse terms and nomenclature like crazy. I'm working on converting a configurator from Configurator 360 to Forge. I created the original Inventor Assembly and iLogic and we farmed out the Forge side of the project. We use our ERP system to generate the engineering number we want from Forge. That number is passed to Forge through a URL and reversed engineered to select all the right options in Inventor. Then .step, .pdf, and .svf files are created with the viewer presenting the .svf and two buttons to download the .step or .pdf respectively. The .step and .pdf look just like they used to from C360 but my viewable is just wrong.
capture from Forge-viewer wrong capture from Inventor-step right
The color of the object should be black and it's white and all parts that are created using iFactories are missing. I don't know if this is two separate issues or caused by the way we are zipping the files for conversion.
I know I haven't given much to go on as to code that could be wrong because I'm not really sure where to start. I do see this in the Immediate Window
Loading model: dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6cHJpbmNlX291dHB1dF9idWNrZXRfMTVlNDY2ZDYyNDU5NGQ3YmIyMjg0OWM3MDMxODgzOTAxL1BDNDAyMDAyMEEwMC0yOTBYVFhMLAAAAA
Exception thrown: 'Microsoft.JSInterop.JSException' in System.Private.CoreLib.dll
And then it throws that same exception 9 more times... that appears to be one less time then the number of parts that are missing from the viewer.
Any help is much appreciated even if it's just asking questions that might point me in the right direction.
Edit 1:
Found a new error that might help. It shows up if I refresh the browser.
ERROR: Cannot read properties of undefined (reading 'getRoot')
TypeError: Cannot read properties of undefined (reading 'getRoot')
at Object.loadDocumentNode (https://localhost:44365/_content/ForgeFunctions/forgeViewerJsInterop.js:168:40)
at https://localhost:44365/_framework/blazor.server.js:1:70369
at new Promise (<anonymous>)
at e.beginInvokeJSFromDotNet (https://localhost:44365/_framework/blazor.server.js:1:70335)
at https://localhost:44365/_framework/blazor.server.js:1:26442
at Array.forEach (<anonymous>)
at e.invokeClientMethod (https://localhost:44365/_framework/blazor.server.js:1:26412)
at e.processIncomingData (https://localhost:44365/_framework/blazor.server.js:1:24223)
at e.connection.onreceive (https://localhost:44365/_framework/blazor.server.js:1:17308)
at WebSocket.i.onmessage (https://localhost:44365/_framework/blazor.server.js:1:46784)
Edit 2:
I noticed when all the files were being copied to make the zip to create the svf, that a subdirectory was created for the iPart Members (named after the iFactory.) I use a flat zip file (all files in one big folder) so I tried creating a zip with a file structure to match our Vault structure. I then got errors that parts couldn't be found. Lots of other things were tried and then I found this blog post. I used the first option to add the "/p" in my Activity Command Line and set "autodesk.inventor.interop -> Embed Interop Types = false". My iFactory Members are now in the viewable!
Anyone have ideas on what's wrong with the colors? I believe "black" is the only color that is wrong. I do think it's a modified appearance from the appearance library but again the .step file looks good (aka is the color I set) so what in the viewer controls colors?
Edit 3:
So... I fixed the colors... I opened the file in Inventor. Opened the Appearance Browser and Unchecked "Self Illumination" for the "Black" color. Saved, Tested, Worked. Went back in turned "Self Illumination" back on, Saved, Tested, Still Works! So didn't really change anything just changed it and changed back and boom.
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?
A customer has created a custom Inventor Material Library: all his parts are defined to use these custom materials in order to obtain a very realistic representation of model.
When I try to convert his assembly files (exported with Pack & Go) with Autodesk FORGE Model Derivative, the output models (no different between SVF and SVF2 format) contains some white surfaces associated to the parts defined with custom materials.
Interessant: in developer console of browser I've found an error HTTP 400 related to the Galvinized_2_svf_tex_mod.png.
What can I do in order to obtain a better SVF model?
I've found the cause: see Appearances with enabled Self-Illumination are translated to white when creating a shared view from Inventor
The Material Library of customer has the "Self Illumination" active!
I just had a similar issue. I removed the "Self Illumination" and the color came through. I then added "Self Illumination" back to the color, but added the assembly file to my zip with copy and paste in leu of Pack and Go. And the color still works in the viewer.
Don't know if that always works, but if anyone else needs SI, it might be worth a try.
P.S. Good to know that shared views can be a quick test of the Viewer. Hadn't thought of that before.
I want to build enterprise solution for configurator base on Autodesk Inventor models and drawings. I want to have ability to change dimension of assembly (witdh, depth, length and another). I want to see changes on model in real time (something like here but with changes dimensions in custom values: https://tylko.com/shelf/bookcases/1429438/?cv=0&board=cat_all__type_all__id_4267)
As a result I want to have fully documented model with drawings.
Can Forge do that? Is there any demo?
Yes, here's a sample application that does something similar.
https://forge-rimconfigurator-inventor.herokuapp.com/
You can find the source code of the above application here:
https://github.com/sajith-subramanian/forge-rimconfigurator-inventor
There also is another intricate sample available. You can find it here:
http://inventor-config-demo.autodesk.io/
The source code of the above sample is available here:
https://github.com/Autodesk-Forge/forge-configurator-inventor
Thank you for response. Provided samples are different than:
https://tylko.com/shelf/bookcases/1429438/?cv=0&board=cat_all__type_all__id_4267
My sample is dynamic. Is there a possibility to not wait for change update. Same as you can see change directly in Inventor.