![facerig pony facerig pony](https://4.bp.blogspot.com/-CR3qcz5KuME/WNRpgZaE9FI/AAAAAAABzso/e92azFZCoLsTK9fCNbqKy_PsiWDf4EsGgCLcB/s640/bottoms_up_by_jadekettu-db22zzh.png)
Idle animations – the system will parse the *.model3.json file and look for motion files grouped into the “Idle” group, first *.motion3.json file in that group will become the default idle animation.ĭefault idle pose (which can hide certain parts for the default pose) - *. exp3.json files in expressions/ folder of the avatar. These animations override tracking remapping) - the system will look for *. Special poses (single frame animations, the pose is kept. motion3.json files in the motions/ folder of the avatar. These animations override tracking remapping) – the system will look for *.
![facerig pony facerig pony](https://i.etsystatic.com/6530391/r/il/a004ef/3735064595/il_fullxfull.3735064595_47r8.jpg)
Special actions (full animations that run to the end and then the model goes to idle. Model meta info like *.moc3 (Live2D model file) and *.png textures will be parsed from the *. These are the specific files that are gathered automatically when importing a Live2D model in the Animaze platform: The Animaze system gathers as much information as possible from the runtime Live2D models in order to have them being run and rendered, out of the box, without too much additional custom configuration, as the models are thought and designed in the Cubism Editor. On a technical level, Live2D models are first rendered to an Animaze render target (basically a separate texture) and then rendered on the screen or used as a texture for various other items (e.g. The Animaze platform supports Live2D models that are exported for the runtime Cubism 3+ (tested with 3.0, 3.1, 3.2, 3.3 and 4.0 models). Animaze supports Live2D powered models for various Animaze items such as: 2D avatars, hybrid avatars (3D geometry with Live2D textures), animated backdrops, animated overlays and animated light masks (or light cookies).