Mirage Pro/Compatibility and Limitations
Revision as of 14:00, 8 July 2026 by lcassets>Mirage docs import (Restructured Mirage Pro documentation (bulk import))
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
Compatible objects
Mirage impostors are compatible with any object that has a MeshFilter and a MeshRenderer attached. Translations (all axes), scaling (all axes) and rotation (around the vertical axis only) are supported.
Limitations
Due to their nature, Mirage impostors have a few limitations.
- Full rotation compatibility
- Impostors are not rotated around the X and Z axes even if their parent is.
- Lossy scale
- Mirage uses the lossyScale of the source objects. If the source objects are skewed by nested non-uniform scaling and rotation, the impostor may appear close to the source but unskewed.
- Shadows
- Mirage impostors are compatible with shadows, but they are not physically correct, since only the alpha-clipped quad is projected rather than a dedicated shadow pass. Shadows are correct when the light comes from the front or the back, but not from the sides of the impostor. This is a simplicity choice: a correct shadow would add a GPU-intensive shader pass, and shadows are usually not even visible from the impostor's nominal distance. It also keeps Mirage natively pipeline-independent, since Shader Graph is not yet designed to add custom passes.
Contact
Didn't find what you were looking for? Feel free to contact me by email or on Discord.