Just how drastically faster?
x2?
x10?
From the link above on "How much is too much - Elements
Test 1: tr0n09 - Dance Ninja - Test 287 frames - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Test 2: tr0n09 - Dance Ninja - Test 160 frames - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Test 3: tr0n09 - Dance Ninja - Test 90 frames - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Test 4: tr0n09 - Dance Ninja - Test 30 frames - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Test 5: tr0n09 - Dance Ninja - Test 16 frames - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Explanation:
Test 1: Facer - Thousands of FREE watch faces for Apple Watch, Samsung Gear S3, Huawei Watch, and more
I painstakingly uploaded all 287 frames. I stripped the images down on Kraken to less than 1Kb each. All told it was 1.12MB. The uploader halved the sizes so I’m sure the actual is even smaller. Going off of that I did a 8 f/s transparency animation. In the test I get performance at around 1 frame every 1.4 seconds. This clearly points to a limitation in the number of elements and not necessarily the size of the image. Every now and then the app resets too. So not good.
Test 2: Facer - Thousands of FREE watch faces for Apple Watch, Samsung Gear S3, Huawei Watch, and more
I reduced the overall count to 160 frames. Now I get around 1 frame every 0.8 seconds. A 45% reduction in frame count resulted in about a 40% performance increase.
Test 3: Facer - Thousands of FREE watch faces for Apple Watch, Samsung Gear S3, Huawei Watch, and more
Reduced again to 90 frames total. animation is now 1 frame every 0.429 - 0.538 seconds. So closer to 2 f/s at this point.
Test 4: Facer - Thousands of FREE watch faces for Apple Watch, Samsung Gear S3, Huawei Watch, and more
Nearly the frame rate chosen. Intervals on the #DWE# tag are around 0.18 - 0.28. that’s close to 5-6 frames a second.
Test 5: Facer - Thousands of FREE watch faces for Apple Watch, Samsung Gear S3, Huawei Watch, and more
16 frames, met or exceeded the 8 f/s. Goal was 0.125 duration. #DWE# time counted off between 0.08 - 0.13 each render interval.
So in the end, what was the goal of the tests? I wanted to determine the average performance of animations using standard expressions. The limitation seems to be with the total count of images loaded.
If you are shooting for smooth animations, you should probably limit things to less than 20 images and a framerate of 8-10 f/s. If you want a longer animation, you could bump the framerate to 4-6 frames per second with at most 30-60 images. Anything more than that and you hit a large performance barrier. For my recent faces I’ve tried limiting my submissions to the 2 second squarewave loop on 16-20 frames. Others I’ve used the #DWE# expression with 6 f/s for 5 sec (30 images total). Things can still get choppy with each.
Anyways, there it is. Note all calculations were on my Huawei watch and eye balling the #DWE# counter.
Also try my newest creations (Note these are still drafts being worked on). First 2 have 12FPS for 2 seconds (24 images):
the next is 9FPS for 2 seconds (18 images):
And one final one for 10FPS for 10 seconds (100 images):
this is incompatible with my Galaxy S8
@Facer_Official When I went to Google Play and initiated installation, it triggered the Facer swirly screen on my Huawei but then nothing happened. It says it’s installed on Google Play, but I still haven’t been able to access and check out this watch face. What am I missing here?
I installed it, but it’s not communicating with my Moto360 Gen2.
AW 2.7.0.
It installed fine via my Samsung S7 to my Huawei. Animation looks relatively smooth. Would love to see how some of my other examples would fare.
1 Like
Ooo, silky smooth.
2 Likes
Getting some weird results with some text. This is what I get with my GoTo Weather design.
Weirdly enough the vowels are missing in the “Weather” title.
Are Gyro functions working on the new engine update?
Its working on my Fossel Q Explorist, and can definitely see a different in the animations!
I have and iphone, when i try to add new faces from the iphone facer app, it will not sent it, i can see the Plaetary app is spinning, but the new face is not showing.
They’ll be working in the next beta, but the current one has gyro disabled. We’ll also look into the font bug!
1 Like
Is the random number generator also not working as intended?
That shouldn’t have changed - can you give me a link to a face where it’s not working?
Technically its working, just not as expected. Just released the following design. The digits for the date bar should cycle through random numbers for about three seconds, then lock on current date. Looks ok in creator preview. However, on the app (phone) and watch, the randomizer locks on a random number and does not cycle.
Will it ever be there a chance of having modulo operation in the face editor? If I may ask…