Animation is really outside of my wheel house, but everyone in Ack Ack Attack! still has to run around with a gun in hand, so this one is all about how they got moving. Nearly all of it is Mixamo animations on Synty characters, with a Synty animation pack and a pose of my own added later on. It turned into another long one, so it's in two parts again. This part is the player and the enemies, from the Unreal version through to the Godot one holding its guns properly. Part two is the floating, a word that keeps turning up in both engines and both games, and that most of the time turned out to mean something else!
It started in Unreal in August 2024, when the animations went in for the player and the alien. I used the in-place versions, so the animation runs on the spot and the code does the actual moving (still how it works in both games today). Then came Unreal's retarget assets, a walk to run blend space and the gun. For that I put a static mesh on a socket on the right hand rather than adding it to the rig, because, as my check-in from the time says, "I don't need an animated weapon". The enemies were still floating above the floor at Milestone 1, and that was gone by Milestone 2, but floating wasn't done with me yet!
Fast forward to May 4th this year and the first import into Godot. The log was happily printing "Playing: Run Forward" over and over while my soldier stood there in a T-pose, not moving a muscle. Claude Code found two things wrong. The code was grabbing the first clip in each Mixamo file, which is Take_001 (the T-pose bind clip) instead of the one called mixamo_com, and the soldier's own FBX came in with no working skin weights, so nothing was going to bend him anyway. The character inside Rifle Idle.fbx was skinned just fine, so that became the player, and 23 minutes after that screenshot the check-in reads "Player is in / Animations are in / Blending of animations is in", with "Animation looping fixed" six minutes after that. There was one more early gotcha. Turning the body to aim also turned its collision box, which then caught on the walls, so now only the visible model turns and the body underneath never does. He still runs on those same five Mixamo clips today, Rifle Idle and Run Forward, Backward, Left and Right, in a 2D blend space that picks between them from which way he's moving compared to where he's facing.
The enemies got moving on June 16th, all sharing a Mixamo run and idle. The war robot started out borrowing the soldiers' run through a retarget at runtime, which had him leaning over far too much, so later that day he got his own Mixamo War-Robot clips instead. The guns went in at the same time. Everyone holds the same shotgun, because the rifle and pistol were "too thin to read top-down", and after a go at attaching it in code and then as a node placed by hand in the editor, on the 18th it moved onto the right hand bone for everyone, with a bit of code that aims the hand and reaches the left hand forward to the grip. The gun is stretched out along the barrel so it reads from way up top, and the first stretch of 1.62 "read too long", so it's 1.15 now.
The left hand took a few goes. First an elbow that flipped over as you turned to aim, then fingers left wide open, so Claude had them curl round the grip in code. Then in August a probe found that the Synty glove fingers are basically rigid mitts, and a curl of 3 radians did nothing at all! So the curls in game probably don't do a lot either.
When the enemy AI got rebuilt in July (there's more on that in From Unreal to the App Store, Part Two), the same change had them patrolling at a walk, and the walk and run for that came from the Synty Base Locomotion pack. That pack is on Synty's newer rig, with different bone names to the classic one my characters are on, and rest poses so far apart (117 to 174 degrees per bone, by Claude's measuring) that just renaming the tracks was never going to work. On top of that the pack rig rests in an A-pose and mine in a T-pose, and without a correction that difference leaks into every frame as raised arms. So Claude wrote an offline baker that runs headless and goes through every frame and every bone, takes the pack bone's rotation away from its own rest, corrects for the A-pose against T-pose difference and puts the result onto my rig's rest. Out of the 692 clips in the pack it baked three, a walk, a run and an idle. The enemies blend from the Mixamo rifle idle into the new walk and run off the speed they actually moved, so one that's stuck against a wall idles instead of running on the spot, and because the pack's cycles are unarmed (arms swinging away while holding a shotgun looked broken) their arms are locked to that rifle idle while the legs do the walking.
For the soldier's arms I posed the weapon hold myself in Maya. The first export didn't come through at all (the gun landed in its new spot and the arms stayed home), and if you ever do this the fix is worth knowing, the joints have to be keyed at frame 0 and the FBX exported with Animation and Bake Animation both ticked. On August 16th it went in, with the arms, hands and fingers locked to my pose over the top of the running clips and the gun sitting on the hand at the grip I posed, in game and on the menu soldier. That same night threw up a couple more. The run looked hunched, and three rounds of fixing it in a row only made it worse, because the lean correction was pitching the wrong way and the camera looking nearly straight down hid it. Looking at him side on finally showed what was going on, and the lesson that went into the notes is a good one, "Judge posture from a PROFILE view, never the game camera". The other was my posed muzzle sitting right on the top edge of the enemies' hit boxes, so shots were going straight through them, and now the bolts leave at a fixed height instead.
Two days later first person went in, with my Maya arms and the shotgun as the view and the legs held at idle while you run, because the run's lean was dragging the gun down and out of the frame. In September I noticed "the thumb is off the weapon" in first person, so that got a little nudge back onto the foregrip too. That's part one! Part two is the floating: a boss that glided, crew that ran a touch too fast, and over on Pyrate Plunder Island a cast stuck in a T-pose and a town of NPCs sliding about. Keep an eye on the dev log!