Mike at BrashMonkey Posted January 28, 2019 Report Share Posted January 28, 2019 @Revagames I spoke briefly with Edgar about your issue and his thoughts were as follows: it seems like it's a bug in either your code or the SpriterPlusPlus code that's leaving easingCurve set to null or pointing somewhere invalid. Unfortunately Edgar will not be able to look into this anytime soon, as Spriter 2 requires his full attention until we hit certain milestones, but he suggests debugging with a breakpoint in that function in order to verify, and going back through the callstack to see when the issue happens would be the first step to looking into it. Let me know if this is helpful. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.