io_export_ogreDotScene._ogredoc_Animation_System Class Reference

Inheritance diagram for io_export_ogreDotScene._ogredoc_Animation_System:

List of all members.

Static Public Attributes
string	mydoc

---

Detailed Description

Definition at line 2287 of file io_export_ogreDotScene.py.

---

Member Data Documentation

string io_export_ogreDotScene._ogredoc_Animation_System::mydoc [static]

Initial value:

'''
Armature Animation System | OgreDotSkeleton
Quick Start:
    1. select your armature and set a single keyframe on the object (loc,rot, or scl)
        . note, this step is just a hack for creating an action so you can then create an NLA track.
        . do not key in pose mode, unless you want to only export animation on the keyed bones.
    2. open the NLA, and convert the action into an NLA strip
    3. name the NLA strip(s)
    4. set the in and out frames for each strip ( the strip name becomes the Ogre track name )

How it Works:
    The NLA strips can be blank, they are only used to define Ogre track names, and in and out frame ranges.  You are free to animate the armature with constraints (no baking required), or you can used baked animation and motion capture.  Blending that is driven by the NLA is also supported, if you don't want blending, put space between each strip.

The OgreDotSkeleton (.skeleton) format supports multiple named tracks that can contain some or all of the bones of an armature.  This feature can be exploited by a game engine for segmenting and animation blending.  For example: lets say we want to animate the upper torso independently of the lower body while still using a single armature.  This can be done by hijacking the NLA of the armature.

Advanced NLA Hijacking (selected-bones-animation):
    . define an action and keyframe only the bones you want to 'group', ie. key all the upper torso bones
    . import the action into the NLA
    . name the strip (this becomes the track name in Ogre)
    . adjust the start and end frames of each strip
    ( you may use multiple NLA tracks, multiple strips per-track is ok, and strips may overlap in time )

'''

Definition at line 2288 of file io_export_ogreDotScene.py.

---

The documentation for this class was generated from the following file:

• io_export_ogreDotScene.py