Units animations

I''ll try to answer some things at least.

Q1.
The .acl (Animation Cycles Library) Files are responsible for the transitions between animations along with some code, but theoretically you won''t need to change the code, everything should already be there. This file ties different animations together, the speed at which they are executed, etc...

ACL.LIB tells you which .acl is used for which unit. In case of the round shier, it is infantry.acl

These acl files are hard to read, they are long and it can be hard to keep the overview. I suggest you look at them at least once in the acl editor for a better understanding.
https://i.imgur.com/95QsMNB.png


You can find the acl editor in the external editor (Module->Animation Library). Select a unit (Roundshier), then hit the edit button.
Alternatively you can you use the standalone version I uploaded to my site: http://cossacksworld.ucoz.co.uk/load/c_iii_files/mod_map_tools/c3_acl_editor/82-1-0-470
It does just the same, you''ll have to select 'all files' first on loading, (it looks for a .library file instead of .lib ( acl.lib)), then you can edit.

Code:

Example:
   [*] : struct.begin
      Name = attack1
      From = idle
      CyclesList = False
      Options : struct.begin
         acoSmoothAnimation = True
         acoRandomFrame = False
         acoRandomCycle = False
         acoSkipActions = False
      struct.end
      items : struct.begin
         [*] : struct.begin
            Action = actAnimation
            AnimationName = prepare1
            NumberCycle = 1
         struct.end
         [*] : struct.begin
            Action = actTrackPoint
            TrackPointMoveStep = 0
            TrackPointTurnStep = 11.125
            TrackPointIdleName = idle1
            TrackPointMode = mmNone
            TrackPointPreset =
         struct.end
      struct.end
   struct.end

This tells you that between the 'attack' animation and the 'idle' animation (notice the 'from' in the second line), the transition that is being used is the 'prepare1' animation, whichever those frames are , as defined in the .aaf file and this cycle of frames is being ran one time and at which speed.
I find this a bit a weird way of doing things, but here it is. There are many unused options in this setup, but that's a different story.


Q2.
Actor files do more than just loading animations for the actor. They also hold the properties/options that are being applied to the .osm and .oss files. That can go from shaders being used over rotation to renderdistance etc...
Look into data/actors/ref files to see all the options that are being loaded by default, for example refobj.actor shows quite a few options.

No need normally to change actors.lib unless you add ('new') units. New as in, proper new graphics. It just tells the game which .actor files to load on startup.

Reference files:
Probably the most important files, or at least it's important that you understand how they work, or what they do.
REF (reference) files are not unique to objects, you can find them for other files as well (.actor, materials, animations,...). These are used to list all the 'default' options and settings used for .actor, .prop, etc files. Rather than bloating a file with all the possible options, making it hard to read, a single line referring to this file will load all these options. (ie: {refurl=.\data\objects\ref\refunit.prop; refkey=mainproperty} ) . Overwriting any of these options is simply done by redefining the option in the used file.
In many cases, settings/options are the same for most units/buildings/trees, etc..., so instead of repeating these options all the time in each .actor file etc, they are just being put in one file, and referred to in the needed file by one line.
It's important that you understand , even though you don't see these options in the .actor, .prop file, they are loaded for these units/buildings if the referral url line is there.

Ref unit.acl:
In case of the refunit.acl file, I don't really see the refurl to this file being used at all, which just makes this a 'sample' file.

Ref unit actor:
If you look at the file, knowing what i just told you, every .actor file which refers to this file will load the defined options , in this case, specific shaders for units, how to handle the animations (morphing,looping,...) AND, all the options from refobj.actor, because that file is being referred to as well. Refunit.actor overwrites some options specified in refobj.actor. Normally you won't have to make changes to this file.

Q3.
Not of the top of my head but it depends what you are doing ofcourse.

Don't know if this helped at all.

 

Np,

I forgot to say, there's actually a line in the .prop files which refers to the acl files as well. It would entirely depend on what you do of course, like are you cloning, making a new unit, etc... but it's there, possibly in the .refunitprop files

Code:

frameanimationproperty : section.begin {refurl=.\data\objects\ref\refunit.prop; refkey=frameanimationproperty}
   FrameAnimationCyclesLibName = base.inf.knight.1
section.end

The lib name being the one being used in the acl files. It's just to the game can tie the .prop and .acl file together so it knows which animations cycles to load for the unit. Again with refurl's as well.


It's possible there are more things related to this, which may or may not be important. I'll keep it in mind if I think of it, ill post, meanwhile others can post relevant information if they have it.



Good luck with all of this, I find it impressive you are trying this out, not many get that far or have the courage to do so. Don't give up now. You are very close to having your own units in game. Keep us up to date.