k1ngy.eth Posted November 24, 2022 Share Posted November 24, 2022 How can I get these animations to start at the same time? const tl1 = gsap.timeline({ scrollTrigger: { trigger: '.sky-container', end: '+=' + window.innerHeight / 3, scrub: 0.5, pin: true } }); const tl2 = gsap.timeline({ scrollTrigger: { trigger: '.sky-container', end: '+=' + window.innerHeight / 3, scrub: 0.5 } }); tl1.to(year1, { opacity: 1, transform: 'translateX(0)' }) .to(year2, { opacity: 1, transform: 'translateX(0)' }) .to(year3, { opacity: 1, transform: 'translateX(0)' }) .to(year4, { opacity: 1, transform: 'translateX(0)' }) .to(year5, { opacity: 1, transform: 'translateX(0)' }) .to(year6, { opacity: 1, transform: 'translateX(0)' }); tl2.to(circle1, { opacity: 1, height: 40, width: 40, top: 0, left: 0, ease: 'none' }) .to(line1, { opacity: 1, width: '130' }) .to(circle2, { opacity: 1, height: 40, width: 40, top: 0, left: 0, delay: -0.3 }) Link to comment Share on other sites More sharing options...
GSAP Helper Posted November 24, 2022 Share Posted November 24, 2022 It's pretty tough to troubleshoot without a minimal demo - the issue could be caused by CSS, markup, a third party library, your browser, an external script that's totally unrelated to GSAP, etc. Would you please provide a very simple CodePen or CodeSandbox that demonstrates the issue? Please don't include your whole project. Just some colored <div> elements and the GSAP code is best (avoid frameworks if possible). See if you can recreate the issue with as few dependancies as possible. If not, incrementally add code bit by bit until it breaks. Usually people solve their own issues during this process! If not, then at least we have a reduced test case which greatly increases your chances of getting a relevant answer. Here's a starter CodePen that loads all the plugins. Just click "fork" at the bottom right and make your minimal demo: See the Pen aYYOdN by GreenSock (@GreenSock) on CodePen Once we see an isolated demo, we'll do our best to jump in and help with your GSAP-specific questions. Link to comment Share on other sites More sharing options...
GreenSock Posted November 25, 2022 Share Posted November 25, 2022 Do you mind me asking why you don't just combine them into one timeline? That'd be simpler and cleaner. You neglected to define a start for either ScrollTrigger, so it's using the defaults. The standard default is "top bottom" EXCEPT if it has a pin defined in which case it defaults to "top top" because it'd be pretty silly to pin something when the top hits the bottom of the viewport. So just define the start on both so they match. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now