This document provides instructions for importing custom Live2D avatars into the FaceRig Mobile application. To import an avatar, users need to zip the avatar folder containing the .moc and .json files as well as texture subfolders in a zip file. They then upload the zip file to a web hosting service and copy the link into the FaceRig Mobile app. Avatars must follow certain specifications like using power of 2 dimensions for textures in order to work properly in FaceRig. Additional optional files like an icon image and .cfg file can provide extra functionality for things like custom camera positioning.
This document provides instructions for importing custom Live2D avatars into the FaceRig Mobile application. To import an avatar, users need to zip the avatar folder containing the .moc and .json files as well as texture subfolders in a zip file. They then upload the zip file to a web hosting service and copy the link into the FaceRig Mobile app. Avatars must follow certain specifications like using power of 2 dimensions for textures in order to work properly in FaceRig. Additional optional files like an icon image and .cfg file can provide extra functionality for things like custom camera positioning.
This document provides instructions for importing custom Live2D avatars into the FaceRig Mobile application. To import an avatar, users need to zip the avatar folder containing the .moc and .json files as well as texture subfolders in a zip file. They then upload the zip file to a web hosting service and copy the link into the FaceRig Mobile app. Avatars must follow certain specifications like using power of 2 dimensions for textures in order to work properly in FaceRig. Additional optional files like an icon image and .cfg file can provide extra functionality for things like custom camera positioning.
This document provides instructions for importing custom Live2D avatars into the FaceRig Mobile application. To import an avatar, users need to zip the avatar folder containing the .moc and .json files as well as texture subfolders in a zip file. They then upload the zip file to a web hosting service and copy the link into the FaceRig Mobile app. Avatars must follow certain specifications like using power of 2 dimensions for textures in order to work properly in FaceRig. Additional optional files like an icon image and .cfg file can provide extra functionality for things like custom camera positioning.
FaceRig Mobile External Live2D Avatars Documentation
Import existing avatars
To add custom Live2D avatars to the mobile application you need to upload a zip archive containing the avatar data.
For example: 1. if you have an avatar and its data is inside a folder, you will have to archive the folder (zip format) 2. then upload it to the web (dropbox, google drive, file share websites, or others) 3. copy/paste the link in the mobile application in the designated input text field
You can use this link as example. [Gogu Rabbit]. Now follow the instructions from step 3. Once you have uploaded an avatar to the web, you can share that link with everyone.
You can also use existing Live2D avatars from other community sources like the FaceRig Steam Workshop.
Note: You can find more information on our forums - FaceRig Forums.
Creating new avatars
Mandatory stuff
Live2D avatars can become FaceRig avatars, if they meet several characteristics. The avatars must be exported with Cubism 2.1 SDK or lower.
FaceRig uses the *.moc and *.json files of the Live2D avatar, along with the subfolder holding the Live2D textures. These textures must be dimensioned by the power of two, in order to work in FaceRig. That means something like square image of 512,1024, 2048 etc.
The Live2D avatar data must be uploaded to the mobile device using the in app UI (found in the live2D avatar list) using a zip archive URL. The archive can contain multiple avatars. Each avatar folder name must be the same as the *.moc file.
These above specifics enable FaceRig to identify and use the Avatar. However, for extended features the Live2D avatar must respect further rules.
Additional descriptive specifications
In order to be easily found in the avatar list, the avatar must have an icon image file and an optional *.cfg file.
The icon must be a png square image, by the power of two dimensions, something like 256/256. The icon must be named “ico_”+avatar_name+”.png”, where avatar name is the name of the *.moc file.
The *.cfg file enables additional features, such as positioning your avatar in the scene. The *.cfg file must be named avatar_name.cfg and contains a JSON string.
Camera position
If you want to frame your avatar in the scene in a custom way then you must set a custom Camera position. For doing this, write the following command line in [avatar_name].cfg:
“camera_position”: [pos_x, pos_y, pos_z]
where pos_x, pox_y, pos_z represent the 3d position coordinates.
Physics
Adding physics simulation to some avatar's features requires you to have a
the_avatar_name.physics.json file in avatar's folder. For creating and exporting it, please read further here: http://sites.cybernoids.jp/cubism_e/live2dviewer/basic/phisics/setting
