autodesk-forge

问题 I am building an application around Autodesk Forge Viewer, where I add extra functionalities using basic functions from Viewer (coloring, isolating etc.) depending on client data. This application also allows you to upload a new model. After the upload and conversion process, metadata is extracted from the model using this Model Derivative API https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-GET/, which basically returns the tree of objects and their ids

问题 I am building an application around Autodesk Forge Viewer, where I add extra functionalities using basic functions from Viewer (coloring, isolating etc.) depending on client data. This application also allows you to upload a new model. After the upload and conversion process, metadata is extracted from the model using this Model Derivative API https://forge.autodesk.com/en/docs/model-derivative/v2/reference/http/urn-metadata-guid-GET/, which basically returns the tree of objects and their ids

问题 I was looking to upgrade the three js which is used in autodesk forge behind the scene and reason for upgrade is I am trying to use this library and this need three js r71 and above and inside forge viewer it seems they are using r33. I found a blog where it showed me how can I take the advantage of later three js. I followed it but seems like its not working. There forge viewer now have 2 references of three js and it gets confused which one to use and hence some of code behave weird here is

问题 I was looking to upgrade the three js which is used in autodesk forge behind the scene and reason for upgrade is I am trying to use this library and this need three js r71 and above and inside forge viewer it seems they are using r33. I found a blog where it showed me how can I take the advantage of later three js. I followed it but seems like its not working. There forge viewer now have 2 references of three js and it gets confused which one to use and hence some of code behave weird here is

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel

问题 SVF2 has different objectid s/ dbid s than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid . However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbId s to load only specified objects. How can I load only specified objects using SVF2 and the https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint? Can I access the svf2 objectIds anywhere or can I use the externalIds when calling Viewer3d::loadModel