I am following this tutorial: https://forge.autodesk.com/en/docs/model-derivative/v2/tutorials/xtract-metadata/task2-upload_source_file_to_oss/
https://i.stack.imgur.com/7k6P9.png
I am getting that error ^ and the size of my object is still 1kb when I try downloading it, so it never finalized.
Any suggestions? Better tutorials to follow for Model Derivative API?
Thanks
We do have other tutorials like https://learnforge.autodesk.io/#/tutorials/viewmodels
and also tools like https://oss-manager.autodesk.io
You can try those I believe.
Related
According to the autodeskissue.pngautodeskissue.png is from the ‘https://forge.autodesk.com/en/docs/acc/v1/reference/http/issues-issue-types-GET/’, as the photo shown there is ‘subtypes’ data in the response, but my response come from ‘my.png’my.png, there is no ‘subtypes’, so I wondering the issue is it still in beta mode, or is it I doing wrong?
To get subtypes, you need to add the query parameters include=subtypes. e.g.
https://developer.api.autodesk.com/construction/issues/v1/projects/:projectId/issue-types?include=subtypes
I am using https://github.com/Autodesk-Forge/recap-walkthrough-photo.to.3d for converting image to 3D, but at the end of the execution its throwing an error when the image is getting processed.
Any Help on this would be highly appreciated.
data: {
Usage: '0.44537496566772',
Resource: '/photoscene/jsjshdfjsdhgjfsdjf/progress',
Photoscene: {
photosceneid: 'jsjshdfjsdhgjfsdjf',
progressmsg: 'ERROR',
progress: '100'
}
}
is the error. Reason for this error is not coming.
Please contact the support via forge (dot) help (at) autodesk (dot) com, providing as much information as possible, e.g.:
how many images you uploaded, and what was their resolution?
how did you upload these files? If you used a custom code or script, could you share it?
when did you run these requests, and what was the Forge Client ID you used for them?
EDIT:
While the response isn't very descriptive, the engineering team confirms that this error is typically caused by insufficient input data. In this particular case only 4 images were uploaded, and the algorithm wasn't able to reconstruct the 3D screen from those.
I need to go back to home default view on Forge Viewer, after a few times go for searching and follow some tutorials to load extension i have something like this
let res = _viewer.loadExtension('Autodesk.GoHome')
if(res){
_viewer.getExtension('Autodesk.GoHome', (gohome)=>{
gohome.active()
})
It not work for me and have an error like "gohome is not a function" ?. Did i do something wrong ?
You have a race condition problem in your code.
I will not get into details here, but briefly speaking, things like "gohome is not a function" usually means that you use an object before it was fully created/initialized.
Try changing your code into:
_viewer.loadExtension('Autodesk.GoHome').then(
(gohome) => {
gohome.active();
})
This should solve the problem.
I am trying to explore design automation for Revit by exploring the code at https://github.com/Autodesk-Forge/design.automation-nodejs-revit.window.family.create.
When I run the application, I get an error message
"Failed to create the family:( "
and the following log -
jstree.min.js:5 [Deprecation] document.registerElement is deprecated
and will be removed in M73, around March 2019. Please use
window.customElements.define instead. See
https://www.chromestatus.com/features/4642138092470272 for more
details. (anonymous) # jstree.min.js:5 ForgeTree.js:348 Uncaught
TypeError: Cannot read property 'className' of undefined
at refreshTypeList (ForgeTree.js:348)
at HTMLSpanElement.spanRemove.onclick (ForgeTree.js:339)
Also while following the instruction in the provided code, most of the links give in README.md for Postman collection (https://github.com/Developer-Autodesk/design-automation-for-revit/blob/master/Docs/AppBundle.md ) was in-accessible to me.
The error you mentioned is on the browser side and it's related to the jsTree, which needs updating due to a browser change. We're fixing it on our samples.
About the overall error, it probably due to a missing setup on the sample. As a suggestion, I would suggest a basic tutorial for Design Automation. Back to the error, you probably need to check the reports.txt to see what happened during the Workitem execution.
We're also fixing a few broken links on the documentation, sorry about that. Are you looking for anything specific?
Update
Design Automation requires code:all scope.
I'm running into issues with the realtime API and I'm unable to track down the root cause due to the obfuscation of the realtime library.
All I can see in the console is something like this when loading the document:
TypeError: a.b is null
...,A(a.aa,a));var f=b.requestParams,g;for(g in f)f.hasOwnProperty(g)&&e.X(g,f[g]);...
api (line 211)
Any ideas how to resolve such an issue?
There is not a de-obfuscated version available. If you post the specifics of what you are trying to accomplish, and the full stack of when you get an error, someone may be able to help.