Couldn't view your track, but those lights seem very, very dim. Double check your AoA brightness knob. It's in the bottom most row of the UFC/HUD stuff, just above the AMPCD.
User preference of course, but: I take mine down to half brightness at night, and only adjust lower if needed to not blow out while using NVGs. Otherwise full brightness during most day operations.
I'd avoid using the LITENING, as our ATFLIR should be the better modelled pod in just about every metric and avionics integration since it has come out that we have a Spanish LITENING pod that pre-dates MSI. The one thing we lose out on is not having an IR laser pointer, due to ED modelling a pre-preduction ATFLIR that has neither the NAVFLIR (early pods should) or the IR marker.
You have a couple of options with the ATFLIR. You can SCS long towards the FLIR page to go straight from INR to AUTO (the moving target track) with out having to step INR>SCENE>AUTO, or you can go from SCENE to AUTO more smoothly than the LITENING because you can still slew in SCENE mode, requiring just one command of SCS towards the FLIR page.
If you decide to use the SCS long HOTAS shortcut you can move your LOS along with the target while it cues to track it, or you could move to AUTO ahead of the target and let it run into the cue, where the pod will then pick it up and track it.
Not a bug, as the Cage/Uncage button should invoke another function in the ATFLIR that we are unlikely to get. Being vague on purpose, sorry. But yep, gotta hit the LST button on the DDI.
Coyle's post in Red AoA doughnut - Today's dumb question was marked as the answer