Acknowledged
9 months ago

Fenix 8 - Font Missing - BionicBold

Just picked up a Fenix 8 51mm today, tested my app and noticed that the fonts are not correct

The Fenix 8 51mm FW 11.60 can't find the BonicBold Font as is displaying my fallback font of RobotoRegular instead.

The screenshot below shows the same app running on the Simulator, Epix 2, and the Fenix 8 51mm. The Sim and Epix2 are clearly showing the same font (BionicBold)

There is also a difference in displayed font size as well. You will notice that everything on the Fenix 8 seems a little squashed together and the time at the top of the display has been clipped. Am I right in assuming that a vector font of size X should display as the same physical size on the watch regardless of the font selected ? (ie the RobotoRegular font is clealry larger than the BionicBold font given the same font size.

Rick
  • 9 months ago

    Looks like this is fixed in FW Version 11.87

  • 9 months ago

    Thanks for the report. I confirmed that this was removed in the latest device releases, but after talking with the device team it'll be restored on devices in a future release.

  • 9 months ago in reply to FlowState

    I'll give that a try - UX's are not my speciality. I had someone in the early days make a comment to the effect "great app except that i don't understand why pressing the down button increases the timer value, and, pressing up decreases it". In my mind pushing down was interating down the list of timer values which naturally was an ordered list starting with the lowest value. Made perfect sense to me Joy

  • 9 months ago

    Nice app btw. One suggestion - the bottom-left and bottom-right fields look like they’re upside down. As an end user I think it would be ideal if all 3 of the bottom fields appeared to be right-side up. (i.e. I would draw the bottom 3 fields as counter-clockwise radial text, starting from “west” to “east”.)

    The bottom half of Garmin’s own native radial map fields are upside down, so you’re in good company.

  • 9 months ago in reply to FlowState

    I saw that bug report late last night after troubleshooting an IQ error at startup with a customer who has a 955. It was working for him last week and now all of a sudden - IQ errors. In the meantime I'd released a new version so I'm pulling my hair out trying to work out what I might have broken. I saw that error report about 9:30pm and by 10:00pm my customer had sideloaded a new version and no more IQ errors. The font's don't look good, but at least he can continue to use the app while we work that out.