Hi - Been using GSAP successfully for animating HTML/CSS to great effect. I recently applied it to a visual concept I had, and bumped up against some performance limitations. I'm here to better understand if those limitations are inherent to PixiJS, or to GSAP, or if I'm overlooking some performance gains, or if it's just my misunderstanding of when to reach for WebGL.
Simplified summary of the design: I'm creating a grid of small colored squares (think: a low-res image, scaled up), and "exploding" the squares on scroll - each will travel in its own direction, with some rotation and scale. Proof of concept below. Works great! Nice and smooth.
However, if I try to enhance the effect by applying a blur to some of the squares, the frame rate drops to the point of unusability. (You can try this by uncommenting line 52 in the pen.)
I built an earlier proof of concept without Pixi - just divs + CSS - and hit basically the same wall. I'm new to WebGL and assumed it was just more efficient at redrawing, but it appears not in this case. Is WebGL good at, for instance, making something look like it's underwater, but no better than CSS at animating 100s of individual blurred graphics? Or is WebGL the right technology, but Pixi not the right tool? Or is the toolset absolutely capable of this, but I just haven't configured it correctly? Trying to suss out where WebGL shines and where it's not enough.
FWIW, been hunting around for examples of ScrollTrigger + Pixi and there aren't many. The link to such examples in your own documentation appears dead.
Thanks!