> For the complete documentation index, see [llms.txt](https://doc.realvirtual.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.realvirtual.io/components-and-scripts/changing-mus.md).

# Changing MUs

Components for dynamically modifying MU (Movable Unit) appearance, materials, and behavior during simulation.

## Available Components

### Visual Modifications

* [**PartChanger**](/components-and-scripts/changing-mus/partchanger.md) - Changes the visual appearance of MUs by switching between predefined appearances
* [**MUSwitcher**](/components-and-scripts/changing-mus/muswitcher.md) - Controls visibility of grouped GameObjects within MUs based on sensor detection
* [**MaterialChanger**](/components-and-scripts/changing-mus/materialchanger.md) - Dynamically changes materials on MU components

### Processing Operations

* [**Cutter**](/components-and-scripts/changing-mus/cutter.md) - Simulates cutting operations on MUs with visual feedback

## Key Features

* **Sensor Integration**: Changes triggered by sensor detection events
* **PLC Integration**: Control via PLCInputBool signals for industrial automation
* **Visual Feedback**: Real-time appearance changes during simulation
* **Logic Integration**: Works with Logic Steps and automation sequences

## See Also

* [MU (Movable Unit)](/components-and-scripts/mu-movable-unit.md) - Base MU functionality
* [Sensors](/components-and-scripts/sensors.md) - Sensor components for triggering changes
* [Logic Steps](/components-and-scripts/defining-logic/logicsteps.md) - Automation logic integration


---

# 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://doc.realvirtual.io/components-and-scripts/changing-mus.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.