You’ll notice that the propertyGroup counts are not intuitive if you try to count up by eyeballing the levels of properties you see in the timeline, because there are some hidden levels: An Animator has a hidden propertyGroup of “Selectors” and a hidden PropertyGroup of “Properties”, and also the animators themselves are inside a propertyGroup “Animators”, all these levels are not represented by a twirly > in the timelines structures.
So, counting up from a property Position to the Pool of animators it is a child of takes 3 steps:
I tried it, and for me this does the characters one by one like a square selector instead of with an overlapping delay.
The only way I can get a delay in an expression selector to work with custom keyframes/timings is to have the actual keyframes somewhere else (in another deactivated animator, or in a point control, on a Null…), because once a property is already keyframed down to 0, no amount between -100 and 100 is going to change it to be anything else.
My approach with Position expressions Selectors is to give the property a fixed value of 10,000;10,000 and then use the amount expression to use percentages to turn those into pixel positions. (It’s unfortunate that all selectors are limited form -100% to 100%)
I’d love to hear your thoughts on this technique, maybe there’s another approach with expression selectors?