|
@@ -12,7 +12,7 @@
|
|
|
|
|
|
<h2>Overview</h2>
|
|
<h2>Overview</h2>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
Within the three.js animation system you can animate various properties of your models:
|
|
Within the three.js animation system you can animate various properties of your models:
|
|
the bones of a [page:SkinnedMesh skinned and rigged model],
|
|
the bones of a [page:SkinnedMesh skinned and rigged model],
|
|
[page:Geometry.morphTargets morph targets], different material properties (colors,
|
|
[page:Geometry.morphTargets morph targets], different material properties (colors,
|
|
@@ -28,11 +28,11 @@
|
|
Unity/Unreal Engine 4. This page gives a short overview of the main components of the
|
|
Unity/Unreal Engine 4. This page gives a short overview of the main components of the
|
|
system and how they work together.
|
|
system and how they work together.
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Animation Clips</h3>
|
|
<h3>Animation Clips</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
|
|
|
|
If you have successfully imported an animated 3D object (it doesn't matter if it has
|
|
If you have successfully imported an animated 3D object (it doesn't matter if it has
|
|
bones or morph targets or both) - for example exporting it from Blender with the
|
|
bones or morph targets or both) - for example exporting it from Blender with the
|
|
@@ -45,11 +45,11 @@
|
|
mesh is a character, for example, there may be one AnimationClip for a walkcycle, a second
|
|
mesh is a character, for example, there may be one AnimationClip for a walkcycle, a second
|
|
for a jump, a third for sidestepping and so on.
|
|
for a jump, a third for sidestepping and so on.
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Keyframe Tracks</h3>
|
|
<h3>Keyframe Tracks</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
|
|
|
|
Inside of such an *AnimationClip* the data for each animated property are stored in a
|
|
Inside of such an *AnimationClip* the data for each animated property are stored in a
|
|
separate [page:KeyframeTrack]. Assumed a character object has a [page:Skeleton skeleton],
|
|
separate [page:KeyframeTrack]. Assumed a character object has a [page:Skeleton skeleton],
|
|
@@ -63,22 +63,22 @@
|
|
information as to how the [page:Mesh.morphTargetInfluences influence] of a certain morph
|
|
information as to how the [page:Mesh.morphTargetInfluences influence] of a certain morph
|
|
target changes during the performance of the clip.
|
|
target changes during the performance of the clip.
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Animation Mixer</h3>
|
|
<h3>Animation Mixer</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
|
|
|
|
The stored data form only the basis for the animations - actual playback is controlled by
|
|
The stored data form only the basis for the animations - actual playback is controlled by
|
|
the [page:AnimationMixer]. You can imagine this not only as a player for animations, but
|
|
the [page:AnimationMixer]. You can imagine this not only as a player for animations, but
|
|
as a simulation of a hardware like a real mixer console, which can control several animations
|
|
as a simulation of a hardware like a real mixer console, which can control several animations
|
|
simultaneously, blending and merging them.
|
|
simultaneously, blending and merging them.
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Animation Actions</h3>
|
|
<h3>Animation Actions</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
|
|
|
|
The *AnimationMixer* itself has only very few (general) properties and methods, because it
|
|
The *AnimationMixer* itself has only very few (general) properties and methods, because it
|
|
can be controlled by the [page:AnimationAction AnimationActions]. By configuring an
|
|
can be controlled by the [page:AnimationAction AnimationActions]. By configuring an
|
|
@@ -87,24 +87,24 @@
|
|
shall be performed with a fade or a time scaling, and some additional things, such crossfading
|
|
shall be performed with a fade or a time scaling, and some additional things, such crossfading
|
|
or synchronizing.
|
|
or synchronizing.
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Animation Object Groups</h3>
|
|
<h3>Animation Object Groups</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
|
|
|
|
If you want a group of objects to receive a shared animation state, you can use an
|
|
If you want a group of objects to receive a shared animation state, you can use an
|
|
[page:AnimationObjectGroup].
|
|
[page:AnimationObjectGroup].
|
|
|
|
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h3>Supported Formats and Loaders</h3>
|
|
<h3>Supported Formats and Loaders</h3>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
Note that not all model formats include animation (OBJ notably does not), and that only some
|
|
Note that not all model formats include animation (OBJ notably does not), and that only some
|
|
three.js loaders support [page:AnimationClip AnimationClip] sequences. Several that <i>do</i>
|
|
three.js loaders support [page:AnimationClip AnimationClip] sequences. Several that <i>do</i>
|
|
support this animation type:
|
|
support this animation type:
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<ul>
|
|
<ul>
|
|
<li>[page:JSONLoader THREE.JSONLoader]</li>
|
|
<li>[page:JSONLoader THREE.JSONLoader]</li>
|
|
@@ -117,10 +117,10 @@
|
|
<li>THREE.SEA3DLoader</li>
|
|
<li>THREE.SEA3DLoader</li>
|
|
</ul>
|
|
</ul>
|
|
|
|
|
|
- <div class="desc">
|
|
|
|
|
|
+ <p class="desc">
|
|
Note that 3ds max and Maya currently can't export multiple animations (meaning animations which are not
|
|
Note that 3ds max and Maya currently can't export multiple animations (meaning animations which are not
|
|
on the same timeline) directly to a single file.
|
|
on the same timeline) directly to a single file.
|
|
- </div>
|
|
|
|
|
|
+ </p>
|
|
|
|
|
|
<h2>Example</h2>
|
|
<h2>Example</h2>
|
|
|
|
|