Changes between Version 5 and Version 6 of PMD_File_Format

Timestamp:

Jul 28, 2012, 8:49:57 AM (12 years ago)

Author:

historic_bruno

Comment:

Updated for version 4, multiple UV sets

PMD_File_Format

@@ -1 +1 @@
 PMD files store a model, which includes vertex positions, normals and texture coordinates, faces (all faces are triangles), rest state bone transformations (if bones are used), and prop point positions and transformations (where other models may be propped onto this one).
 
-The following is the version 3 PMD format.
+The following is the version 4 PMD format, which adds support for multiple UV sets per model (i.e. multiple texture coordinate pairs per vertex).
 
 Basic types:
@@ -16 +16 @@
  PMD {
     char magic[4];  // == "PSMD"
-    u32 version;  // == 3
+    u32 version;  // == 4
     u32 data_size;  // == filesize-12
  
     u32 numVertices;
+    u32 numTexCoords;  // number of UV pairs per vertex
     Vertex vertices[numVertices];
  
@@ -31 +32 @@
     PropPoint propPoints[numPropPoints];  // note: PropPoint has variable size (see below)
  }
- 
+
  Vertex {
     Vector3D position;  // in world space, matching the restStates pose
     Vector3D normal;
+    TexCoord coords[numTextureCoords];
+    VertexBlend blend;
+ }
+
+ TexCoord {
     float u, v;
-    VertexBlend blend;
  }
  
@@ -77 +82 @@
 }}}
 
-Some meshes also use PMD version 1. The only difference between this and version 2 is that no prop points are specified (there is no numPropPoints and no propPoints array).
+Some meshes also use PMD version 1. The only difference between this and version 2 is that no prop points are specified (there is no `numPropPoints` and no `propPoints` array).
 
-Some use PMD version 2. These store vertex positions/normals already transformed by the inverse of restStates. That can only work correctly when !VertexBlend has only a single non-zero weight, so PMD version 3 stores vertices in world space instead.
+Some use PMD version 2. These store vertex positions/normals already transformed by the inverse of `restStates`. That can only work correctly when `VertexBlend` has only a single non-zero weight, so PMD version 3 stores vertices in world space instead.
 
 The algorithm for calculating vertex data under a skeletal animation is:
@@ -95 +100 @@
  norm = normalise(norm)
 }}}
+
+PMD version 3 supported only one UV pair per vertex, so there was no `numTexCoords`.