Every other animation works, so that is unlikely.Maybe a stupid question, but can't it be just some settings?
Aha, that's good to know. I get the same results as you guys then; K-Mod doesn't make a difference.
Does the DLL support some form of manual log printing?
Well, yes ...
So, to whom it may concern, logging from the DLL:
But what to iterate over? There are animation paths in XML, but those don't reference a particular animation. I really don't understand how this stuff works once the EXE has determined the animation path and category.
What one could try is call PlayAnimation for all ids from 10 (the first 9 being assigned to resources and improvements) up to ... some number and see what the unit model does. For the ANIMCAT_AIRSTRIKE BaseID of 42, the SAM Infantry just freezes for a few seconds. If I try to play them in a loop
for (int i = 10; i < 50; i++)
gDLL->getEntityIFace()->PlayAnimation(pInterceptor->getEntity(), (AnimationTypes)i);Deprecated is programmer talk for:
I've tried playing a new animation at every 16th game update – that should be every 2 seconds. Still, up to id 100, there is no effect on the unit. I've tried 1042, which is the number shown on the Ctrl+U screen (which appears to be part of the EXE); also no effect. I'm not going to investigate the PlayAnimation function further in this manner. I don't think it has the right parameters to be intended for unit animations:
AnimationTypes eAnim, float fSpeed = 1.0f, bool bQueue = false,
int iLayer = 0, float fStartPct = 0.0f, float fEndPct = 1.0fThe 3.13 release notes do contain a few bullets about air units:
Doesn't really sound like it would require the code to be restructured; well, the stack combat thing perhaps. I would assume that Firaxis hadn't noticed that they broke the SAM Infantry. That really seems to be the only Vanilla/BtS unit with special anti-air animations.
Mobile SAM only has that one hurt animation; so I don't suppose that's an error?
This is more anecdotal observation. Code stuff is more like magic spells for me. But ranged units don't use the hurt animation during combat (rifleman). This is because they would have to switch to a melee/idle pose from a ranged pose. Bombardment does trigger it. Anyway, that was my line of thought. It has since occurred to me that is wrong. Mech units do use the hurta in combat. However, in this case the mobile sam should use the ranged attack animation for interception.
From what I can see, range units have a hurt animation and use them, but only in melee combat. For pure range units, like the rifleman and the mech units, the hurt animation is made for their ranged stance. The ancient and medieval range units change into a melee combat stance and have their hurt animation for that stance. If you have a combat where both units are pure range, no hurt animation will be triggered.
<KFM>
<Header>;Gamebryo KFM File Version 2.0.0.0b
</Header>
<NIF>JetFighter.nif</NIF>
<Master>MD</Master>
<Unknown></Unknown>
<Animations>
<Animation>
<Event>1000</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Idle.kf</File>
</Animation>
<Animation>
<Event>1020</Event>
<Variation>0</Variation>
<File>JetFighter_MD_FadeIn_Intercept.kf</File>
</Animation>
<Animation>
<Event>1010</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Run.kf</File>
</Animation>
<Animation>
<Event>1500</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Plane_Texture_DamTexture1.kf</File>
</Animation>
<Animation>
<Event>2500</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Plane_Texture_DamTexture2.kf</File>
</Animation>
<Animation>
<Event>3500</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Plane_Texture_DamTexture3.kf</File>
</Animation>
<Animation>
<Event>4500</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Plane_Texture_DamTexture4.kf</File>
</Animation>
<Animation>
<Event>1022</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Intercept.kf</File>
</Animation>
<Animation>
<Event>1023</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Hurt.kf</File>
</Animation>
<Animation>
<Event>1024</Event>
<Variation>0</Variation>
<File>JetFighter_MD_RunDie.kf</File>
</Animation>
<Animation>
<Event>1510</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Smoke_DamSmoke1.kf</File>
</Animation>
<Animation>
<Event>2510</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Smoke_DamSmoke2.kf</File>
</Animation>
<Animation>
<Event>3510</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Smoke_DamSmoke3.kf</File>
</Animation>
<Animation>
<Event>4510</Event>
<Variation>0</Variation>
<File>JetFighter_MD_Damage_Smoke_DamSmoke4.kf</File>
</Animation>
</Animations>
</KFM>That would follow... Except you see the intercept uses the melee attack. It is the bomb that is the ranged attack. It seems the "Fadein" intercept is the "fortify" (or the equivalent for planes).
