Jump to content


  • Posts

  • Joined

  • Last visited

1 Follower

Contact Methods

Profile Information

  • Gender
  • Location
    Brooklyn, NY
  • Interests
    computers, video games, photography, travel, food, hip-hop

Recent Profile Visitors

6,035 profile views

flysi3000's Achievements

  1. Thanks @Jonathan. It was the latest versions of Safari on the latest version of macOS 12, but only on non-retina screens. I seem to have fixed the problem in the interim, using a combination of the fixes suggested above. Interestingly, I tried replicating my problem on CodePen (with a crap-ified version of the client's artwork), but couldn't get the same blurry scaling issue, though, so ultimately, I'm not sure what was going on!
  2. Thanks @greensock! I know it's not a GSAP thing, so I really appreciate you taking the time to share some tips!
  3. Hi @Cassie, yeah I tried force3D: false; I’m bringing the svg in at about double the size I need it at and scaling it down. Again, it looks great on all the browsers except Safari on non-retina displays.
  4. It's that time... resurrecting this topic, with the caveat that I only see the blurry svg on Safari on non-retina displays. Sorry, I don't have a codepen; just wondering if anyone has seen this, or has any tips for a fix. 🤞
  5. Aha, I think that was the part I was missing - how to grab the current target. Thanks, I’ll give this a shot!
  6. I feel like this has to have been asked before, but if so, I can't find it. I'm trying to replicate a text typing animation, with a blinking cursor (or insertion point) that follows the text. Animating character by character with SplitText is easy, but does gsap expose a property where I can I figure out the position + width of the current character, and position my blinking "cursor" relative to it? Or am I approaching this in the wrong way? Thanks y'all!
  7. Ha, I found that immediately after I posted this - thanks!
  8. Hey all, I'm looking for the GSAP 2.x demo of using the Modifiers Plugin to make an infinitely scrolling carousel. While I'd love to use GSAP 3 as shown in this example, I have to use GSAP because our animation tools haven't been updated quite yet, and I need to get some client work out the door. Any pointers for where I can find the older syntax? Thanks!
  9. Ah, true, true... I was just curious and thought I'd ask here cuz I figure this is a pretty in-the-know crowd.
  10. Hearing more and more about Lottie lately (plugin for exporting animation from After Effects to JSON), and as I understand it, the real obstacle to using it for banner animation is the weight of the js library. Now that support for it is coming in Adobe Animate, might we have a strong enough case to get it white-listed (like gsap, createjs, etc)?
  11. Chiming in, just because I saw this the other day as well and had the same freakout, but then I realized that it happened when viewing our ads in a private window in Firefox. When viewing in a regular tab, I think it's okay, but it bears a little more research (which I haven't had the time to do yet).
  12. Whoa - that page is a treasure trove of helpful stuff! Thanks!
  13. Woo! I actually used easeInOut on the main tween, and stepped the other one - so the inverse of what you suggested. Seems slightly more noticeable, but I guess in essence it's the same thing. Thanks for the speedy reply!
  14. Hi! I have a hypothetical question - some creative feedback I got for an animation was to make it more "stop-motion-like" but at the same time, add some easing in/out to it. My initial reaction was that this is self-contradicting feedback, but then I thought that if I were actually shooting some stop-motion animation, I could actually add easing by adding more frames at the beginning or end of the sequence. Is this something we can simulate with GSAP? I'm currently using SteppedEase, and was thinking I could take my existing tween, and tween its progress with an easeIn/Out applied to that. Is that nuts? Is there a better approach?
  15. Thanks for the input, guys. @geedix I was looking at those specs; I think we had more than 10 external images, though - that's probably why we got the banners kicked back. I ended up solving it using a couple of gulp tasks to parse the js for image file paths and base64 encode them inline, then inline the js into the index.html file. I managed to get the files down relatively small, but I had to start with non-retina images. It was a lot of f*cking hoops, and I told our producers it seemed really excessive, but we just wanted to get these out the door, so I didn't push the issue too much.