MSH - Revision history

Tmp7704: update of the Type attribute

2011-05-16T17:48:20Z

update of the Type attribute

ChewyGumball: /* Constants */ they are not unsigned floats...

2010-06-10T03:45:25Z

‎Constants: they are not unsigned floats...

Tmp7704: added COLOR Semantic

2010-04-14T00:08:57Z

added COLOR Semantic

ChewyGumball: /* Example .MSH.XML file */

2010-03-10T05:30:12Z

‎Example .MSH.XML file

ChewyGumball: Updated the semantics part

2010-03-10T05:29:09Z

Updated the semantics part

ChewyGumball: added link to custom model import/export tools

2009-11-26T00:39:06Z

added link to custom model import/export tools

ChewyGumball: /* Example .MSH.XML file */

2009-11-20T03:17:08Z

‎Example .MSH.XML file

ChewyGumball at 03:16, 20 November 2009

2009-11-20T03:16:06Z

ChewyGumball: /* Example .MSH.XML file */

2009-11-13T01:29:27Z

‎Example .MSH.XML file

ChewyGumball: added example XML based only on provided schema

2009-11-13T01:22:35Z

added example XML based only on provided schema

@@ Line 174: / Line 174: @@
 						COLOR - vertex color
-			Type="string" -- indicates how many elements and of what type are in the tuples in the CDATA.
+			Type="string" -- indicates how many elements and of what type are in the tuples in the CDATA, as well as the output format for the provided values (as described in the Constants section) Appears to be case-sensitive.
-						"Float4" (four floating point numbers),
-						"Float2" (two floating point numbers),
+                                                "FLOAT1" (single floating point numbers)
-						"Short4" (four integers)
+                                                "FLOAT2", "FLOAT16_2" (two floating point numbers)
 		-->
 		data <!-- contains CDATA with tuples of numbers. For example, a Float2 type MSH had this:

@@ Line 110: / Line 110: @@
              /// 2 16-bit floats
              DECLTYPE_FLOAT16_2 = 15,
-             /// 4 16-bit unsigned floats
+             /// 4 16-bit floats
              DECLTYPE_FLOAT16_4 = 16,
              DECLTYPE_UNUSED = 0xffffffff
@@ Line 148: / Line 148: @@
              DECLUSAGE_UNUSED = 0xffffffff
 </pre>
 == Example .MSH.XML file ==

@@ Line 56: / Line 56: @@
                </optional>
                <attribute name="Semantic">
-                 <data type="NCName"/> <!-- "POSITION", "Indices", "TEXCOORD", "TANGENT", "BINORMAL", "NORMAL", "BLENDWEIGHT", "BLENDINDICES" -->
+                 <data type="NCName"/> <!-- "POSITION", "Indices", "TEXCOORD", "TANGENT", "BINORMAL", "NORMAL", "BLENDWEIGHT", "BLENDINDICES", "COLOR" -->
                </attribute>
                <optional>
@@ Line 163: / Line 163: @@
 			IndexCount="int" -- If semantic is "Indices", this is the number of integers in the data's CDATA.
 			IndexType="string"> -- Every example of this has the value "Index32", without exception.
-			Semantic="string" -- "POSITION", "Indices", "TEXCOORD", "TANGENT", "BINORMAL", "NORMAL", "BLENDWEIGHT", "BLENDINDICES"
+			Semantic="string" -- "POSITION", "Indices", "TEXCOORD", "TANGENT", "BINORMAL", "NORMAL", "BLENDWEIGHT", "BLENDINDICES", "COLOR"
 						POSITION - vert coordinates
 						TEXCOORD - texture coordinates
@@ Line 173: / Line 173: @@
 						BLENDINDICES - the indices of the bones which the above weights apply to the index is the index of the bone in the accompanying
                                                                 MMH's corresponding NodeMesh tag
-		    Type="string" -- indicates how many elements and of what type are in the tuples in the CDATA.
+			Type="string" -- indicates how many elements and of what type are in the tuples in the CDATA.
-							 "Float4" (four floating point numbers), "Float2" (two floating point numbers), "Short4" (four integers)
+						"Float4" (four floating point numbers),
 		-->
 		data <!-- contains CDATA with tuples of numbers. For example, a Float2 type MSH had this:

@@ Line 168: / Line 168: @@
 						TANGENT/BINROMAL/NORMAL - tangent/bitangent/normal of a vert
 						Indices - the vert numbers (from the POSITION data block) which the faces are made from.
-                                                             Note that the tangents/bitangents/normals/blendweights/blendindices are by vertex and the ordering MUST be the same as
+                                                             Note that the texcoords/tangents/bitangents/normals/blendweights/blendindices are by vertex and the ordering MUST be
-                                                            in the POSITION block
+                                                            the same as in the POSITION block
 						BLENDWEIGHT - the movement weights of up to 4 bones on this vertex
 						BLENDINDICES - the indices of the bones which the above weights apply to the index is the index of the bone in the accompanying

@@ Line 155: / Line 155: @@
 <?xml version="1.0" encoding="UTF-8"?>
 <ModelMeshData name="string" Version="int">
-   <!-- must have 0 or more of these, obviously having at least 1 would be required for being useful -->
+   <!-- must have 0 or more of these, obviously having at least 1 would be useful -->
 	<MeshGroup name="string"><!-- optional attributes: Optimize="string"<< all,none, or indicies -->
-	  <!-- must have at least 1 of these -->
+	  <!-- must have at least 1 of these, will almost always have at least 6 -->
-	  <!-- I believe each separate data element contains data of the type specified in Semantic
-			--dont know what default behaviour is when Semantic is not specified--
-		   for instance, first will hold all vert data, second hold normals, third hold triangle indecies etc
-	   -->
 		<Data>
 		<!-- optional attributes:
 			ElementCount="int"  -- If semantic is not "indices", this is the number of tuples in the CDATA.
-			IndexCount="int" -- If semantic is "indices", this is the number of integers in the data's CDATA.
+			IndexCount="int" -- If semantic is "Indices", this is the number of integers in the data's CDATA.
 			IndexType="string"> -- Every example of this has the value "Index32", without exception.
 			Semantic="string" -- "POSITION", "Indices", "TEXCOORD", "TANGENT", "BINORMAL", "NORMAL", "BLENDWEIGHT", "BLENDINDICES"
-		        Type="string" -- indicates how many elements and of what type are in the tuples in the CDATA.
+						POSITION - vert coordinates
-					 "Float4" (four floating point numbers), "Float2" (two floating point numbers), "Short4" (four integers)
+						TEXCOORD - texture coordinates
 		-->
 		data <!-- contains CDATA with tuples of numbers. For example, a Float2 type MSH had this:

@@ Line 1: / Line 1: @@
 '''MSH''' (mesh) files define a 3D mesh, to be referenced by [[MMH]] files when creating models in the game.
-MSH files are defined using XML source files with the extension .msh.xml. These files are run through the GraphicsProcessorMSH.exe program (found in the Dragon Age\Toolset\export_processors directory) to produce binary files that can be used by the game directly.
+MSH files are defined using XML source files with the extension .msh.xml. These files are run through the GraphicsProcessorMSH.exe program (found in the Dragon Age\Toolset\export_processors directory) to produce binary files that can be used by the game directly. See [[3rd_party_extensions]] for custom model export and import.
 :GraphicsProcessorMSH [-outdir <out-dir>] [-platform <x360,pc,ps3>] [options] [-indir<input-directory> / <input-file>]

@@ Line 6: / Line 6: @@
 Other options include:
-:-mmdtogff{{undocumented}}
+:-mmdtogff{{undocumented}} - what mmdtogff means or does is unknowns besides it is required to compile msh.xml files.
 == msh.xml schema in RELAX NG 1.0 format ==

@@ Line 147: / Line 147: @@
              // error/other/unset
              DECLUSAGE_UNUSED = 0xffffffff
 </pre>
 [[Category:File types]]