一批可在应用程序之间导入和导出的 WorldAnchor。
| anchorCount | （只读）获取此 WorldAnchorTransferBatch 中的世界锚点的数量。 |
| AddWorldAnchor | 使用指定标识符将一个 WorldAnchor 添加到批次中。 |
| Dispose | 清理 WorldAnchorTransferBatch 并释放内存。 |
| GetAllIds | 获取当前映射到此 WorldAnchorTransferBatch 的所有标识符。 |
| LockObject | 针对提供的 ID 从 TransferBatch 中加载和应用 WorldAnchor，从而将提供的游戏对象锁定到世界。 |
| ExportAsync | 将输入 WorldAnchorTransferBatch 导出到字节数组中，系统会将该数组传递给 WorldAnchorTransferBatch.ImportAsync，以恢复原始 WorldAnchorTransferBatch. |
| ImportAsync | 将提供的字节导入 WorldAnchorTransferBatch 中。 |
| DeserializationCompleteDelegate | 在反序列化完成时使用的处理程序。 |
| SerializationCompleteDelegate | 在序列化完成时使用的处理程序。 |
| SerializationDataAvailableDelegate | 在某些序列号数据可用时使用的处理程序。 |
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.