> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/features/scene-metadata.md). # 场景元数据查找场景元数据的指南、组件参考和示例——该功能让 Convai 角色感知 Unity 场景中的对象。场景元数据让 Convai 角色能够感知 Unity 场景中的对象。添加一个 `ConvaiObjectMetadata` 组件到任意 GameObject，以描述它是什么——该静态名称、描述和包含标志会在会话连接时自动发送，并在之后你编辑它们时实时重新同步到每个已连接的角色，无需编写脚本。同一个组件还可以公开可选的跟踪属性，在会话激活期间将对象的实时运行时状态报告给角色。


场景元数据如何工作了解注册和传递流程，以及何时使用场景元数据与动态上下文。	场景元数据的工作原理
场景元数据快速开始注册你的第一个场景对象，并确认它已到达 Convai。	场景元数据快速开始
场景元数据组件参考用于 `ConvaiObjectMetadata`的每个 Inspector 字段，包括跟踪属性，以及 `ConvaiSceneMetadataCollector`.	场景元数据组件参考
场景元数据脚本 API `ConvaiObjectMetadata`, `ConvaiMetadataRegistry`，以及 `ConvaiSceneMetadataCollector` 公共方法。	场景元数据脚本 API
场景元数据使用示例医疗培训、工业安全、博物馆导览、运行时对象排除以及跟踪属性的完整设置。	场景元数据使用示例
排查场景元数据问题用于诊断 AI 忽略对象、验证错误、元数据负载为空以及依赖项失败。	排查场景元数据问题

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/features/scene-metadata.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.