I created a watch in te creator with a floating second hand. (#DWFSS#)
This worked fine in the preview in the creator.
Then I open the Facer-app on my tablet, The standard preview is showing also a floating second hand, when I open the watch to download it, it is appearing with a ticking second hand as if #DWFS#.
Try Download it again . Put ( ) Round the Formula . Show us here . Sadly #DWFSS# is the only smooth timer we have now and I guess they are chipping away at that , all in the Power saving Efforts .
Sadly . Sometimes On Creator I get hidden Bugs . Make a new Image Layer put your hand in and Type the Formula / Tag by hand . Delete the previous layer . Try that . I presume it is not published . I can test it for you if you post the Link .
Works fine for me on my GW4 . I must say that it seems a bit of a Lump on Syncing . It took a while to come from LA . Are the Resources High Definition .
.
.
This is only a comparative test . Open the preview in The Web App and hit Right Mouse / Inspect then Memory . I note that this Face is as Loaded as my Private Face which I don’t use smooth Second on because it is glitchy . This is about the only Memory Test you will get easily . Try it on one of the templates to see the difference . Obviously the numbers do not reflect what is on the watch but give you some thing to compare faces . I would say your face is heavy on memory .
.
.
I have a Fossil Carlyle watch I use for testing and all of the smooth second hands rapidly tick on it. The same watchface on my Galaxy watch 1st gen, (Tizen) and my other GW watches, (6 Classic and 5 Pro, both WearOS) will show a smooth second hand. It’s just something about how each watch company sets up their watch programming to function.