Search the Community
Showing results for tags 'hardware accelerated'.
-
(This following might be more or less a colleage of related, yet independent thoughts) I suppose I just want smoother transitions in my sprite movement. I'm trying to address the issue with my sprite.position changes.. which are currently just incremental. http://www.iakarra.net/demo/polymer/WiAClient/index.html where as, http://www.iakarra.net/demo/polymer/WiAClient/wiia.account.js actually contains the update function/method (and in turn calls on the 'character.step' function) that is executing on every animate call/tick on the main page. So this is really the scope I'm concentrating on. Alright, so I'm familiar with the concept of css transitions being smoother than javascript animations because they are 'hardware accelerated'. but from this article: http://css-tricks.com/myth-busting-css-animations-vs-javascript/ it becomes apparent that javascript can be hardware accelerated as well. And the speed/execution myth was really invalid and perpetuated because people were basing their comparison on jquery animations. Referencing the following: http://chimera.labs.oreilly.com/books/1234000000802/ch05.html#animating_by_programmatically_updating_p as well as the following sections in/to that reference 'tweening' and 'interpolation' I hope to add a time-based animation (movement) using this javascript hardware accelerated concept.. Is there anything within the PIXI framework that I should account for when I do this? Or has someone implemented something similar to what I'm trying to accomplish? With my mild experience with the XNA framework, I noted that it passed around a gametime tick/timer.. In another post on here, I made reference to the requestAnimation method using the window.renderAnimationFrame .. based on date.now()... though that time did not seem to be global..