While digging into this, I've noticed a couple of clear issues.
First, most of the time, the asterisk is on T=0 which I understand is the trigger. I remember we used to say to keep the program checking, you put something impossible in the To cancel text box. I do that. DoNotCancel.
But I only see the asterisk on an image later than T=0 occasionally. So it seems to me that the program decides at Trigger that the capture is static, so it just stops checking.
I have captures that at T=0 it finds two objects that are static, but later images show the moving object with high confidence and marks all of them as static.
Second, if there is a moving object that is under the desired confidence, it will identify the higher confidence object. (My car in my driveway, typically)
Again, I do see some that fix on later images, but not frequently.
I wonder if there is an issue with the code under the Motion Required list box.