Answered
why does createjs implement less efficient timers
Hi.
In my animation sequence an object redraws approximately 100 times at regular intervals. To start the process there is a timer.
Comparing the performances of
a) start = createjs.Ticker.getTime(true);
and
b) start = performance.now();
The same process requires almost 20 seconds with the Ticker compared with performance.now(), about 12-15 seconds. This is not exaggerated.
Can anyone explain why there is such a huge difference at a constant framerate? 20. Does performance.now() ignore the framerate and set its own default -- higher?
Moreover, createjs.Ticker appears incapable of the high speed even when raising the framerate.
createjs.Ticker.framerate = 60;
Hardly any difference.
Thanks in advance.
AdChoices