Jump to content

Search In
  • More options...
Find results that contain...
Find results in...

ZachSaucier last won the day on September 30

ZachSaucier had the most liked content!


  • Content Count

  • Joined

  • Last visited

  • Days Won


ZachSaucier last won the day on September 30

ZachSaucier had the most liked content!

Community Reputation

960 Leader


About ZachSaucier

  • Rank
    Advanced Member

Contact Methods

Profile Information

  • Gender
  • Location
  • Interests
    Frontend development, soccer, board games, theology

Recent Profile Visitors

2,878 profile views
  1. Hey Ben and welcome to the GreenSock forums. Another user recently posted about a similar topic, maybe looking at it can help:
  2. Hey @duty47, Would you mind posting the approach that you figured out? Another user is asking about a similar effect.
  3. Hello piker and welcome to the GreenSock forums. Maybe this article can help you:
  4. Hey Enzo, You can modify and add new values to the arrays as you'd like. Are you wondering how to more easily create these points? It might be easier to use an SVG path using our MorphSVG plugin instead. P.S. In the next version of GSAP this sort of thing will be even easier! We're working hard on getting it released ASAP.
  5. I recommend using a regular input element with type="range" for this. You don't even need GSAP, really https://codepen.io/GreenSock/pen/oNNxOxR?editors=0100 If you need more control over the styling (stying default input elements across browsers can require a lot of testing/workarounds) then you could create a dummy version using divs like you did and hide the input. But this approach avoids the issue you describe above. Edit: Looks like Blake beat me by half a second
  6. Hey evomedia and thanks for being a Shockingly Green member! It doesn't help us helping you if you always are updating the same CodePen that you posted in the first link. It would be good to save different version so that we can see your first attempt followed by any changes that you make. In general, I would structure my approach as such: Set up a tween to linearly scroll to the end of the page. Keep it paused. On the range slider's change event, calculate the percentage of the range in the 0-1 range and pass that value into your scroll tween's .progress(). On scroll, update the range slider's position but don't update the page's scroll position inside of the listener (that way you keep the page's default scroll behavior). That way you keep the range slider and page scroll behavior in agreement but independent.
  7. Hey bacondo and welcome to the GreenSock forums. ScrollMagic isn't a GreenSock product and we don't support it here so you may not get a response from other forum members. We really try to keep these forums focused on GSAP-specific questions. However, the ScrollMagic documentation has an example of how to do this, maybe that will help: https://scrollmagic.io/examples/advanced/anchor_link_scrolling.html It looks like the ScrollMagic author does offer paid support which you can learn about at https://support.scrollmagic.io/. If you have any GSAP-specific questions, we'd love to help. Good luck with your project!
  8. If you hang around the GreenSock forums and contribute for a while I bet your understanding of how GSAP works will also increase a good bit. We'd love to have you around contributing wherever you can
  9. This post may also interest you for a general description of why GSAP is fast:
  10. Hey chenxin and thanks for being a Shockingly Green member. What do you mean "learn animation"? If you mean how to create things like what Chris Gannon or other animators make, reading the source code of GSAP probably won't help very much. For learning how to create animations like that, creating demos and breaking down demos of other animators is probably the best way to learn. GSAP is just specialized JavaScript, so if you're having trouble understanding the source code it'd be good to get a more full understanding of JavaScript itself. There are online courses, articles, videos, and books that can help you there. But again, I find that creating demos and breaking down other peoples' is one of, if not the best, ways of learning. Ultimately it depends on what your end goals are - if you want to be a developer like Jack (@GreenSock) who spends most of his days working on the backend of an animation library like GSAP, then understanding the source code could really help. If you want to be more like Chris Gannon, understanding the source code probably won't help very much.
  11. You'll have to make a demo of your issue. It's impossible for us to help blind. Please create a CodePen or something that recreates the inconsistency that you're referencing. The below thread can help you so do:
  12. That's a good question. I'm not sure why that happens. Maybe another forum member like @GreenSock can help.
  13. Thanks for clarifying. I see what you mean. If you go into "Toggle Device Toolbar" mode and try to scroll the polygons in the vertical direction they don't move very far. However, on an actual mobile touch device I don't see the same behavior. Maybe it's an error with Chrome's dev tools?
  14. Hey kidaww and welcome to the GreenSock forums. I put your code into a CodePen and wasn't able to reproduce the error that you're speaking of. Evidently there's something else going on. https://codepen.io/GreenSock/pen/OJJyRWQ?editors=1000 Can you please create a minimal demo of your issue inside of a CodePen? You can for the pen above if you'd like.