> 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/gaze-attention.md).

# 注视注意力

查找注视注意力系统的指南和参考，该系统允许玩家通过注视世界对象来引导 Convai 角色的注意力。

凝视注意力允许玩家通过注视带有标签的世界物体来引导 Convai 角色的关注点。请在 `UConvaiPlayerComponent`上启用此功能，为道具添加 `UConvaiObjectComponent`，角色便能对玩家正在注视的对象作出响应。

{% hint style="info" %}
凝视注意力基于场景元数据和角色动作构建。开始之前，请确认你的关卡具备以下条件：

* 至少有一个世界 Actor 添加了 `UConvaiObjectComponent` ，并且其 **Name**非空。如果你还没有为对象添加标签，请参阅 [场景元数据快速入门](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/scene-metadata/scene-metadata-quick-start.md) 。
* **启用动作** 已在以下位置的聊天机器人设置中勾选： **Convai | Actions** → **Environment**。如果尚未配置动作，请参阅 [角色动作快速入门](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/character-actions/character-actions-quick-start.md) 。
* `UConvaiPlayerComponent` 已添加到玩家 Pawn，且 **启用凝视注意力** 已开启。

如果你刚开始使用此功能，请先阅读 [凝视注意力的工作原理](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention/how-gaze-attention-works.md) 了解完整流程，然后继续阅读 [凝视注意力快速入门](https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention/gaze-attention-quick-start.md).
{% endhint %}

<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>凝视注意力的工作原理</strong><br>了解追踪流程、注意力提升计时器、组件范围内的目标选择，以及注意力源锁定规则。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention/how-gaze-attention-works.md">注视注意力的工作原理</a></td></tr><tr><td><strong>凝视注意力快速入门</strong><br>在 Player Component 上启用凝视注意力，并验证角色是否会在玩家注视带标签的对象时作出响应。</td><td><a href="https://docs.convai.com/api-docs/zh/cha-jian-yu-ji-cheng/convai-unreal-engine-plugin/features/gaze-attention/gaze-attention-quick-start.md">注视注意力快速开始</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/features/gaze-attention/gaze-attention-reference.md">注视注意力参考</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/features/gaze-attention/gaze-attention-usage-examples.md">注视注意力使用示例</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/features/gaze-attention/troubleshoot-gaze-attention.md">排查凝视注意力问题</a></td></tr></tbody></table>


---

# 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/gaze-attention.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.
