Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

atgc-core-tween: implement our own tween engine #34

Open
jbilcke opened this issue Feb 9, 2015 · 0 comments
Open

atgc-core-tween: implement our own tween engine #34

jbilcke opened this issue Feb 9, 2015 · 0 comments

Comments

@jbilcke
Copy link
Member

jbilcke commented Feb 9, 2015

creating thousand of new tweens is a costly operation because it involves a lot of prototype instancing, playing with lambdas, and memory writing, during gameplay the framerate drops quickly :(

it would more efficient to have a pre-allocated array of tweens, pre-initialized with same functions, and recycle them. also, maybe we should compare the function to just reusing existing one (ie. if we have 100000 tweens, to not create 100000 lambdas but reuse the same)

actually I need to check the inside of tween.js, either we fork tween.js to add ra .recycle() function, or we create our own, if the tween.js architecture doesn't allow this kind of modification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant