> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/assets/materials/multi-material.md).

# Multi Material

The **MultiID** operator lets you assign different materials on a single mesh. This works by associating mesh faces to different “IDs” or “groups”. You can set up your model’s **MultiID** values in another software or add a **Material IDs** operator in the model asset.

To use this feature apply a material with a **MultiID** operator to a model that has been setup with material id values. Then the corresponding **Material ID Asset** of the **MultiID** operator is applied to the model asset.

<table data-header-hidden><thead><tr><th width="177"></th><th></th></tr></thead><tbody><tr><td><strong>Default Color</strong></td><td>Defines the default color when no material asset is assigned to the Material ID group. We use a color picker that can use RGB, HSV or HEX inputs.</td></tr><tr><td><strong>Material ID 0 - Material ID 29</strong></td><td>This is where a user applies which material asset is applied to the corresponding <strong>Material ID</strong> number. You need a model asset with Material IDs in order for this to work correctly.</td></tr><tr><td><strong>Is MultiID</strong></td><td><strong>MultiID</strong> when checked enables having multiple materials on a single mesh.</td></tr></tbody></table>

{% hint style="info" %}
Avoid using MultiID Materials, as they can have a serious impact on performance depending on the mesh density
{% 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 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://community.threekit.com/platform-documentation/project-data/assets/materials/multi-material.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.