three.js/examples/models/skin_and_morph.dae at dev · JavaScriptsShare/three.js

619 lines (605 loc) · 34.6 KB
<?xml version="1.0" encoding="utf-8"?>
<COLLADA xmlns="http://www.collada.org/2005/11/COLLADASchema" version="1.4.1">
   <contributor>
     <author>gcorson</author>
     <authoring_tool>Maya8.5 | ColladaMaya v3.03</authoring_tool>
     <comments>Collada Maya Export Options:
bakeTransforms=0;exportPolygonMeshes=1;bakeLighting=0;isSampling=0;
curveConstrainSampling=0;removeStaticCurves=1;exportCameraAsLookat=0;
exportLights=1;exportCameras=1;exportJointsAndSkin=1;
exportAnimations=1;exportTriangles=0;exportInvisibleNodes=0;
exportNormals=1;exportTexCoords=1;
exportVertexColors=1;exportVertexColorsAnimation=0;exportTangents=0;
exportTexTangents=0;exportConstraints=1;exportPhysics=1;exportXRefs=1;
dereferenceXRefs=0;cameraXFov=0;cameraYFov=1</comments>
     <source_data>
file:///C:/Documents%20and%20Settings/gcorson/Desktop/Crystal%20Content/AmandaCrush/untitled
     </source_data>
   </contributor>
   <created>2007-04-04T23:08:51Z</created>
   <modified>2007-06-21T18:50:45Z</modified>
   <unit meter="0.01" name="centimeter"/>
   <up_axis>Y_UP</up_axis>
 <library_materials>
   <material id="lambert1" name="lambert2">
     <instance_effect url="#lambert1-fx"/>
   </material>
 </library_materials>
 <library_effects>
   <effect id="lambert1-fx">
     <profile_COMMON>
       <technique sid="common">
         <lambert>
           <emission>
             <color>0 0 0 1</color>
           </emission>
           <ambient>
             <color>0 0 0 1</color>
           </ambient>
           <diffuse>
             <color>0.9 0.5 0.5 1</color>
           </diffuse>
           <transparent opaque="RGB_ZERO">
             <color>0 0 0 1</color>
           </transparent>
           <transparency>
             <float>1</float>
           </transparency>
           <index_of_refraction>
             <float>1</float>
           </index_of_refraction>
         </lambert>
       </technique>
     </profile_COMMON>
   </effect>
 </library_effects>
 <library_geometries>
*******************************************************************************************
This is a pretty standard mesh for the same as used in the skinning example.  It's a 6 
sided cylinder divided into 6 sections with a total of 42 vertices.  It is used as the
base mesh (source) in the morph controller.
******************************************************************************************* 
   <geometry id="pCylinderShape1" name="pCylinderShape1">
     <mesh>
       <source id="pCylinderShape1-positions" name="position">
         <float_array id="pCylinderShape1-positions-array" count="126">20 -90 -34.641
-40 90 -0.000005 -20 90 34.641 20 90 34.641 40 90 0</float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-positions-array" count="42" stride="3">
             <param name="X" type="float"/>
             <param name="Y" type="float"/>
             <param name="Z" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <source id="pCylinderShape1-normals" name="normal">
         <float_array id="pCylinderShape1-normals-array" count="468">0 0 -1 0 0 -1
0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026
0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026
0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026
0 -0.5 0 0 -1 0 0 -1 0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026
0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
-1 0 0 -1 0 0 -1 0 0 -1 0 0 -1 0 0 -1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0</float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-normals-array" count="156" stride="3">
             <param name="X" type="float"/>
             <param name="Y" type="float"/>
             <param name="Z" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <source id="pCylinderShape1-map1" name="map1">
         <float_array id="pCylinderShape1-map1-array" count="122">0.578125 0.020933
0.979066 0.578125 0.979066 0.65625 0.84375</float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-map1-array" count="61" stride="2">
             <param name="S" type="float"/>
             <param name="T" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <vertices id="pCylinderShape1-vertices">
         <input semantic="POSITION" source="#pCylinderShape1-positions"/>
       </vertices>
       <polylist material="lambert2SG" count="38">
         <input semantic="VERTEX" source="#pCylinderShape1-vertices" offset="0"/>
         <input semantic="NORMAL" source="#pCylinderShape1-normals" offset="1"/>
         <input semantic="TEXCOORD" source="#pCylinderShape1-map1" offset="2" set="0"/>
       </polylist>
     </mesh>
   </geometry>
*******************************************************************************************
This mesh is the same as the one above, but one of the rings of verticies has been moved 
outwards to create a bulge in the middle of the cylinder.  This geometry is used as the
morph target (aka deformer or blend shape) in the morph controller.
A morph can operate on ANY or ALL of the sources so you could morph positions, UVs and 
normals all at the same time.  The sources to be morphed have to be referenced by <input>
tags inside the <vertices> tag in both the morph target and the base mesh.  In this example
only the positions are referenced by the <vertices> tag so they are all this morph will effect.
Since only the positions are being morphed, everything but the target__pCylinderShape1-positions
source and the <vertices> tag could be deleted from this <geometry> and it the morph
should still work.  The DCC tool should get all the other information from the base mesh, so
there is no need to duplicate it here.
This extra information may still be exported by some DCC tools for a variety of reasons.
The only time it is actually REQUIRED is if the morph target geometry is also instantiated in
the scene by having an <instance_geometry> tag point directly to it's geometry tag.
Due to a bug in the ColladaMaya Maya expects the polylist information to be present in the 
morph target or the morph will not be instantiated.
******************************************************************************************* 
   <geometry id="target__pCylinderShape1" name="target__pCylinderShape1">
     <mesh>
       <source id="target__pCylinderShape1-positions" name="position">
         <float_array id="target__pCylinderShape1-positions-array" count="126">20 -90 -34.641
40 90 0</float_array>
         <technique_common>
           <accessor source="#target__pCylinderShape1-positions-array" count="42" stride="3">
             <param name="X" type="float"/>
             <param name="Y" type="float"/>
             <param name="Z" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <source id="target__pCylinderShape1-normals" name="normal">
         <float_array id="target__pCylinderShape1-normals-array" count="468">0 0 -1
0 0 -1 0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
-0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026
0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026
0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026
0 -0.5 0 0 -1 0 0 -1 0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
0 -0.5 -0.866025 0 -0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026 0 0.5 -0.866026
0 -1 0 0 -1 0 0 -1 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025 0 -0.5 -0.866025
-1 0 0 -1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0 0 1 0</float_array>
         <technique_common>
           <accessor source="#target__pCylinderShape1-normals-array" count="156" stride="3">
             <param name="X" type="float"/>
             <param name="Y" type="float"/>
             <param name="Z" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <source id="target__pCylinderShape1-map1" name="map1">
         <float_array id="target__pCylinderShape1-map1-array" count="122">0.578125 0.020933
0.84375</float_array>
         <technique_common>
           <accessor source="#target__pCylinderShape1-map1-array" count="61" stride="2">
             <param name="S" type="float"/>
             <param name="T" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <vertices id="target__pCylinderShape1-vertices">
         <input semantic="POSITION" source="#target__pCylinderShape1-positions"/>
       </vertices>
       <polylist material="target__lambert2SG" count="38">
         <input semantic="VERTEX" source="#target__pCylinderShape1-vertices" offset="0"/>
         <input semantic="NORMAL" source="#target__pCylinderShape1-normals" offset="1"/>
         <input semantic="TEXCOORD" source="#target__pCylinderShape1-map1" offset="2" set="0"/>
       </polylist>
     </mesh>
   </geometry>
 </library_geometries>
 <library_controllers>
*******************************************************************************************
This controller defines a morph with pCylinderShape1 as the source and 
target_pCylinderShape1 as the morph target (deformer)
*******************************************************************************************
  <controller id="pCylinderShape1-morph" name="blendShape1">
     <morph method="NORMALIZED" source="#pCylinderShape1">
*******************************************************************************************
This source lists all the morph targets that will be used by this controller.  In this
case there is just one, but there could be as many as you like.  Multiple targets are 
commonly used to apply facial expressions to characters.  There would a "happy" morph,
a "sad" one, an excited one...etc. Which could be mixed so you could make an expression
that was half sad, half excited...etc.
*******************************************************************************************
       <source id="pCylinderShape1-morph-targets">
         <IDREF_array id="pCylinderShape1-morph-targets-array" count="1">target__pCylinderShape1</IDREF_array>
         <technique_common>
           <accessor source="#pCylinderShape1-morph-targets-array" count="1" stride="1">
             <param name="MORPH_TARGET" type="IDREF"/>
           </accessor>
         </technique_common>
       </source>
*******************************************************************************************
This source contains the weights to be applied to each morph target (in this case just one)
A weight of 1 means the morph is fully applied.  This can be animated.
*******************************************************************************************
       <source id="pCylinderShape1-morph-morph_weights">
         <float_array id="pCylinderShape1-morph-morph_weights-array" count="1">1</float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-morph-morph_weights-array" count="1" stride="1">
             <param name="MORPH_WEIGHT" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <!--
*******************************************************************************************
The inputs in the targets tag point to the sources containing the list of morph targets and
the list of corrisponding weights.
*******************************************************************************************
        -->
       <targets>
         <input semantic="MORPH_TARGET" source="#pCylinderShape1-morph-targets"/>
         <input semantic="MORPH_WEIGHT" source="#pCylinderShape1-morph-morph_weights"/>
       </targets>
     </morph>
   </controller>
*******************************************************************************************
This controller defines how to skin the geometry that comes out of the morph controller.
*******************************************************************************************
   <controller id="pCylinderShape1-morph-skin" name="skinCluster1">
*******************************************************************************************
A regular skin controller would point at a geometry we wanted to skin.  In this case we are 
taking the output of a morph controller (which is geometry) and skinning that.
*******************************************************************************************
     <skin source="#pCylinderShape1">
       <!--
*******************************************************************************************
The bind shape matrix describes how to transform the pCylinderShape1-morph geometry into the
right coordinate system for use with the joints.  In this case we do an +90 Y transform because
the geometry was initially a 180 unit long cylinder with 0,0,0 at it's center.
This moves it so 0,0,0 is at the base of the cylinder.
*******************************************************************************************
        -->
       <bind_shape_matrix>
       </bind_shape_matrix>
       <!--
*******************************************************************************************
This source contains a list of the SIDs of the 7 joints that will influence the skin.  You
can also use an IDREF_Array here but use of SIDs is prefered because they allow a controller
to be used several times with different skeletons.  Applications MUST be able to import either
IDREF_Array or Name_array tags.  And MUST search the correct namespace for the ID or SID
*******************************************************************************************
        -->
       <source id="pCylinderShape1-morph-skin-joints">
         <Name_array id="pCylinderShape1-morph-skin-joints-array" count="7">
joint1 joint2 joint3 joint4 joint5 joint6 joint7</Name_array>
         <technique_common>
           <accessor source="#pCylinderShape1-morph-skin-joints-array" count="7" stride="1">
             <param name="JOINT" type="Name"/>
           </accessor>
         </technique_common>
       </source>
       <!--
*******************************************************************************************
This source defines the inverse bind matrix for each joint, these are used to bring 
coordinates being skinned into the same space as each joint.  Note that in this case the
joints begin at 0,0,0 and move up 30 units for each joint, so the inverse bind matrices
are the opposite of that.
*******************************************************************************************
        -->
       <source id="pCylinderShape1-morph-skin-bind_poses">
         <float_array id="pCylinderShape1-morph-skin-bind_poses-array" count="112">
         </float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-morph-skin-bind_poses-array" count="7" stride="16">
             <param name="TRANSFORM" type="float4x4"/>
           </accessor>
         </technique_common>
       </source>
       <!--
*******************************************************************************************
This source defines a weight for each vertex and each joint.  The weight defines how much
a particular joint will contribute to moving a particular vertex's position.  This allows
several joints to influence vertices by different amounts, giving a nice smooth bend.
Since there are 42 vertices and 7 joints there should be at most 294 weights.  In this case
the skinning algorithm was told that each vertex should be effected by the 5 nearest joints
so we have 5 weights per vertex giving a total of 210.  Maya has thrown in an extra weight
of 1 at the beginning giving us a total of 211.
Weights 1-6 will be applied to the first vertex, you can see how they work.  The first weight
represents the closest joint to the vertex and has the largest value, the remaining 4 weights
get smaller and smaller as the associated joint gets farther from the vertex.
*******************************************************************************************
        -->
       <source id="pCylinderShape1-morph-skin-weights">
         <float_array id="pCylinderShape1-morph-skin-weights-array" count="211">
0.010747 0.037398 0.161802 0.395025 0.395025 0.010747 0.037398 0.161802 0.395025 0.395025</float_array>
         <technique_common>
           <accessor source="#pCylinderShape1-morph-skin-weights-array" count="211" stride="1">
             <param name="WEIGHT" type="float"/>
           </accessor>
         </technique_common>
       </source>
       <!--
*******************************************************************************************
The joints tag connects the source containing the name of each joint with the source 
containing the inverse bind matrices for each joint.
*******************************************************************************************
        -->
       <joints>
         <input semantic="JOINT" source="#pCylinderShape1-morph-skin-joints"/>
         <input semantic="INV_BIND_MATRIX" source="#pCylinderShape1-morph-skin-bind_poses"/>
       </joints>
       <!--
*******************************************************************************************
The vertex_weights tag associates the weights and joints from the previously defined
sources with the vertices in the geometry being skinned.  Each entry in this list matches
a vertex in the original geometry, so the count here should be the same as the count
in the geometry being skinned.
Each weight/joint pair is referred to as an "influence", a vertex can have any number of
influences applied to it.  The <vcount> value for a vertex defines the number of influences 
on that vertex.  In this case every vertex has 5 influences.  The values in the <v> array
are the indices of the joint and weight that make up that influence.
*******************************************************************************************
      <vertex_weights count="42">
         <input semantic="JOINT" source="#pCylinderShape1-morph-skin-joints" offset="0"/>
         <input semantic="WEIGHT" source="#pCylinderShape1-morph-skin-weights" offset="1"/>
       </vertex_weights>
     </skin>
   </controller>
 </library_controllers>
 <library_visual_scenes>
   <visual_scene id="VisualSceneNode" name="untitled">
*******************************************************************************************
This is the node hierarchy that represents the skeleton of the skinned object.
The first node has an ID to act as a starting point for SID searches, the rest
of the nodes in the hierarchy only need SIDs.  It is preferable to use SIDs to
identify the joints of the skeleton because it allows the skin controller to be
used several times with different skeletons.  For example we could have a second
joint hierarchy using the same SIDs but with a different id (like skeleton2_root)
on the first node and different transforms.  
In this example the root joint of the skeleton is 20 units above the ground.  
All the other joints are 30 units apart in the Y direction.  A Z rotation has been
added to some of the joints to cause the skinned/morphed cylinder to gradually bend so
you can see the skinning effect.
*******************************************************************************************
      -->   
     <node id="skeleton_root" name="joint1" sid="joint1" type="JOINT">
       <translate sid="translate">0 20 0</translate>
       <!-- 
*******************************************************************************************
Some people try to put the instance_controller here.  This will not work correctly for
a skin because the skinning process has already transformed all the vertices using the
full transform in the joints that the skin controller references. This means the data
coming out of the instance_controller is effectively in world space.  If we put the 
instance_controller here, the geometry coming out of it would be transformed (again) by 
this node, moving it up an additional 20 units. 
*******************************************************************************************
        -->   
       <node name="joint2" sid="joint2" type="JOINT">
         <translate>0 30 0</translate>
         <node name="joint3" sid="joint3" type="JOINT">
           <translate>0 30 0</translate>
           <rotate>0 0 1 17.972</rotate>
           <node name="joint4" sid="joint4" type="JOINT">
             <translate>0 30 0</translate>
             <rotate>0 0 1 16.4036</rotate>
             <node name="joint5" sid="joint5" type="JOINT">
               <translate>0 30 0</translate>
               <rotate>0 0 1 21.1126</rotate>
               <node name="joint6" sid="joint6" type="JOINT">
                 <translate>0 30 0</translate>
                 <rotate>0 0 1 16.007</rotate>
                 <node name="joint7" sid="joint7" type="JOINT">
                   <translate>0 30 0</translate>
                 </node>
               </node>
             </node>
           </node>
         </node>
       </node>
     </node>
*******************************************************************************************
This node is where the skinned/morphed geometry is instantiated.  The geometry that comes out
of a skin controller has already been transformed by the joints referenced in the skin
which puts the geometry in world space.  This is why we are instantiating the skin at
the root of the hierarchy rather than up in the "skeleton_root" node
*******************************************************************************************
       --> 
    <node id="pCylinder1" name="pCylinder1" type="NODE">
       <instance_controller url="#pCylinderShape1-morph-skin">
         <!--
*******************************************************************************************
The skeleton tag tells the controller where it should start searching for any SIDs found
in the skin.  This allows the same controller to be re-used with different joint hierarchies.
If the controller uses an IDREF_Array then the skeleton tag is not required because IDs are 
*******************************************************************************************
          -->
         <skeleton>#skeleton_root</skeleton>
         <bind_material>
           <technique_common>
             <instance_material symbol="lambert2SG" target="#lambert1"/>
           </technique_common>
         </bind_material>
       </instance_controller>
     </node>
   </visual_scene>
 </library_visual_scenes>
   <instance_visual_scene url="#VisualSceneNode"/>
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

FilesExpand file tree

skin_and_morph.dae

Latest commit

History

skin_and_morph.dae

File metadata and controls
