Amazfit Watch faces

Firmware bug? Or is the screen of my Mi band 6 faulty?
https://i.postimg.cc/K8jMBcPs/0000.png
https://amazfitwatchfaces.com/mi-band-6/view/3455
This watch face has 3 lines running along the edges (yellow, red and green).
On my Mi band 6 the yellow line is missing everywhere, in fact at the ...

@lvpokka:
Please give us some info about "Lunar calendar".

@schmitty782 :
Set "UsePaletteMode" value="1" in file WatchFace.exe.config

Suggestion for improvement:
The display of the MB5 has rounded corners.
It would be nice if the corresponding pixels were also set to black in the preview.

My own and at the same time (of course) my favorite: https://amazfitwatchfaces.com/mi-band-5/view/449
There is an english version too: https://amazfitwatchfaces.com/mi-band-5/view/450

Next preview bug:
"StepsProgress": - "CircleScale":
MB5 stops drawing the progress bar if "EndAngle" is reached, preview drawes around...

Update
Tested with new firmware 1.0.1.84: All bugs still remaining

"Alarm" - preview bug
"Text": OK
"ImageOn": OK
"ImageOff": OK
"ImageNoAlarm": The red line in my example should start at X=0 and Y=17, but starts at the position defined in "Text"

On MB5 all works like expected.

"Alarm" - "ImageNoAlarm":
X and Y not working in preview, Image is shown always at text position

MiBandWFTool viewtopic.php?p=1817#p1817

You probably come from a country where the number of the weekdays was used as name anyway.

Only if you can interpret "4" instantly as Thursday.

So "pretty" is more important than the legibility of the information displayed?

Why are these Watch Faces

https://i.postimg.cc/PqL80GN3/1597773222-0e9c00fcc7-1.gif https://amazfitwatchfaces.com/storage/mi-band-5/img/1597627217_91231b7457.gif

downloaded more times than these:

https://amazfitwatchfaces.com/storage/mi-band-5/img/1598077598_2c68a2c162.gif https ...

The bottom alignment bug in preview ist NOT fixed !

see viewtopic.php?p=6371#p6371
and viewtopic.php?p=6374#p6374

Yes, it was not supported by purpose. It's not possible to get data from photo wface because its just a dummy and all compilations was performed on uploading to mi band 5

Are you sure that it's just a dummy?
I think that there is in the MB5 an overlay with a PNG with alpha blend to give all white ...

I want to show here all known MB5 firmware bugs concerning custom WFs:
- 2 or more animations are always running with the speed of the slower one
- Seconds are not really working (analog and digital)
- UVI and wind are not working together with other weather features (current temperature)
- heart ...

MiBandWFTool cannot unpack the MI stock WFs of the "Photo Watch Face" series (Style1 ... Style5).
The following error message appears in the log file: Debug|Parsing parameters...
Trace|2 'Background'
Trace|2.1 'Image'
Trace|2.1.1 'X': 0
Trace|2.1.2 'Y': 0
Trace|2.1.3 'ImageIndex': 59
Fatal|System ...

"Time": "DelimiterImage" is still not displayed in preview.
"Time": {
"TimeDelimiterImage": { // visible in preview
"X": 95,
"Y": 168,
"ImageIndex": 92,
},
"DelimiterImage": { // NOT shown in preview
"X": 0,
"Y": 168,
"ImageIndex": 92,
},
},

Pulse: NoDataImage is not shown in preview.

@GIK-Team:
Take a look at THAT: https://amazfitwatchfaces.com/mi-band-5/view/362
and then say again that I am not creative enough ...

In Current_Speed you can see the bottom alignment problem. Look on the decimal point.
The km looks OK here, because the km image has the same height as the digits.
The bug occurs only if a prefix/suffix/delimiter image has a height different from the digits height. https://i.postimg.cc/zBVLZvPD ...

MiBandWFTool preview shows not the same alignment as MB5 with "Alignment": "BottomXXXX".
On MB5 then decimal point and the km are bottom aligned, in preview not.
DecimalPointImage is 3x3, KmSuffixImage is 20x12, digits are 9x16

OK, animation speed IS a firmware bug, sorry.

But:

Unpacking stock WF "Aurora Glass": Trace|12.2.3 'ImageIndex': 63
Trace|12.2.4 'ImagesCount': 6
Debug|Generating previews...
Error|System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei WatchFace.Parser ...

There are no stock watchfaces with 2 different animation speeds.

Could you fix the "DelimiterImage" preview bug ?