Skip to main content

Modular Avatar

Modular Avatar applies its components at Basis build time when it, NDMF and the Basis NDMF platform are installed in the project, and much of what it does then needs no conversion. Its components are read here so the parts that cannot work on Basis are handled rather than silently doing nothing.

Modular Avatar does not need to be installed. Its components are read from the prefab, and every one is named in the report.

Left to Modular Avatar​

Merge Armature, Bone Proxy, Mesh Settings and the rest of the components that rearrange the hierarchy or the meshes do platform-independent work. They are reported as left alone rather than as unrecognised, and nothing is written for them. Blendshape Sync and Parameters are listed with them but their build passes are VRChat-only in Modular Avatar 1.18.7, so they do nothing on Basis.

Rebuilt​

Menu Item targets VRChat's expression menu and Merge Animator targets its animator layer slots, neither of which exists on Basis, so clothing that installs a toggle this way does nothing there.

Read together, those two describe a toggle completely: the menu item names the parameter, the merged animator holds the layer that implements it. Those are traced and rebuilt as Vixxy controls, on the same terms as menu toggles from the avatar's own menu.

Object Toggle needs no animator. Its objects switch while its own object is active, and the menu item on that object drives it. Objects it does not name keep their authored state. An inverted toggle acts while the item is off. An item with no parameter gets the one Modular Avatar assigns from the object's name; default, saved and synced carry onto the control.

Paths inside a merged animator's clips are relative to the object the animator was merged at, and are rebased before anything is resolved. An Object Toggle entry is resolved by its object reference first, then by its path, which Modular Avatar records from the avatar root.

Reported, not rebuilt​

  • Shape Changer, Material Setter and Material Swap react to a menu item or bake a constant at build. Modular Avatar applies the constants itself on Basis when installed with the Basis NDMF platform; the menu-driven ones are listed as modularAvatar.menus.
  • Components that act on VRChat's own systems, its colliders, its head chop, its MMD layers. There is nothing for them to act on under Basis, and they are reported as modularAvatar.vrchatOnly.

Not covered​

  • Gimmick controllers whose layers are steered by several parameters at once, which are reported rather than guessed at.
  • Menu structure. A rebuilt control keeps its label, not its place in a menu tree.