Blaze Posted January 22, 2020 Share Posted January 22, 2020 I keep seeing this once in a while since I've updated my project from GSAP2 bezier to GSAP3 motionPath. When I hit the play button it continues ok, so doesn't seem to be critical. Never seen that on GSAP2. Link to comment Share on other sites More sharing options...
GreenSock Posted January 22, 2020 Share Posted January 22, 2020 Welcome to the forums, @Blaze. Is there any chance you could share the path data string with me? It sounds like an edge case related to the distance of the anchors from one another. There's a performance optimization that MotionPathPlugin (and CustomEase) uses that pre-cache certain measurements so that it's much faster during the tween (when smoothness is most important) and it looks like maybe your path requires an unusual amount of those measurements, so I'd like to see why. 1 Link to comment Share on other sites More sharing options...
Blaze Posted January 27, 2020 Author Share Posted January 27, 2020 Link to comment Share on other sites More sharing options...
Blaze Posted January 27, 2020 Author Share Posted January 27, 2020 Link to comment Share on other sites More sharing options...
Blaze Posted January 27, 2020 Author Share Posted January 27, 2020 Link to comment Share on other sites More sharing options...
Blaze Posted January 27, 2020 Author Share Posted January 27, 2020 Link to comment Share on other sites More sharing options...
Blaze Posted January 27, 2020 Author Share Posted January 27, 2020 Had to run it for a while to see this happening again, I've got basically about 1500 3d points flying around on different motion paths at the same time. All motion paths are very similar. Up to three x/y/z coordinates. Thank you for checking this out! Link to comment Share on other sites More sharing options...
GreenSock Posted January 27, 2020 Share Posted January 27, 2020 I wasn't asking for screenshots of the GSAP code or instances - I was asking for the actual path data that you're feeding in. Can you please provide that? My guess is that some of the points are SUPER close together (and could therefore be eliminated). Link to comment Share on other sites More sharing options...
Blaze Posted February 3, 2020 Author Share Posted February 3, 2020 Sorry this wasn't helpful, I've tried to extract the paths I am generating in my project in a codepen, they are all auto generated, that's basically what I am doing, but I can't get it to come up with the same warning in the codepen. I'm not sure what is causing the problem also bear in mind I have to run my set up for days before I see this happening, I'll keep an eye on it See the Pen MWYZLLb by blaze747 (@blaze747) on CodePen Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now