Yeah, exactly. This is more of an issue with LocomotiveScroll and its [apparent?] inability to immediately scroll to a specific place with no smoothing at all. It creates a race condition where ScrollTrigger is trying to do a normal scroll and LocomotiveScroll is intercepting it and being like "no way, buddy, I'm slowing this down and starting over...".    This is why we don't support 3rd party libraries and also why we intentionally designed ScrollTrigger not to do scroll-jacking.
    • Like
    4