Instinct – 2.76 Beta Release

Hi having loaded the new Beta Firmware I am finding that the Instinct watch will still not navigate a course correctly, I have sent courses to the watch created in both the Explore App and Connect but when you select them to Navigate although the course line displays fine the watch will not move past the first marked point on the route, i.e none of the ETA, ETE, data boxes will display anything, the pointer whether set as Bearing or course will transition past the first point also the elevation line is flat when navigating a course, I have seen some other instinct users reporting the same issues on other parts of the forum.
Look forward to a firmware update to sort out this issue and am looking forward to testing out the navigation course feature properly once this function is working correctly.
Great that you are releasing Beta firmware for us, so far apart from the frustration of the navigate course not working all other features of the watch are great.

I use the Navigation a lot and in my own experience it works great. I do even find the ETA very accurate.
Your mileage may vary like they say.
Don't forget to push the upper right button to get ETA and ETE working. Sometimes it happen to me because I was launching the navigation, everything was set and the course appears (ETA and ETE were blank) on the screen but I forgot then to push the button to start it. Once pushed everything was OK.

I've had some troubles with navigation too.
I didn't contact Garmin support yet because I'm not sure how exactly to reproduce it. Next time I use it I will try to make screenshots and send it to Beta support.

So far here is what I noticed:
- elevation profile is working correctly at the beginning until it becomes (almost) flat at some point and never refresh anymore.
It seems that it can appear when getting back on course after being off course, but not every time...

- Explore courses with waypoints are not working correctly.
The bearing always points back to the start of the course. However if I create a course on the Instinct with the same waypoints imported from Explore then it works.
Waypoints on courses created with Garmin Connect are working but are not shown on the map.

- ETE and ETA are working. When I have a lot of ascent and descent it is really not accurate, but I don't consider this as being a bug (they are just estimations).
I prefer using remaining distance to next waypoint and would love to have a data field with remaining ascent to next waypoint.

mihailstacanov Yes those have VERY confusingly similar names!! However, those are two different groups of settings, one for "Navigation Settings" and one for "Navigate Settings".

Click down into the 1st one (Navigation on my English watch) and you'll see the configuration settings specific to the concept of Navigation that are in effect when you've enabled Navigation (whether in the Running App, the Hiking App, etc...or in this case the "Navigate" App)

Data screens (Map on/off, Elevation Plot, and 4 optional screens for Navigation-specific info),
Type (bearing or course),
and Alerts.

The 2nd option (Navigate) has the same set of settings you will see under other Activity Apps (running, hiking, walking, etc). This is where you configure the set of activity features common to other non-Navigate activities. The "Data Screens" sets the base set of data screens for this activity, and then the Navigation-specific data screens you've configured in the 1st group above would show up in the screen roll after this base set of screens.

As others are finding the main issue I am having is that any routes created in Explorer when navigated as a course on the unit the waypoints (Route Points) are not working correctly i.e. regardless of whether you have navigation set to course or bearing the bearing will only point to the first point and not move on, I am pressing the start button to start the recording of the navigation activity but this does not change the problem and I am still seeing no data in the ETA, ETA data boxes, otherwise loving the watch

The hourly chime/alert is odd. The font should be a lot bigger so you don't have to squint at the time. I'm not even sure that any screen is actually required just let the watch vibrate and chime.

Honestly, when I got my first Fenix (5), I was excited when I saw the Hourly Alert option. It reminded me of my Casio’s but then it become annoying, like I was 5 years old with the text of Hourly Alert popping up with no way to turn off the text, adjust the alert to just a beep, etc.

The Hourly Alert doesn’t need a “visual” reminder, just some sort of reminder. It should be changeable.

Honestly, when I got my first Fenix (5), I was excited when I saw the Hourly Alert option. It reminded me of my Casio’s but then it become annoying, like I was 5 years old with the text of Hourly Alert popping up with no way to turn off the text, adjust the alert to just a beep, etc.

The Hourly Alert doesn’t need a “visual” reminder, just some sort of reminder. It should be changeable.

Fully agree on this one.
Please make the hourly alert just a beep, vib, beep+vib, nothing... but with no other display announcement.

If i have to pick, I would prefer by a mile a beep, instead of vibration.

By the way, this beep should be independent of the configuration of the other tones in the watch.
For example, I don't like keys to make noise, or alarms to make noise (I only use vibration) but I'd love to have the hourly alert to beep.

@renhoek54 you’re right thanks, but in german the names are almost the same so it would be better to have different names for them