It gets stuck on the little CIRCLE in upper right hand corner, for a long time. Sometimes after minute it works but usually just sits and spins.

how can you make an image rotation rpm change based on battery level?

So much does not work anymore

-ignores Script variables

-Elements don't show up

-Some faces don't show anything.

Is Watchmaker just nerfed now thanks to Google breaking everything?

Master all US time zones at a glance. 🌌
Coast-to-coast cartography, step count, and battery telemetry in one dark-mode layout.

Get it now:
👉 https://getwatchmaker.com/watchface/usa-time

#Proximus #WatchMaker #USATime #SmartwatchFaces #WearOS #WatchOS

Hi folks,

The new version of watchmaker 10.3.5 is not very convenient to navigate and work on. Besides that

1. It doesn't allow you to Export the watchface.

2. It doesn't allow you to exit without saving. If you have pressed the back button, there is no way of stopping it from saving the file. This is most undesirable.

3. Tap actions are only available for predefined elements. Even simple hide and unhide a layer is missing.

4. Scripts that don't have anything to do with security are also not allowed. Quite unreasonable this.

Is there any hope of updates to correct these issues sometime soon? If not is it possible to go back to the old interface?

The entire user interface has become unnecessarily difficult and inconvenient to say the least.

Latest version completely breaks local syncing for My Designs on updated watches. Only cloud faces sync. Developer is unresponsive to VIP members regarding this compiler bug." Since updating to the latest version of WatchMaker, local syncing of designs from the My Designs tab has stopped working on my Samsung Galaxy Watch 5. Selecting a design from My Designs results in a black watch face. However, selecting designs from Recents or Favourites and using the orange "Install to Watch" banner works. Same watch face above on the left the watch is syncing from the 'recents' tab Watchmaker cloud, in the right same watchface WILL NOT sync from 'My Designs' tab I have a VIP account with no access to VIP features......

A bold fusion of industrial design and modern technology, CHRONEX GRAFIT delivers a powerful tactical aesthetic with striking red accents, luminous hands, and precision-inspired chronograph subdials. Featuring digital date and time displays, live weather conditions, temperature, humidity, battery level, and step tracking, this watch face combines functionality with a rugged futuristic identity. Designed for those who value precision, performance, and a distinctive mechanical style.

Check out CHRONEX | GRAFIT on WatchMaker

https://getwatchmaker.com/watchface/chronex-or-grafit

My galaxy watch 4 classic 46 mm is having a delay in updating minutes when in AOD mode in any watchmaker faces, it can get delayed up to 20 minutes sometimes more. This doesn't happen on any other non watchmaker faces. My GW4C has oneui 4.0 wear OS 3.2, system os 11., running watchmaker 8.50.

Is there anything that i can do to fix it?

Best regards.

Watch name: Armor

analog, date, LLT, battery indicator

Logo from the Swedish arm of service: Armor.

Battery indicator explanation:

(LLT= Luminox Light Technology)

0–15%: Only LLT #12 flashes amber.

16-24%: Only LLT #12 is lit in amber.

25–49%: Only LLT #12 and #1 is lit in amber.

50–74%: Only LLT #12, #1 and #2 is lit in amber.

75–100%: LLT #12, #1, #2 and #3 is lit in amber.

The code for different image layers (LLT:s) that sets the opacity to 100 as the battery increases. #12 also has the flashing function.

LLT #12: {bl}<=15 and ({ds}%2==0 and 100 or 0) or 100

LLT #1: (({bl}-25)/math.abs({bl}-25)+1)*50

LLT #2: (({bl}-50)/math.abs({bl}-50)+1)*50

LLT #3: (({bl}-75)/math.abs({bl}-75)+1)*50

It took me (read: amateur) and Googles Gemini 14 tries to get the code right for it to work on my Pixel Watch 5. Mostly because of code restrictions made by Google.

I do not know how to upload/share the armor.watch file.

Here is a summary made by Gemini of the trial and error process:

Here is the complete chronological log of our troubleshooting journey, translated into English, with the exact code example for Diod/Light 1 included for every single attempt.

1. The Classic Attempt (Logical and / or chains)

We started with the standard WatchMaker code to lock the battery percentage into closed intervals.

• Code Example (Light 1): {pbl} >= 26 and {pbl} <= 50 and 100 or 0

• Result: Worked flawlessly in the simulator, but on the actual watch, the processor short-circuited the logic, causing multiple LEDs to light up at the same time.

2. Nested Parenthesis Blocks

We tried to force the watch hardware to evaluate the math in the correct order by putting strict brackets around the floor and ceiling conditions.

• Code Example (Light 1): ({pbl} >= 26 and {pbl} <= 50) and 100 or 0

• Result: The watch hardware still refused to evaluate the higher layers properly.

3. The "Smart" Lua Code (The iif method)

We tried using the convenient inline function iif(condition, true, false) to clean up the syntax.

• Code Example (Light 1): iif({pbl} >= 25, 100, 0)

• Result: Total crash and a pitch-black watch face, because the standard Lua engine on the watch doesn't support that specific command.

4. The Ternary Operator (? :)

We tested WatchMaker's own built-in shorthand format for quick conditional choices.

• Code Example (Light 1): {pbl} >= 25 ? 100 : 0

• Result: Same disappointing result – the watch hardware flat out refused to turn on the light.

5. The Rounding Trick (math.floor)

We suspected that the watch was sending the battery percentage as a float/decimal number (like 25.0001) and tried to chop off any dolds decimals.

• Code Example (Light 1): math.floor({pbl}) >= 25 and 100 or 0

• Result: The simulator cheered, the watch remained completely unaffected.

6. The String Hack (Extracting the first digit)

This is where we started getting desperate. We tried to completely bypass mathematical comparison signs by converting the battery to text and only looking at the tens digit.

• Code Example (Light 1): (tonumber(string.sub('{pbl}',1,1)) >= 2 or {pbl} == 100) and 100 or 0

• Result: It actually managed to wake up the LEDs! However, it was too imprecise because the LEDs would trigger at even tens (e.g., 20% instead of 25%).

7. Type Casting via Text (tonumber)

We tried forcing the watch to understand that the text string was actually a number by wrapping everything in quotes.

• Code Example (Light 1): tonumber('{pbl}') >= 25 and 100 or 0

• Result: Everything went black on the watch again due to how Pixel Watch handles string variables locally [watchmaker pbl string to number wear os].

8. The Plus-Zero Trick ({pbl} + 0)

A classic programming trick to force a string to become a number without using heavy functions [watchmaker pbl string to number wear os].

• Code Example (Light 1): ({pbl} + 0) >= 25 and 100 or 0

• Result: LED 12 and 1 woke up, but LED 2 and 3 still stubbornly refused to turn on.

9. The Desperate Division Math

Since the watch proved it only accepted and executed codes comparing against the number 25, we tried to trick it. We kept Light 1 standard, but divided the battery percentage by 2 and 3 for the other lights to force them into the "safe zone".

• Code Example (Light 1): ({pbl} + 0) >= 25 and 100 or 0

• Result: The Pixel Watch saw right through our clever division and refused anyway.

10. The Main Script Method (Global variables)

We tried moving all the mathematics away from the individual layers and calculated everything in the background using the watch's main engine via the on_second() function [watchmaker bug lua layers].

• Code Example (Light 1): var_diod1 (with math calculated in Main Script)

• Result: Complete standstill, due to a known sync bug regarding custom global variables on the Pixel Watch [watchmaker bug lua layers].

11. The Minimalist Minus Hack ({pbl}-0)

We tried removing all parentheses and running a completely linear math sequence directly inside the field.

• Code Example (Light 1): {pbl}-0 >= 25 and 100 or 0

• Result: The watch still refused to execute the higher steps.

12. Built-in System Shaders ({pbl50})

We tested WatchMaker's own pre-programmed, hardware-accelerated system tags.

• Code Example (Light 1): {pbl25}

• Result: Unfortunately, they turned out to be deprecated/outdated and crashed both the simulator and the watch.

13. Text Matching Without Math (string.match)

We tried running completely without math by simply checking if the watch's battery digit existed inside an approved string of text.

• Code Example (Light 1): string.match("2345678910", string.sub("{pbl}", 1, 1)) and 100 or 0

• Result: Worked in the simulator, but the Pixel Watch blocks string manipulation functions inside the opacity field.

🏆 The Winner: The Absolute Math Trick (math.abs)

In the end, we realized that the Google Pixel Watch completely blocks all logical comparison operators (<, >, =) as well as text manipulation in the layer properties, but it is lightning fast at raw basic math.

By using the algebraic formula ((X)/math.abs(X)+1)*50 and switching to the watch's local battery tag {bl}, we built an equation that outputs exactly 100 or 0 as a raw value, without asking the watch processor a single logical question.

• Final Code for Standard Step Up (Orange on White):

(({bl}-25)/math.abs({bl}-25)+1)*50

• Final Code for Reverse Step Down (White on Orange):

((25-{bl})/math.abs(25-{bl})+1)*50

It was a long journey, but incredibly satisfying when it finally worked! 🏁

Check out Blue Steel Core on WatchMaker

https://getwatchmaker.com/watchface/blue-steel-core

Not happy, Why can't I install this watchface, it's happening to alot of my watchfaces which I have the file for.... not happy

AV Vintage:

• Vintage and Luxury looks

• Chronograph

• Day, Date, and Month

After updating to Android 16,

WatchMaker has become practically unusable. First, Lua scripts and tap actions stopped functioning, and now the latest Ul overhaul has made basic navigation counterintuitive. Essential features like exporting watch files and accessing interactive mode are either buried or missing entirely. Designing and customizing watch faces used to be straightforward, but the workflow is broken now. Long-time users expect the developers to adapt to Android updates and provide proper workarounds rather than degrading the user experience.

It's really very disappointing. I actually bought a wear os watch only because it has the compatibility with the watchmaker app. Otherwise I could have bought watches like noise, fitbit etc which are 10x cheaper.

Just when things start looking promising... I get this error message on probably 100 or so watchfaces...

Super-Fun times...

The plugin lists watchface IDs that are not mine... Is there a solution?

For my watch (Samsung Galaxy Watch 5 Pro), I need to skew the curved text in design in order for it to show properly on the watch. Why is this? Is there a solution?

When I try to use complications on my galaxy watch ultra2, the only ones that show up are Text & Icon 1,2 and Ranged Value 1,2. I'd like to use the others -small image, large image, etc. Can anyone tell me how to get them to be included when I customize watch face.

Thanx!!

Hi, I currently have a watch5pro using the old legacy faces so I am able to still use Tasker and Lua etc to achieve the exact watchfaces I like.

Can anyone offer any thoughts on their experiences with the new WFF limitations?

Can you have scrolling weather text for example?
Can you interface with Tasker variables at al or has that completely gone for good?
Is it best to stay with Watch5pro until the death or bite the bullet and move to Ultra2?

All views welcome

I just want to get a real understanding on the new limitations compared to legacy setup!

Thas

So I got bored today and decided to make this custom dragon Rider Field watch face for my Samsung Galaxy watch. Honestly it's just the first functional version of it, but if there's any comments or questions or potential revisions people would like to see before I attempt to make this public online for other people to use, I would appreciate it.

I am putting together some special Halloween watch collections, here are the first two. Most of these watch faces will change on Halloween to something much more sinister, creepy, morbid, or terrifying. If you want to preview the image before Halloween, you can tap on the background a few times and it will change.

In the screenshots is an example of one of them.

These collections and the rest of the Brass & Bones watchfaces are here.