Thanks for the improved clarity on exactly what the issue is, how to reproduce, etc. 👍   I believe this boils down to several things:  As I explained in a previous thread, when you associate a ScrollTrigger with a timeline (rather than a tween), it must WAIT 1 tick to do its refresh (when it calculates start/end values and applies pinSpacing, etc.) because timelines are almost always created and THEN populated and it's super common to assign the ScrollTrigger in the constructor l
    • Like
    4