Inconsistencies in font rendering

I use a manually created custom font for displaying time in my watchface.

This font renders perfectly in the simulator for all supported watches - VA, epix and 920xt, it also renders perfectly on VA (and I believe epix) hardware. However, I have users reporting a rendering glitch on the 920xt!

This is a screenshot of the rendering on 920xt in the simulator


And this is what one user is seeing
Photo courtesy of splittingfield
You'll notice that there are extra white lines drawn at the top of the text.

Any suggestions would be appreciated because I'm not sure how to handle this since the simulator and other hardware platforms all render the font without issue.

Thanks,
Dan
  • Fixed the space issue like this, added a dummy space character

    char id=32 x=224 y=136 width=45 height=68 xoffset=0 yoffset=26 xadvance=45 page=0 chnl=15
  • OK, this is just getting ridiculous. I have now released a number of versions of segment since the first reported issue and tweaked the font in each, it now has a pixel border of padding around each side and yet it still continues to render incorrectly on the 920xt hardware:

    Example of v2.1.0 courtesy of user -fifithereal-

    It also appears that the icon for activity in the lower right corner is corrupted - all of the icons are in a single font and defined the same way and yet the others are rendering correctly. Again, there are no issues with the icons in the simulator or on other types of hardware, it appears to be restricted to the 920xt.

    Here is an excerpt from my font file for rendering the 7-segment time:

    info face="Segment" size=65 bold=0 italic=0 charset="" unicode=1 stretchH=100 smooth=0 aa=0 padding=0,0,0,0 spacing=0,0 outline=0
    common lineHeight=67 base=67 scaleW=425 scaleH=67 pages=1 packed=0 alphaChnl=1 redChnl=0 greenChnl=0 blueChnl=0
    page id=0 file="segment-border.png"
    chars count=15
    char id=48 x=0 y=0 width=42 height=67 xoffset=0 yoffset=0 xadvance=42 page=0 chnl=15
    char id=49 x=40 y=0 width=42 height=67 xoffset=0 yoffset=0 xadvance=42 page=0 chnl=15
    ...


    Because of the border all of the pixels at Y=0 are black in the font png, so where are these extra artefacts coming from?
  • I am very interested in this problem and its correction on 920XT.

    I try all the .fnt configuration (xoffset, xadvance, spacing, pading, ...): no good solution

    Currently, I continue to use sdk 1.2.1.
  • OK, this is just getting ridiculous. I have now released a number of versions of segment since the first reported issue and tweaked the font in each, it now has a pixel border of padding around each side and yet it still continues to render incorrectly on the 920xt hardware:

    Example of v2.1.0 courtesy of user -fifithereal-

    It also appears that the icon for activity in the lower right corner is corrupted - all of the icons are in a single font and defined the same way and yet the others are rendering correctly. Again, there are no issues with the icons in the simulator or on other types of hardware, it appears to be restricted to the 920xt.


    Are you saying that for 920xt in the simulator it displays correctly?
    Just want to confirm that the problem is just on the 920xt hardware.

    I am interested in doing an update for some of my watchfaces, but a bit cautious if it affects hardware and there is no way to detect the anomalies before.
  • For me, it's exactly that.
    Simulator is ok
    920xt is inconsistence
  • I saw these issues on the 920 device itself but like you not the simulator.

    Clearly the simulator is not simulating the device! Perhaps the simulator needs to be re-aligned to how the firmware on the device works with the font files.

    Secondly I had to manually change all my font files (12 of them) to fix the rendering issues. The slightly alarming thing is that although the fonts render correctly on my 920, I have had a LOT of users reporting the fonts arent rendering correctly on their 920 and other devices.

    Garmin - what is happening with regards this issue?

    Thank you!
  • Weirdly a user reports that "Sunday" is rendered fine but "Saturday" is rendered as a managed mess for the "Saturda" but but the y is OK

    How come the S and a charcters are rendered correcly for Sunday but not for Saturday!?

    EH!? I think this is a 920 firmware bug!

    GARMIN CAN YOU PLEASE TEST!?