> 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/configurator/rules/actions/billboard-mode.md).

# Billboard Mode for Meshes

Make specific meshes always face the camera, regardless of how the user rotates the model — useful for signs, labels, and interactive elements.

The **Billboard Mode** action makes specific meshes rotate to always face the camera as the user navigates around the model. Use it for signs, labels, or interactive elements that must stay visible from any angle.

## Setting up the rule

1. Go to the **Rules** section in your configurator.
2. Create a new rule or open an existing one.
3. Select **Set Billboard Mode** as the action type.
4. Add trigger conditions as normal.

## Billboard types

| Type               | Behaviour                                                   | Best for                                                                              |
| ------------------ | ----------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Full billboard** | Rotates on all axes to face the camera completely           | Text, icons, and interactive elements that must stay readable from any angle          |
| **Y-axis**         | Rotates vertically while keeping the mesh upright           | Signs and displays that should follow camera movement but stay oriented upright       |
| **X-axis**         | Tilts up and down while keeping horizontal position fixed   | Elements that need vertical tracking while maintaining depth and sideways orientation |
| **Z-axis**         | Rotates around the depth axis while keeping screen position | Elements that should spin without changing their relative position in the view        |

## Mesh and material settings

Select the specific meshes the billboard effect should apply to — you can select multiple.

{% hint style="warning" %}
Consider setting billboarded meshes to an **Unlit material**. Without it, you may see unrealistic lighting artefacts as the mesh rotates to face the camera.
{% endhint %}

## Use cases

* **Informational signs** — add text or icons that are always readable
* **Product labels** — keep labels visible regardless of model rotation
* **Interactive elements** — create clickable items that are always accessible
* **Feature highlights** — draw attention to specific parts of your configuration

{% hint style="success" %}
**Tips**

* Combine billboard meshes with highlight effects for attention-grabbing elements.
* Use billboard mode selectively — applying it to too many meshes can look unnatural.
* Avoid positioning billboarded meshes too close to other geometry, as they may intersect when rotating.
  {% endhint %}

## Related articles

* [Rules Overview](/configurator/rules/overview.md)
* [Actions Overview](/configurator/rules/actions.md)


---

# 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://help.mimeeq.com/configurator/rules/actions/billboard-mode.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.
