> For the complete documentation index, see [llms.txt](https://harpiagames.gitbook.io/low-poly-color-changer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://harpiagames.gitbook.io/low-poly-color-changer-documentation/support/faq.md).

# FAQ

**Why should I save the FBX file?**&#x20;

For optimization proposes. Without saving, there may be a lot of mesh instances inside the memory.

**Can I use LowPolyColorChanger in builds?**

&#x20;No. LowPolyColorChanger is an editor only script.

**Why do some transparent Colors "don't work"?**

&#x20;You are probably using the default material for it. If you want to use transparency, please use the transparent material located under the Materials folder.

**Why does my object's color change slightly when I apply the LowPolyColorChanger component?**

The slight color change when applying the LowPolyColorChanger component is due to color precision adjustments. The component simplifies color variations in textures, merging similar colors for ease of use. For detailed settings and handling, see the 'Color Precision' section in the documentation.

Does it work on Android or iOS apps?

Yes, it does. Any model modified with Low Poly Color Changer can be used on any platform, no matter if its mobile, AR, VR, Desktop, etc. All the changed are made on the Editor layer of development.


---

# 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:

```
GET https://harpiagames.gitbook.io/low-poly-color-changer-documentation/support/faq.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
