Several comparisons of supported action model formats (MD2,MD5,SEA3D) "Go"

Recently, several different model formats have been used to perform character movements, documenting the pros and cons

1) MD2 data content: Record all action vertex data data format: Binary action file: Action file merged in a model file file size: The action is a lot of memory: Many initialization speed: Fast model and map: separate, need manual control map loading and processing 2) MD5 data content: Bone data Record Data format: string action file: Action file with original model independent file size: The action is very large, but because it is a string format, you can use zip compression to obtain a larger compression ratio of memory: very small initialization speed: Because of the string data parsing processing, Very slow model and mapping: separation, need to manually control map loading and processing 3) SEA3D data content: Bone data record Data format: binary action file: action file merged in a model file file size: Relatively small footprint: very small initialization speed: Soon the model and the map: The map is merged in the model file, do not need to self-processing through the above comparison, found that SEA3D will be a better choice of action model

Several comparisons of supported action model formats (MD2,MD5,SEA3D) "Go"