So I’ve been testing out creating animations using the transparency field. With the help from @Mellin I made an in depth tutorial of how to use a conditional expression to essentially recreate an animated gif. One of the things I’ve been curious about has been the performance of animations. I’ve published several that are slow 4-8 frames per second, and several that are fast 10-20/sec. I have also played with a variation on the animation expression in creating longer examples based on the wake functions instead of a simple looping one on the second counter.
Through all of this I’ve noticed the performance is somewhat spotty on faster animations. Even when watching some of the slower ones, there doesn’t seem to be the smoothness I would expect. To experiment further I’ve created several prototype faces:
Syncing these with my watch the 4, 5, and 8 frame prototypes seems to display all frames consistently. I do still notice that sometimes there’s a herky jerky movement. When I try and sync the 16 frame prototype, I can see the watch only displaying the odd numbers. So only 8 frames are showing per second. Clearly a fail.
So the question becomes, is this a Facer limitation or is it a watch performance limitation? I’d like to see others test additional watches of various brands and see what the outcome is with the experiment. Also when I get some additional time, I will create a 10 and 20 second prototype.
Let me know what happens when you load the faces. Do you see all the frames? Is your’s silky smooth or does it judder and sputter?
My Watch: Huawei
RAM: 512 MB
CPU: 4x Arm Cortez A7 @ 1190 MHz