In the new Facer 2.6.0 beta, animations that use the #DWE# tag appear to be broken.
Thanks for the bug report! We’re going to look into it today!
Facer Dev here. Can you go ahead and post a link to the watchface so we can take a look?
This one is a good example: SPARETIME - Burst - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer
Alright, cool. I took a look at Burst, as well as a few others I knew were using the #DWE# tag. I’ll drop the links for those below so you can check them out yourself and see if those work for you.
On my devices, it looks like the #DWE# tag is working consistently, and Burst’s animations look great on my phone. On the watch, it’s a little bit of a different story. The framerate takes a sharp dive and can’t keep up, so the end result is an ugly mess – or in the most extreme case, the animations are skipped entirely.
The other faces I tested look fine, though, it seems to be just this particular face having a hard time. Testing the face in our production build was a little better in my case, but not a whole lot.
The good news here is that I know what the problem is, and a general performance pass should improve it significantly. There’s some other things in the pipeline ahead of it, but I’ll probably be tackling it sometime in the next couple days.
If you’re running into another issue, though, please let me know. I’d be happy to take another look and see if we can get it squared away.
Thanks for the feedback!
Also, here’s a couple other faces I looked at:
Matt - Disk Face - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer (Spinning text is done with #DWE#)
Matt - Ultimate Power - watch face for Apple Watch, Samsung Gear S3, Huawei Watch, and more - Facer (Fade in/out is done with #DWE# and an interpolator)