Mirage Pro/LOD Group Settings: Difference between revisions
lcassets>Mirage docs import (Restructured Mirage Pro documentation (bulk import)) |
m (1 revision imported) |
(No difference)
| |
Latest revision as of 17:18, 8 July 2026
Mirage documentation
- Overview & Quick Start
- Setup the target(s)
- Quality Settings
- Information Panel
- LOD Group Settings
- Runtime Baking
- Post-Baking Adjustments
- Memory Optimization
- Compatibility & Limitations
Need help? support@leochaumartin.com · Discord
LOD Group Settings
This category is not crucial — you can always modify it afterwards — but it can save a lot of time. If you just want to bake the impostor to a prefab without adding it to the scene, untick the Automatic Setup field.
There are four possible scenarios:
| Scenario | Result |
|---|---|
| None of the input meshes are part of a LOD Group | A LOD Group is added on the common ancestor. All source renderers are added to LOD0 and the impostor is added to LOD1 following the given settings. Cross-fading is added for smooth transitions. |
| There is already a LOD Group but no impostor | The impostor is added as an additional LOD level following the given parameters. All source renderers must belong to either no LOD or the same LOD level from the same LOD Group, to avoid nested LOD Group errors. |
| There is already a LOD Group with an impostor | The impostor is replaced using the same relative height transition. Impostors are detected via the ImpostorReference script attached to the LOD Group. To keep several impostors in the same LOD Group, safely delete the ImpostorReference component before baking. The previous impostor's prefab is not deleted — only the instance in the scene is replaced. |
| There is no common ancestor for the input objects | Baking is not possible. |