Difference between revisions of "Animation format"
Imathrowback (Talk | contribs) |
Imathrowback (Talk | contribs) m |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
imp.nif | imp.nif | ||
| − | Character models (eg, the player) are slightly different. They have a base "empty" model, eg: | + | Character models (eg, the player) are slightly different. They have a base "empty" model based on the gender and race, eg: |
human_female_refbare.nif | human_female_refbare.nif | ||
| − | + | Armor pieces are then "grafted" onto it using reference points within the NIF. For example, a shoulder piece: | |
dwarf_male_vanity_shoulder_405B.nif | dwarf_male_vanity_shoulder_405B.nif | ||
| Line 30: | Line 30: | ||
pauldron_r_JNT | pauldron_r_JNT | ||
| − | These reference points also exist within ```human_female_refbare.nif``` and so can be grafted onto the correct bone | + | These reference points also exist within ```human_female_refbare.nif``` and so can be grafted onto the correct bone. |
===KFM=== | ===KFM=== | ||
| Line 43: | Line 43: | ||
A KFB file is a NIF file containing the actual animation data. These files contain a series of data, each made up of 4 NIF blocks. | A KFB file is a NIF file containing the actual animation data. These files contain a series of data, each made up of 4 NIF blocks. | ||
A KFB file uses a slightly different naming convention than the KFM. | A KFB file uses a slightly different naming convention than the KFM. | ||
| − | In general if the NPC can wield different weapons, then the KFB file name changes depending on the type of weapon equipped. | + | In general if the NPC can wield different weapons, then the KFB file name changes depending on the type of weapon equipped, otherwise it simply uses the basename: |
| + | |||
| + | imp.kfb | ||
| + | |||
| + | For models that can wield weapons, the actual strings can be gathered from dataset 230 such as: | ||
2h_staff | 2h_staff | ||
1h_ranged | 1h_ranged | ||
dual | dual | ||
| + | mount | ||
etc. | etc. | ||
| Line 55: | Line 60: | ||
human_female_dual.kfb | human_female_dual.kfb | ||
human_female_2h_staff.kfb | human_female_2h_staff.kfb | ||
| + | human_female_mount.kfb | ||
| Line 83: | Line 89: | ||
The stored NIF data file within the KFB contains a list of NiSequenceData and NiBSplineCompTransformEvaluator that define how the bones should be transformed for each frame by evaluating a spline function. | The stored NIF data file within the KFB contains a list of NiSequenceData and NiBSplineCompTransformEvaluator that define how the bones should be transformed for each frame by evaluating a spline function. | ||
| − | See [https://github.com/imathrowback/telarafly/blob/ | + | See [https://github.com/imathrowback/telarafly/blob/6a0fd0bd25448e75ee19f486baa24fe1e5f96970/Assets/AnimatedNif.cs#L199]. |
Latest revision as of 14:57, 5 June 2018
Contents
Animation data
Animation within a Gamebryo NIF is achieved using a combination of different techniques.
Texture animation/scrolling
Part of a NIF file. Uses a NiFloatsExtraData flag to specify UV texture co-ords to scroll. See NIFLoader.cs source.
Character models
NIF
Most models in use a bone system to link the mesh (skin) with the bones, then the bones can be transformed. Model references are stored in telara.db in dataset 7305.
An example model might be
imp.nif
Character models (eg, the player) are slightly different. They have a base "empty" model based on the gender and race, eg:
human_female_refbare.nif
Armor pieces are then "grafted" onto it using reference points within the NIF. For example, a shoulder piece:
dwarf_male_vanity_shoulder_405B.nif
Contains two nodes:
pauldron_l_JNT pauldron_r_JNT
These reference points also exist within ```human_female_refbare.nif``` and so can be grafted onto the correct bone.
KFM
The animations for the model utilize a KFM (Keyframe) file. A KFM file contains a list of animations sequence ids and names. The names are not used in RIFT, instead the 'ID' is used to link to a KFB file.
A KFM file uses the same naming convention as the NIF and is usually specified within the NIF entry in telara.db:
imp.kfm
KFB
A KFB file is a NIF file containing the actual animation data. These files contain a series of data, each made up of 4 NIF blocks. A KFB file uses a slightly different naming convention than the KFM. In general if the NPC can wield different weapons, then the KFB file name changes depending on the type of weapon equipped, otherwise it simply uses the basename:
imp.kfb
For models that can wield weapons, the actual strings can be gathered from dataset 230 such as:
2h_staff 1h_ranged dual mount etc.
These are then formatted with the name to give a valid KFB file:
human_female_dual.kfb human_female_2h_staff.kfb human_female_mount.kfb
Each sequence in the KFB is made up of:
| NIF Type | Purpose |
|---|---|
| NiIntegerExtraData | Contains the ID to link to the sequence within the KFM |
| NiIntegerExtraData | Size of the uncompressed binary data of the next block |
| NiBinaryExtraData | Compressed(ZLIB) NIF file stored as binary data. |
| NiBinaryExtraData | Unknown additional data. Appears to contain references to animation triggers like sounds. |
Applying to the model
The stored NIF data file within the KFB contains a list of NiSequenceData and NiBSplineCompTransformEvaluator that define how the bones should be transformed for each frame by evaluating a spline function.
See [1].
