MotionCapSpritesheet

Configuration Files

There are four different types of configuration files:

MVC Config File

This is the top-level configuration file, passed into render.start() to generate the animation. All parameters and options not specifically related to the Animated Drawing character, the BVH file, or the retargeting process go in here. Such parameters belong to one of three subgroups, in alignment with the Model-View-Controller design pattern. (Note: the ‘Model’ element of MVC is referred to as ‘scene’) Most of the available parameters are defined in animated_drawings/mvc_base_cfg.yaml. This file should not be changed. Instead, create a new mvc config file containing only the parameters that need to be modified. The rendering script will read the initial parameters from mvc_base_cfg.yaml and overwrite any parameters specified within the new mvc config file. See the example mvc config files for examples.

Character Config File

This configuration file (referred to below as char_cfg) contains the information necessary to create an instance of the Animated Drawing class. In addition to the fields below, which are explicitly listed within char_cfg, the filepath of char_cfg is used to store the location of the character’s texture and mask files. Essentially, just make sure the associated texture.png and mask.png files are in the same directory as char_cfg.

Motion Config File

This contains information about the motion used to drive the Animated Drawing. Currently, only BVH (BioVision Hierarchy) files are supported, but there is considerable flexibility regarding the skeleton specified within the BVH (note- only BVH’s with one skeleton are supported).

Retarget Config File

This file contains the information necessary to apply the motion specified by the motion config onto the Animated Drawing character specified in the character config. Note: below we refer to the BVH actor’s skeleton as skeleton and we refer to the Animated Drawing character’s rig as rig or character rig.