• Replies 4 replies
  • Subscribers 16 subscribers
  • Views 729 views
  • Users 0 members are here
Options
Related

Epix Gen 2 glance view position and size

tonix76
over 3 years ago

Dear Garmin team,

Could you please fix the glance view position and size in the simulator.json file for the epix2? In a real devive the glance views displays fine, but in the Garmin simulator the glance view canvas is not properly centered.

Many thanks in advance!

Toni.

  • over 3 years ago

    Hi Jim.

    Thanks for your quick response. I already read that thread searching for a similar issue, but I've verified that if i manually modify the glance view width/height & x/y data in the epix2 simulator.json file then I can get the closer view to the real device.

    By comparing the simulator.json data (for the glance view) with other simulator.json files (fenix6xpro, fenix7x, etc.) I guess that it's clear that the issue is in the simulator.json file. I do not know how Garmin computers the final correct values so this is why I opened this thead.

    Greetings,

    Toni.

  • over 3 years ago in reply to tonix76

    In general you don't want to modify things in devices.  The time stamp on your file can be newer than the official Garmin update.  BTW, there is actually a lesser issue with the venu2

  • over 3 years ago in reply to jim_m_58

    Yes I agree, I do not want to modify such things. I decided to do it due to the glance view was working fine in all the other devices in the simulator, and working fine in the epix2 real devices, and also in my Fenix 6X Pro, and the code is equivalent. So I decided to modified the simulator.json and verified that I could get it work properly in the Garmin simulator

    On the other hand, the timestamp of the simulator.json file correspondes to the time when you've downloaded the device definition. I removed the epix2 device by usgind the SDK device manager, then checked that the epix2 dir has been removed, then re-dowloaded the Garmin device definition and then checked and tested again.

    I can live with this issue. I've just shared to help other developers or to point out the issue to be fixed.