dreinzy Posted October 23, 2018 Share Posted October 23, 2018 Using the action manager's .registerActon and .then, if I start the next interpolation before the previous one finishes, it looks like the last 'frame' briefly flickers while the second one is playing. https://playground.babylonjs.com/#LXF99J Click the sphere to start it moving, click it a second time before it's finished animating to see the effect. Is this the expected behaviour? Is there a way of avoiding it? NasimiAsl 1 Quote Link to comment Share on other sites More sharing options...
dreinzy Posted October 23, 2018 Author Share Posted October 23, 2018 Curiously, the effect doesn't happen if I add a second object and move both of them back and forth at the same time... https://playground.babylonjs.com/#LXF99J#1 Quote Link to comment Share on other sites More sharing options...
Guest Posted October 23, 2018 Share Posted October 23, 2018 Even on your second example I can see it and it is expected because you have two concurrent animations on the same property. So depending on the internal animator, they will override the same property. You will need to force the action to cancel other ones before running: https://playground.babylonjs.com/#LXF99J#2 (Check the last parameter of the InterpolateAction constructor) dreinzy 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
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.