> 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/embodiment/quick-start.md).

# 具身化快速入门

将凝视模块添加到现有 Convai 角色，使其与玩家进行眼神接触，并在 Play 模式下立即可见。

将 Gaze 模块添加到现有的 Convai 角色，并在 Play 模式下确认角色会与玩家进行眼神交流。待场景中已有可正常运行的 `ConvaiCharacter` 后，可使用本页首次查看角色化表现，然后再配置其他四个模块。

***

### 前提条件

* 场景中已有一个 `ConvaiCharacter` ，且它已能连接并响应——如果尚未完成，请先完成 [验证设置](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/getting-started/validate-your-setup.md) 。
* 角色上需要有一个 `Animator` 。使用 **Humanoid** 骨架时，Convai 可以自动映射头部和眼睛；使用 **Generic** 骨架也可以，但需要通过 `Character Rig` 绑定至少指定头部。

{% hint style="info" %}
尝试模块前无需创建设置资源。每个模块都使用经过调校、效果良好的内置默认值运行；配置文件用于之后调整行为，而不是用于启用模块。
{% endhint %}

***

### 添加 Gaze 模块

{% stepper %}
{% step %}

#### 选择角色

在 Hierarchy 中，选择附带 `GameObject` 的对象，该对象上有 `ConvaiCharacter` 组件。
{% endstep %}

{% step %}

#### 添加 Gaze 组件

在 Inspector 中，选择 **Add Component**，然后选择 **Convai > Embodiment > Gaze**。这会将 `ConvaiGazeController` 添加到角色上。

Convai 还会自动添加模块所需的共享基础设施——一个 `EmbodimentContext` 和一个 `StandardRigBinding` 。无需手动添加。
{% endstep %}

{% step %}

#### 检查骨架检测结果

打开 **Convai > Embodiment Editor** 并选择 **Setup** 选项卡。选择 **Set Up This Character** ，即可查看 Convai 检测到的面部混合形状规范、检测置信度以及解析出的骨骼。

此步骤是可选的——Gaze 无需此步骤也能运行——但你可以借此查看 Convai 的检测结果，再进入 Play 模式。
{% endstep %}
{% endstepper %}

***

### 验证设置

进入 Play 模式并与角色开始对话。Gaze 的默认眼神交流模式为 `Natural` ——当你在角色周围移动时，它的眼睛和头部应该会明显跟随你，而不是一直盯着空间中的某个固定点。

{% hint style="success" %}
**预期结果：** 对话开始后不久，角色的头部和眼睛会转向你；在对话进行期间，它们会持续追踪你的位置。
{% endhint %}

***

### 故障排查

如果角色的眼睛和头部没有移动，请打开 **Convai > 具身编辑器 > 设置** 并检查检测到的绑定约定及其置信度——置信度较低是最常见的原因。请参阅 [角色绑定设置](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/character-rig-setup.md) 以修复骨骼或混合变形映射，或参阅 [具身功能故障排查](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/troubleshooting.md) 了解所有故障模式。

***

### 后续步骤

{% content-ref url="/pages/528b8780a5fa83913d2d3f95cdbf6b1a0c52b073" %}
[具身化如何运作](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/how-embodiment-works.md)
{% endcontent-ref %}

{% content-ref url="/pages/dddb9a87015e6befbe3c15caf6aa6b2df224fa33" %}
[角色骨架设置](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/character-rig-setup.md)
{% endcontent-ref %}

{% content-ref url="/pages/260c8f480c6e05ba6ea9db729322298e970606cc" %}
[具身化预设](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unity-sdk/embodiment/embodiment-presets.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-unity-sdk/embodiment/quick-start.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.
