Difference between revisions of "Descr engine skeleton.txt"
(link to adding sounds tut - and more info - needs sorting a bit here...) |
m (removed Category:RTW Modding; added Category:RTW Skins, Models & Animations using HotCat) |
||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | {{ | + | {{RTW M2TW Modding Logo}} |
==Overview== | ==Overview== | ||
| − | Unlike [[descr_skeleton.txt]] this file is | + | Unlike [[descr_skeleton.txt]] this file is used by the game even when packed animations are present. |
Format is : | Format is : | ||
| Line 11: | Line 11: | ||
engine_skeleton ballista | engine_skeleton ballista | ||
| − | + | ===Adding New Skeleton=== | |
You can add a new skeleton by copying whole section and changing the type name at the start eg: | You can add a new skeleton by copying whole section and changing the type name at the start eg: | ||
type newonager | type newonager | ||
do the same for the dying one as well. | do the same for the dying one as well. | ||
| − | This might not allow you to make a new animation - though you could possibly | + | This might not allow you to make a new animation - though you could possibly use the existing ones for different points in the engines fire cycle. You can also use it to add unique sounds for one particular unit using the new skeleton. |
| + | ===Relationship to Sounds Files=== | ||
The sounds the engine uses when firing are set in [[descr_sounds_units_anims.txt]] new events can be added to that file. The events are called by the .evt files referenced in this file. They are actually just text files with a silly file name! | The sounds the engine uses when firing are set in [[descr_sounds_units_anims.txt]] new events can be added to that file. The events are called by the .evt files referenced in this file. They are actually just text files with a silly file name! | ||
| Line 25: | Line 26: | ||
so if you make newballista_recovery.evt with contents | so if you make newballista_recovery.evt with contents | ||
event SOUND ANIM_NEWBALLISTAE_RECOVER 0 0 | event SOUND ANIM_NEWBALLISTAE_RECOVER 0 0 | ||
| − | it will read ANIM_NEWBALLISTAE_RECOVER entry in the sound file | + | it will read ANIM_NEWBALLISTAE_RECOVER entry in the sound file (assuming you have added one there!) |
| − | ( | ||
==See Also== | ==See Also== | ||
| − | *[ | + | *[[Sounds: Changing Animation Sounds for Engines]] |
| − | + | [[Category:RTW Skins, Models & Animations]] | |
| − | [[Category:RTW | ||
[[Category:M2TW Modding]] | [[Category:M2TW Modding]] | ||
[[Category:RTW Files]] | [[Category:RTW Files]] | ||
[[Category:M2TW Files]] | [[Category:M2TW Files]] | ||
Latest revision as of 11:39, 18 March 2021
Overview
Unlike descr_skeleton.txt this file is used by the game even when packed animations are present.
Format is :
type ballista anim idle data/animations/engine/ballista_idle.CAS -evt:data/animations/engine/ballista_idle.evt anim idle_to_moving data/data/animations/engine/ballista_idle2move.CAS -evt:data/animations/engine/ballista_idle2move.evt
etc.
the type - ballista in that example is the name that needs to be used in descr_engines.txt at:
engine_skeleton ballista
Adding New Skeleton
You can add a new skeleton by copying whole section and changing the type name at the start eg:
type newonager
do the same for the dying one as well.
This might not allow you to make a new animation - though you could possibly use the existing ones for different points in the engines fire cycle. You can also use it to add unique sounds for one particular unit using the new skeleton.
Relationship to Sounds Files
The sounds the engine uses when firing are set in descr_sounds_units_anims.txt new events can be added to that file. The events are called by the .evt files referenced in this file. They are actually just text files with a silly file name!
For instance ballista_recovery.evt just has some comments and:
event SOUND ANIM_BALLISTAE_RECOVER 0 0
so if you make newballista_recovery.evt with contents
event SOUND ANIM_NEWBALLISTAE_RECOVER 0 0
it will read ANIM_NEWBALLISTAE_RECOVER entry in the sound file (assuming you have added one there!)
