Jump to content
GreenSock

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

Leaderboard

  1. ZachSaucier

    ZachSaucier

    Administrators


    • Points

      11

    • Content Count

      1,523


  2. GreenSock

    GreenSock

    Administrators


    • Points

      5

    • Content Count

      13,861


  3. Jonathan

    Jonathan

    Moderators


    • Points

      2

    • Content Count

      3,545


  4. green_machine

    green_machine

    ShockinglyGreen


    • Points

      2

    • Content Count

      44



Popular Content

Showing content with the highest reputation on 01/20/2020 in all areas

  1. 2 points
    Ah, I gotcha. I misread then; I thought in 3.0 that you meant that you could now use "rotate" across the board in GSAP, which I prefer since it matches CSS now and not AS (and it's also fewer characters). If it means you had to add logic now to convert "rotate" to "rotation" everywhere behind the scenes then no need, I can just go back to using "rotation" instead and keep the library leaner.
  2. 2 points
    Hey MustketeerHo. This is caused by the image not being perfectly symmetrical, not anything related to GSAP. There's no way to get rid of it other than to get a different (symmetrical) image.
  3. 2 points
    @PaulB yes, I definitely want to see a reduced test case if at all possible because GSAP 3 should not be noticeably slower than GSAP 2 and I'm very curious to see your use case. Do you have a reduced test case that shows v2 and the same thing with v3 that we can compare? I wonder if the perceived difference actually has nothing to do with GSAP but only a change in the way certain browsers render things. I remember a while back Chrome suddenly changed how it rendered 3D transforms (at least on the Mac) and it made a HUGE performance difference but nothing changed in GSAP.
  4. 2 points
    If you're loading it via a script tag or in something that requires UMD files (like Vue.js), yes. If you're using a different build tool that requires modules (like React, etc.) then you would use the modules version instead. Our Installation page has more details.
  5. 1 point
    Yes, I'm certain. You can tell from the text in your pen. Here's a minimal demo that shows it very clearly: https://codepen.io/GreenSock/pen/povQKxR?editors=0100
  6. 1 point
    Do you have specific Browser versions of the browsers you listed? But that will help along with a limited reduced Codepen demo example like Jack advised above.
  7. 1 point
    Welcome to the forum @PaulB It would be helpful if you could provide a simple example instance of your claims via a codepen. This would allow staff to evaluate these claims and assist in providing you some helpful feedback. If issues exist as you've stated then I’m sure @GreenSock would like to see an example so he can address things.
  8. 1 point
    Hey ninmorfeo, This is exactly what .getProperty() is for. We don't recommend mixing jQuery's .css() with GSAP as it's really not ever necessary to do.
  9. 1 point
    Hey Ben and welcome to the GreenSock forums! Using timeScale to make a timeline responsive is an... interesting approach we generally recommend killing off the previous tweens/timelines and creating new ones on resize if the need be. Alternatively using responsive units or something like intersection observers make it so you don't have to do that a lot of the time. It seems like this.scrollTimeline.time(window.pageYOffset); would be passing in numbers that are much larger than the duration of the timeline if the page is very tall. I might check to make sure that value is within the time of the scrollTimeline. Besides that, it's really hard to say what's going wrong. Sorry, but it'd be very helpful for us to see a minimal demo. P.S. Why not use GSAP 3? It's smaller, has a lot of new features, and has an improved API. If you do switch over to GSAP 3, use the beta file for now because version 3.0.5 has a regression related to timeScale.
  10. 1 point
    I think Zach already answered that above - you must have a license for anyone who writes or edits any GSAP-related code in your theme/app/site. Yes, if the developer that has the license creates something for another company that sells it but NOBODY (besides the license-holder) makes any edits or codes anything that's GSAP-related, that's fine. It's not a license that can be passed around though. I think you'll find that the license pays for itself quickly, even if you need to get a multi-developer license. Happy tweening!
  11. 1 point
    Sorry about that, @mikel - there was a regression in 3.0.5 that caused tweening of timeScale() on another animation not to always work as expected. That should be resolved in the next release which you can preview at https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/gsap-latest-beta.min.js - is that better?
  12. 1 point
    Yeah, that's because the official GSAP property is "rotation", but when you directly animate things via CSSPlugin it'll accept some aliases too like "rotate" (which internally we just map to "rotation"). MotionPathPlugin wasn't able to do that mapping. I'll update the next version of MotionPathPlugin to look for those aliases too - here's a preview: https://s3-us-west-2.amazonaws.com/s.cdpn.io/16327/MotionPathPlugin.min.js Better? By the way, thanks so much for the reduced test case! Super helpful.
  13. 1 point
    Perhaps GSAP 3.x documentation is yet not perfect, but gsap forum is. Thanks again Zach, that's exactly what i was looking for. You saved me a lot of time. I will accept your syntax and advice.
  14. 1 point
    Hey AslanGoi, In terms of how to count developers for the different levels of the Business Green membership, it’s based on the number of people who would actually use GreenSock tools. So if 7 of the employees at the company would never touch GSAP code or anything that's directly related, they don't have to be included in the count. However it’s not intended to be a license that gets passed around from person-to-person, like “Hey Sally, can you stop using GreenSock for 5 minutes so I can update something?” If a company has 3 developers who use GreenSock from time to time, they should get the “Up to 5 developers” license. You can always upgrade later too. Also note that the commercial license that comes with Business Green must be kept active for the duration of the time which you are selling the product that is using GreenSock technology. So if you stop developing with GSAP this year but still sell the product in future years, you'd need to keep that license active (renew it yearly or just get the permanent license). Let us know if you have any questions!
  15. 1 point
    Hey MusketeerHo and welcome. The main issue is that you didn't load InertiaPlugin (previously known as ThrowPropsPlugin). Adding that and changes endValue to the correct value in your callback fixes your issues https://codepen.io/GreenSock/pen/rNaqoeN?editors=0010 Keep in mind that using InertiaPlugin on your site requires at least a Shockingly Green Club GreenSock membership. We'd love to have you join the club!
  16. 1 point
    The bug fix for this has already been released in GSAP 3.0.5. But GSAP 3.1.0 is planned to be released early next week.
  17. 1 point
    Hi @monixm and Welcome to the GreenSock Forum! Just some additional info we need to better help you: What browser and browser version are you seeing this on? What OS and OS version are you seeing this on? Some things you could do is to maybe add a slight rotation: 0.01 to your tween, and or also using autoAlpha instead of opacity for better performance. autoAlpha is part of the CSSPlugin: https://greensock.com/docs/v3/GSAP/CorePlugins/CSSPlugin#autoAlpha autoAlpha Identical to opacity except that when the value hits 0 the visibility property will be set to hidden in order to improve browser rendering performance and prevent clicks/interactivity on the target. When the value is anything other than 0, visibility will be set to inherit. It is not set to visible in order to honor inheritance (imagine the parent element is hidden - setting the child to visible explicitly would cause it to appear when that’s probably not what was intended). And for convenience, if the element’s visibility is initially set to hidden and opacity is 1, it will assume opacity should also start at 0. This makes it simple to start things out on your page as invisible (set your CSS visibility: hidden) and then fade them in whenever you want. //fade out and set visibility:hidden gsap.to(element, {duration: 2, autoAlpha: 0}); //in 2 seconds, fade back in with visibility:visible gsap.to(element, {duration: 2, autoAlpha: 1, delay: 2}); Also to better help you and please setup a limited codepen demo example so we can test your code live. Since trying to debug your code from your website will be really hard without your isolating the GSAP issue. Happy Tweening!
  18. 1 point
    Hey fernandofas and welcome. Three issues: You have a script tag that tries to use GSAP and DrawSVGPlugin before the script tag where you load them - whoops! Make sure that you load GSAP and DrawSVGPlugin first. Second, it looks like you're trying to use the module version of DrawSVGPlugin. You should use the UMD version instead as it's meant to be loaded via a script tag like you have. Once you have everything loaded correctly, you get an error about tl being undefined. Just add something like var tl = gsap.timeline() before you use tl for that to be fixed. Happy tweening!
  19. 1 point
    Assuming it does not impact performance I would say it be would desirable. It is rather counter intuitive the way it needs to be handled now and likely to trip up a lot of people. And the resulting code would be simplified and easier to follow when things get complex.
  20. 1 point
    Scale is going to be exception and few other properties like skew, you will need to use modifier on scaleX and scaleY. Though you can use same function as modifier on both properties. Performance, I have never noticed any negative impact on the performance but it depends on how much calculation you are doing. I wouldn't use it for every tween unless it is necessary. @OSUblake is master of modifiers plugin, he will know better.
  21. 1 point
    Scale is actually 2 different calculations. var tween = TweenMax.to('.red', 1, { //this value won't matter scale: 2, modifiers: { scaleX: scaleModifier, scaleY: scaleModifier } }); function scaleModifier(scale) { if (scale > 1.5) return 1.5; return scale; }
  22. 1 point
    Hi all, It seems the default value for transformOrigin has changed (but not the documentation). It broke some of my older animations that expected the origin in the center. While TweenMax 1.11.8 was fine, my animated bicycle was shattered all over the screen with version 1.15 (or gsap/latest). I thought I'd let you know
  23. 1 point
    Hi potatoDie you can change the transformOrigin with this : TweenMax.set(element,{transformOrigin:"50% 50%"}); pls read the CSSplugin Docs : http://greensock.com/docs/#/HTML5/Plugins/CSSPlugin/ http://codepen.io/MAW/pen/MYyzpv
×