> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/content-creator-zh/mian-xiang-yi-dong-duan-gou-jian/kai-fa/optimize-performance.md).

# 性能

Decentraland 场景的移动端限制和性能目标，以及如何在 Creator Hub 中预览和衡量它们。

移动设备的资源限制比桌面或网页更严格。了解移动场景限制以及如何预览它们，有助于你发布一个能为最广泛受众流畅运行的场景。

## 移动场景限制

下表显示了在移动设备上运行时强制执行的限制。达到 **软限制** 会在性能面板中触发警告；达到 **硬限制** 将阻止场景加载。

| 指标         | 软限制       | 硬限制       |
| ---------- | --------- | --------- |
| 三角形        | 1,000,000 | 1,200,000 |
| 实体         | 4,800     | 6,000     |
| 网格（主体）     | 2,400     | 3,000     |
| 几何体        | 1,000     | 2,000     |
| 材质         | 400       | 500       |
| 纹理         | 400       | 500       |
| 碰撞体        | 1,200     | 1,500     |
| VFX 发射器    | 8         | 10        |
| 实时粒子       | 25,000    | 50,000    |
| 光源         | 8         | 16        |
| 阴影光源       | 2         | 4         |
| 内容大小       | 120 MB    | 150 MB    |
| 外部内容       | 40 MB     | 50 MB     |
| 内存（进程 RSS） | 1,638 MB  | 2,048 MB  |
| 绘制调用       | 1,000     | 2,000     |
| 性能（越高越好）   | 90%       | 85%       |

## 灯光和粒子

灯光行计数 **制作的** 每个图形配置只会启用一定数量最近的光源预算（从“超低”时的 0 到“高”时的 8），并且可能完全禁用阴影——因此，一个制作了 20 盏灯的场景仍然要承担这些场景成本，尽管一次最多只有 8 盏会发光。请按上限进行制作，不要依赖运行时预算。

粒子在运行时还会额外受到上限限制：每个发射器 5,000 个粒子，每个场景 50,000 个粒子。任何在制作时超过这些上限的内容都会被静默截断，因此超出它们只会浪费场景预算。

## 预览移动性能

你可以直接从以下位置检查场景的移动性能 **Creator Hub** ，无需部署到实体设备。

1. 在以下位置打开你的场景 **Creator Hub**.
2. 选择 预览 > 显示移动端二维码
3. 打开 **场景限制预览** ，点击手机右上角图标（带红色统计信息的显示器图标）。

![Creator Hub 中的移动场景限制面板](https://2460066822-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoPnXBby9S6MrsW83Y9qZ%2Fuploads%2Fgit-blob-65a2ca6fbdd8873f352431b5433817c0f944121d%2Fmobile_scene_limits.png?alt=media\&token=ed32dc52-362d-4af1-9a40-56e683774e94)

{% hint style="warning" %}
**在高画质下将性能保持在 90% 以上**

该 **性能** 数值是当前活动图形配置设定的 FPS 预算的百分比。分数为 **100%** 表示场景已达到完整的 FPS 目标。

始终在中端设备上测试，例如 **Samsung Galaxy A54** 并以 **高图形配置下性能分数超过 90%**。这能为大多数移动玩家提供流畅体验。参见 [硬件要求](/creator/content-creator-zh/mian-xiang-yi-dong-duan-gou-jian/yi-dong-ke-hu-duan/hardware-requirements.md) 了解参考设备。

你可以从以下位置更改图形配置 **游戏内菜单 → 设置 → 图形 → 将动态图形设为关闭 → 切换配置**.
{% endhint %}


---

# 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.decentraland.org/creator/content-creator-zh/mian-xiang-yi-dong-duan-gou-jian/kai-fa/optimize-performance.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.