Jump to content

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

Shrug ¯\_(ツ)_/¯ last won the day on March 23 2021

Shrug ¯\_(ツ)_/¯ had the most liked content!

Shrug ¯\_(ツ)_/¯

  • Posts

  • Joined

  • Last visited

  • Days Won


Shrug ¯\_(ツ)_/¯ last won the day on March 23 2021

Shrug ¯\_(ツ)_/¯ had the most liked content!

1 Follower

About Shrug ¯\_(ツ)_/¯

Recent Profile Visitors

4,454 profile views

Shrug ¯\_(ツ)_/¯'s Achievements

  1. @akapowl Unless I'm mistaken I think thats already the lib that was being loaded in the codesandbox? Here is another wrapper for React Components using that same smooth scrollbar library, if it helps anyone.
  2. You may get some use out of insertBefore (some information seen here) like the below two examples. https://codepen.io/osublake/pen/YXoEQe https://codepen.io/GreenSock/pen/yLYJodZ Edit: Sorry @GreenSock, I just looked at your Pen after the fact, which is what you are doing. ☺️
  3. You may like this thread Specifically .. https://codepen.io/GreenSock/pen/8fcb337385d0f1e401a66f260cf73e76 You might be also able to use some logic from the below example that uses GSAP, Draggable, SVG.js and Spline. https://codepen.io/georgedoescode/pen/ExNpqJP
  4. It sounds like you instead want the stack of images to fade through as you scroll? If so then you can remove the pin, try scrub: true, adjust the start &/or end values and play around with the next var (stagger) and fade var . Just play around until you get everything to your liking (if you want to stick with that example). The ScrollTrigger Docs have detailed information on those things along with links too many ScrollTrigger examples and demos. I sugggest you take time to get familar with the usage.
  5. Welcome to the forum @LivingInAZoo This codepen by @mikel seems to have most of what you described. Hopefully you can modify it to your own needs by using it as a starting point while using the documentation to assist you further. https://codepen.io/mikeK/pen/NWRoQJo
  6. Sorry to nudge this thread I’m just seeing it and could not resist a little reminiscing. I remember this exact same effect back in the Flash / Actionscript days. It was something like using a few containers, swapping depths and image sources. Along with the scaling & fading of pre-rendered distortions and blur on identical yet much smaller images done in Photoshop used for the in/out transitions. The transition part would happen so fast you never really noticed the difference going between the two actual images and the two transition images scaling / fading. Those cleaver manual techniques have largely diminished with the presence of more modern dynamic approaches available today. Plus screen sizes were a lot smaller and of less quantity back then. Now with 4K, 5k, 8K monitors and thousands of devices dynamic WebGL, PixiJS, Shaders, etc., are the way to go ... GPU to infinity and beyond. 😄
  7. Really nice @mikel, you +next leveled+ this previous peel effect. 😉
  8. Nice one @OSUblake. This related Three.js Forum thread has some good advice for those seeking similar. If that's actually your thread @Lolia Trafam then please reference this GSAP thread over there as this discussion here might help other Three.js + GSAP users also. 😉
  9. ^ Yeah that one and many more can be found throughout the forum.
  10. Maybe the links in this post will also help you some. ¯\_(ツ)_/¯
  11. I look forward to seeing your outcome if you're able to share. For anyone else looking for similar but resulting in a less dynamic result, you could use your own map artwork like the below example. It may help someone in some way. ¯\_(ツ)_/¯ https://codepen.io/oliviale/pen/jOryjNX
  12. I saw the below drawSVG + canvas recently, it seemed interesting though its needs updating to GSAP 3. I wonder if there could be a cleaver helper function like this morphSVG function? Maybe something from this codepen approach could help you in some way superM. https://codepen.io/cjgammon/pen/poeMmqY
  13. Some of the examples found in the thread may also assist you in some way.
  14. 😂 Just as IE announces the EOL date, Safari looks around and continues to step forward to fill the void.