> 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/wu-dai-ma-ti-yan/convai-xr-animation-capture-app/creating-animations-for-ai-avatars.md).
# 为 AI 头像创建动画
使用 Meta Quest 头显捕捉逼真的动画，让你的 AI 头像栩栩如生——无需动捕服。
## **概览**
使用 **Convai XR 动画捕捉** 应用，你只需在 VR 中亲自演示，就可以为你的 AI 角色创建自定义动画。这些动画可帮助你的头像在对话中自然地表达自己——无论是在 Unity、Unreal、Avatar Studio 还是 Convai Sim 中。
{% hint style="warning" %}
***还没有设置好应用？***\
请前往 [Convai XR 动画捕捉应用设置指南](/api-docs/zh/wu-dai-ma-ti-yan/convai-xr-animation-capture-app/convai-xr-animation-capture-app-setup.md) 再继续。
{% endhint %}
***
## **在 VR 中录制动画**
### **步骤 1：查看现有动画（可选）**
当你启动应用时，你会看到你的 **动画仪表板**。在这里，你可以：
* 查看之前录制的动画
* **重播** 它们，看看效果如何
* **删除** 任何你不再需要的内容
***
### **步骤 2：开始录制**
1. 在应用中，点击 **“开始录制”**.
2. 将开始五秒倒计时。
3. 开始 **表演你的动画。**
* 例如：挥手、指向、做手势等。
***
### **步骤 3：停止并查看**
1. 完成后，点击 **“停止”**.
2. 你可以通过按下 **“重播动画”** 按钮。
* 来查看已录制的动画。这有助于你决定是保存、重录还是丢弃。
***
### **步骤 4：命名并保存**
1. 输入一个 **清晰且具有描述性的名称** （例如， *挥手问候*, *向左指*).
2. 点击 **“保存并上传”**.
该动画现在已上传到你的 **Convai 仪表板**，可随时用于：
* 分配给 AI 头像
* 用于 **Unity**, **Unreal**, **Avatar Studio**，或 **Convai Sim**
***
### **继续构建你的动画库**
录制并保存多个动画，以充实你的库。这些动画可在各个项目中重复使用，使你的头像能够 **智能地做出手势** 在对话中——让你的虚拟体验更具吸引力和真实感。
---
# 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/wu-dai-ma-ti-yan/convai-xr-animation-capture-app/creating-animations-for-ai-avatars.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.
