> For the complete documentation index, see [llms.txt](https://enoch-app.gitbook.io/enoch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enoch-app.gitbook.io/enoch/developers-integration-guide/unity-integration/faqs-for-unity.md).

# FAQs for Unity

<details>

<summary><strong>Is there a way to cache (store) avatars locally to reuse them without downloading each time?</strong></summary>

Yes. Starting with SDK 1.12.0, avatars are cached at runtime and therefore loading much faster. See [Avatar Caching](/enoch/developers-integration-guide/unity-integration/optimize/avatar-caching.md).

</details>

<details>

<summary>Can I create an avatar directly in-engine? </summary>

No. It is not currently possible to directly create an avatar inside the engine. You need to use a WebView. See [Avatar Creator Integration](/enoch/developers-integration-guide/unity-integration/avatar-creator-integration.md).

</details>

<details>

<summary>How do I change the Render Pipeline of my Unity Project with avatars to URP?</summary>

There are no specifics when it comes to changing the render pipeline with Enoch avatars. Depending on the Unity version you use, you need to follow the general guide for changing the Render Pipeline.

</details>

<details>

<summary>How can I integrate the Avatar Creator into my VR application?</summary>

You can do so by using a 3rd party library called Vuplex WebView. See [Avatar Creator for VR and PC](/enoch/developers-integration-guide/unity-integration/avatar-creator-integration/vr-and-pc.md).

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://enoch-app.gitbook.io/enoch/developers-integration-guide/unity-integration/faqs-for-unity.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.