ETA calculated completely wrong mostly, not always, so it is not reliable.

Using ETA for navigation does not always work properly. It usually shows some intermediate turning point, but is not always the same. Using the course function from the Expiore app shows the next turning point as ETA, which should be showed by ETA at Next and not by ETA. The same is true for ETE, which als shows ETE at Next instead of ETE. Using the Navigate function and sync it with the Fenix 8, shows sometimes ETA at Next and later on sometimes correctly ETA, depending on the rest of the track to Destination. Hope this will be fixed soon as for Navigation this is a pretty important function which should be reliable. 

  • neither to me but I took some activities and did a reverse calculation on the flat speed needed to match the final moving time and created 3 "profiles".

    I wish I could save and apply those profiles on Plotaroute Smiley

  • I have been using plotaoute for years and ETA has always worked well with previous Fenix. With the 8 series it does not work, it shows the estimated time of arrival to the next point also in the data field of the end point. Is this only me?

  • I have looked at plotaroute, it looks realy good, much better then strava or komoot for trailrunning (especially with that flat pace, i have drawn a route I ran and the estimated pace is really close),

    Do you know if is necessary to put it manually in the Newfiles folder or does the sync (with the premium version) works also? 

  • in theory, sync should work (it sends the track to Garmin connect) but I don't know if GC processes the track with their algorithms for pace, elevation, etc... So I would recommend the good old manual way :)

  • If you intend having "custom waypoints"/"course points"/"cuepoints" , you named, you have to put the file manually once Plotaroute does not synch them even with Premium account.

    I wish they do it ..

    ps: Strava does synch custom waypoints but have a small set and no turns symbols (left, rgiht, etc) at all... 

  • Same for me.

    ETA was working perfectly with my previous fenix7 but on my enduro3, the watch gets the final arrival point and intermediate waypoints mixed up. It is namely the case when i am going uphill, ETA is the time i get to the summit of the automatically identified uphill as opposed to the time of the predicted final arrival.

    This seems absolutely easy to solve and hope Garmin will eventually pay attention to customer request and comments. 

  • I understand the problem for ETA at next, but what about simple ETA? Why does not the data field ETA only focuses on arrival final point, as opposed to intermediate waypoints? (For example the summit of an automatically identified uphill).