> 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-unreal-engine-plugin/features/vision.md). # 视觉在 Unreal Engine 中为 Convai 角色提供场景视觉，使其能够在对话期间对关卡中可见的内容作出反应。视觉功能可让 Convai 角色在对话过程中看到 Unreal 场景。你只需为角色添加一个场景捕获组件，将其指向角色应观察的区域，Convai 就会将这些画面与语音一同使用。


视觉工作原理了解在会话期间，场景帧如何被捕获、发现并发送到 Convai。	视觉的工作原理
Vision 快速入门向角色添加 Environment Webcam 组件，并在一次编辑器内运行会话中确认场景视觉功能正常工作。	视觉快速开始
视觉帧来源配置内置的 Environment Webcam 组件、其渲染目标、捕获速率以及活动来源选择。	视觉帧源
自定义视觉组件当内置的 Environment Webcam 组件无法覆盖你的图像管线时，创建一个 C++ 帧来源。	自定义视觉组件
Vision 蓝图引用蓝图可访问的视觉枚举、组件属性、事件以及 Chatbot 集成节点参考。	视觉 Blueprint 参考
视觉使用示例应用常见的蓝图模式，用于自动开始捕获、手动开始和停止、FPS 调整以及来源切换。	视觉使用示例
排查视觉问题诊断缺失的视觉上下文、启动失败、空白渲染目标、无效来源以及捕获速率问题。	排查视觉问题

### 下一步先从 [视觉工作原理](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/vision/how-vision-works.md) 开始，了解捕获管线。然后再按照 [Vision 快速入门](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/vision/vision-quick-start.md) 进行操作，再在 [视觉帧来源](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/vision/vision-frame-sources.md) 中调整捕获设置，或在 [视觉使用示例](/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/vision/vision-usage-examples.md). --- # 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-unreal-engine-plugin/features/vision.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.