> For the complete documentation index, see [llms.txt](https://help.mimeeq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mimeeq.com/augmented-reality/unsupported-parameters.md).

# Unsupported AR Parameters

Avoid materials that look wrong in AR. Learn which material parameters WebAR does not support and how to work around opacity textures and bump level.

Below is a list of material parameters that are not supported in WebAR.

{% hint style="info" %}
As of 24/05/2022, you can add an alternative material that is used specifically for the AR-generated models. Read how to set this in [AR-Only Materials](/augmented-reality/ar-only-materials.md).
{% endhint %}

***

## Opacity texture

* Opacity texture does not work with AR. We recommend using **Albedo** with alpha instead.
* It mostly affects mesh fabrics, which are displayed as flat surfaces when the opacity texture is assigned.

### How to solve this

1. Download the existing opacity map.
2. Invert the colours – what is white should be black and vice versa.
3. Create an alpha channel on the opaque parts.
4. Export as a PNG.
5. Add the new map to the **Media Library**.
6. In the **Material Editor**, remove the opacity map from its slot and assign the new map to the **Albedo** texture slot, with the **HAS ALPHA** option on.
7. Under the **Transparency** section, select the **Alpha from Albedo texture** option.

{% hint style="warning" %}
Textures with transparency need a roughness level of 1 for AR purposes. Otherwise, the display will be distorted.
{% endhint %}

***

## Bump level

Although the bump (or normal) texture is compatible, the bump level is not. In AR, it will always use a level of 1 (100%). For example, if the level was set to 0.5, it will effectively appear twice as strong in AR as in the configurator.

### How to solve this

To reduce the bump strength, edit the bump map in an image editor to reduce the height. Then set the bump level to 1.

***

## Other unsupported parameters

<table><thead><tr><th width="60.078125">#</th><th>Parameter</th><th>Alternative</th></tr></thead><tbody><tr><td>1</td><td>Emissive</td><td>–</td></tr><tr><td>2</td><td>Metallic texture</td><td>Use metalness from the blue channel instead</td></tr><tr><td>3</td><td>Roughness texture</td><td>Use roughness from the green channel instead</td></tr><tr><td>4</td><td>Depth pre-pass and separate culling pass</td><td>–</td></tr><tr><td>5</td><td>Ambient texture strength</td><td>–</td></tr><tr><td>6</td><td>Real-time filtering</td><td>–</td></tr><tr><td>7</td><td>Subsurface</td><td>–</td></tr><tr><td>8</td><td>Anisotropy</td><td>–</td></tr><tr><td>9</td><td>Clear Coat</td><td>–</td></tr><tr><td>10</td><td>Sheen</td><td>–</td></tr></tbody></table>

If you need any help or have any questions, feel free to reach out to Mimeeq support.

***

## Related articles

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>AR-Only Materials</strong></td><td>Assign a simplified material for AR without compromising your browser-rendered model.</td><td><a href="/augmented-reality/ar-only-materials.md">AR-Only Materials</a></td></tr><tr><td><strong>Low-Poly Models</strong></td><td>Add a lighter model for AR so USDZ files load faster on Apple devices.</td><td><a href="/augmented-reality/low-poly-models.md">Low-Poly Models</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://help.mimeeq.com/augmented-reality/unsupported-parameters.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.