> 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/compatibility-and-requirements.md).

# 兼容性与要求

查找 Convai Unreal Engine 插件支持的 Unreal Engine 版本、平台目标、角色骨骼兼容性和网络要求。

在安装 Convai Unreal Engine 插件之前，请确认你的环境满足以下要求 <code class="expression">space.vars.unreal\_plugin\_version</code>。以下页面介绍 Unreal Engine 版本支持、平台目标、角色骨骼兼容性和网络要求。

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Unreal Engine 版本</strong><br>支持的 Unreal Engine 版本范围、各版本的模块可用性，以及已知的版本相关注意事项。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/compatibility-and-requirements/unreal-engine-versions.md">Unreal Engine 版本</a></td></tr><tr><td><strong>Unreal Engine 平台支持矩阵</strong><br>Win64 和 Android 构建目标、必需的插件依赖项，以及 Android 麦克风权限处理。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/compatibility-and-requirements/unreal-engine-platform-support-matrix.md">Unreal Engine 平台支持矩阵</a></td></tr><tr><td><strong>角色骨骼支持</strong><br>哪些角色骨骼可开箱即用，哪些需要额外设置，以及角色骨骼设置指南链接。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/compatibility-and-requirements/character-rig-support.md">角色骨架支持</a></td></tr><tr><td><strong>网络和 API 要求</strong><br>插件运行所需的域名、协议、端口和防火墙规则。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/compatibility-and-requirements/network-and-api-requirements.md">网络和 API 要求</a></td></tr></tbody></table>

### 最低要求一览

| 要求                     | 最低要求                                                                 |
| ---------------------- | -------------------------------------------------------------------- |
| Unreal Engine          | <code class="expression">space.vars.unreal\_min\_version</code> 最低要求 |
| Convai 账户              | 必需 — 请在 [Convai 控制面板](https://convai.com)                            |
| API 密钥                 | 标准配置所需 — 在 Convai 控制面板中生成                                            |
| `AudioCapture` 插件      | 随引擎附带的插件；作为依赖项自动启用                                                   |
| `AndroidPermission` 插件 | 随引擎附带的插件；仅 Android 构建需要                                              |
| 构建目标                   | `Win64` 或 `Android`                                                  |

### 后续步骤

环境满足这些要求后，即可安装插件。

{% content-ref url="/pages/1e7f8ff5f6dd180c804dba754f19c21a745be07f" %}
[安装 Convai 插件](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/getting-started/install-the-convai-plugin.md)
{% endcontent-ref %}


---

# 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/compatibility-and-requirements.md?ask=<question>&goal=<user_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.
