问题描述
SVF2 与 SVF1 具有不同的 objectids/dbids.在这个 SO-Answer 中，建议使用 externalId 而不是 objectid.但是，viewer.loadModel(svfUrl,{ids:[dbIds...]}) 需要 dbIds 来仅加载指定的对象.如何使用 SVF2 和 https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/:urn/metadata/:guid/properties 端点仅加载指定的对象?我可以在任何地方访问 svf2 objectIds 还是在调用 Viewer3d::loadModel 时可以使用 externalIds?
SVF2 has different objectids/dbids than SVF1. In this SO-Answer, it was advised to use externalId instead of objectid. However, viewer.loadModel(svfUrl,{ids:[dbIds...]}) takes dbIds 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?
推荐答案
你说得对，SVF1 dbID"和SVF1 dbID"是有区别的.和SVF2 dbID"- SVF2 格式的 ID 是持久的"，这意味着在同一设计文件的不同版本中，单个 ID 将引用相同的设计元素(SVF1 中并非如此).
You're right, there's a difference between the "SVF1 dbIDs" and the "SVF2 dbIDs" - the IDs in SVF2 format are "persistent", meaning that in different versions of the same design file, a single ID will reference the same design element (which was not the case in SVF1).
不幸的是，该平台有一些部分(例如 loadModel 查看器方法和 /modelderivative/v2/regions/eu/designdata/:urn/metadata/:guid/properties 端点)没有赶上"与 SVF2 呢.在这些更新可用之前，您必须在新旧 dbID 之间"进行映射.手动，这本身就是另一项重要的任务.
Unfortunately, there are parts of the platform (like the loadModel viewer method and the /modelderivative/v2/regions/eu/designdata/:urn /metadata/:guid/properties endpoint) that have not "caught up" with SVF2 yet. And before those updates are available, you would have to map "between the old and new dbIDs" manually which is itself another, non-trivial task.
这篇关于如何使用 SFV2 在伪造查看器中仅加载特定对象?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！