= How Mutable works
= Features
= Mutable assets
== Customizable Object
== Customizable Object Instance
= Parameters
== Slider
== Enum
== Toggle
== Projector
= Mutable Editor (interface)
== Actions
Save, Compile, Stress test, Bake...
== Source Graph
== Graph Node Properties
== Object Propertes
== Preview Instance Viewport
== Preview Instance Properties
= Hierarchy
== Objects
== Groups
== Multiple Assets
= Object Interactions
= Texture Layouts
(IMPORTANT) The space that the materials added with extend material nodes will use at the final mesh layout depends on their relative block sizes. The root customizable object layout defines what a block cell resolution is. Artists will have more control on the final look if they take this into account when creating textures for extend material nodes.
Example: **TODO: Add images showing this in detail, as it may be hard to grasp without visualization of the case and the consequences.**
A parent object mesh with a layout of 2x2, with one bloc 1x2 and one 1x1. Only one image in the material, of dimensions 256x256.
A child object mesh with a layout of 1x1 and one block 1x1 added to the parent mesh, using an extend material node. Only one image in the material, of dimensions 256x256.
The final mesh with this child active will have a layout of 2x2 with one 1x2 block and two 1x1 blocks, one of them the one added by the active child. The final image size is 256x256, which means that the child object has had its resolution **halved**, as it now uses only a quarter of the space, a bloc of 1x1 which has an image size of 128x128.
The artist would have controlled the exact appearence of the child object material by making it 128x128 from the beginning.
= Object States