You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For animations, it seems to me a layer should update at the framerate of the fastest sprite animation on that layer instead of at the screen refresh rate? For example, it seems if I have multiple sprites but have started animation on only 1 of these with a framerate of 1 frame per second, the entire layer is erased and all sprites redrawn an my screen's refresh rate (typically 60Hz). I'm concerned about how this will affect performance, especially on lower-powered Android/iOS devices.
The text was updated successfully, but these errors were encountered:
You're correct, assuming that there are no other animations running alongside the sprites. For cases when you are running other animations, tweens, or dragging and dropping stuff, while sprites are animating, you don't want to only refresh a layer when a sprite is updated. Also, for people who are using Sprites with different frame rates, the layer redraw rate is no longer constant.
Essentially, you have a special use case, in which the only thing driving layer redraws are sprite animations, and each of your sprites have the same frame rate. What I need to do, is to add logic that detects this condition, and then redraws layers only when the sprites update. The moment that another animation or tween is detected on the same layer, Kinetic would have to switch to the current model. I'll add this to my todo list, thanks!
For animations, it seems to me a layer should update at the framerate of the fastest sprite animation on that layer instead of at the screen refresh rate? For example, it seems if I have multiple sprites but have started animation on only 1 of these with a framerate of 1 frame per second, the entire layer is erased and all sprites redrawn an my screen's refresh rate (typically 60Hz). I'm concerned about how this will affect performance, especially on lower-powered Android/iOS devices.
The text was updated successfully, but these errors were encountered: