[Race - 2.53.42] Climb Guidance Segment Issue

[isazi]

@sky-runner it may be indeed Suunto App related, I will report it now.

[SergioB]

@isazi here below some other insights, if needed to reproduce/describe the issue.

I made some more tests today and find out that the first segment is always gray regardless of:

• The date of creation of the route (today or months ago)
• The sport mode used on the watch (trail running, trekking, etc)
• The grade of the first segment (cloud be uphill or downhill)
• The length of the first segment (could be few meters or some km)

Btw, thank you very much for reporting it!

[SamppaP]

@isazi I noticed the same on my Vertical 1 yesterday, never seen that before. First section was greyed out. It must indeed be app related because vertical 1 is still with the Q1 firmware.

[isazi]

@SamppaP yes I reported this, it seems unrelated to the watch but something that is happening with the app

[isazi]

I need the link to the activities and the planned routes to report this, send them to me in private.

[SergioB]

@isazi sent

[sky-runner]

@isazi, the above issue seems to be partially resolved but it is now broken in a different way.

On today’s run, the first climb segment showed as red for me on the overall climb profile, but when I attempted to zoom in the single segment view of Climb Guidance was just empty, meaning that it didn’t show any elevation profile at all. It still showed the remaining distance at the bottom.

This got resolved at the end of the first climb segment, after that zoomed in view (to individual climb /descent segments) worked correctly.

Also, what I have noticed is that zooming by distance did no longer work. I suspect this has something to do with the changes introduced in the latest firmware. There is now a new Climb Guidance settings menu inside Navigation settings which allows to select the default zoom mode - with Waypoint, Climb, and Distance options. I have rhe Waypoint options selected.

However on today’s run I didn’t have any waypoints on the route. I wonder if that contributed to the issue.

[MarTej_cz]

Ahoj, způsobuje to mobilní aplikace.
Každá 1. zóna mapy (červená, modrá, zelená, žlutá)
Zobrazí se jakou šedou.

Vytvořena nová trasa první zóna červená = šedá

Stejná trasa posunutý první bod na modrou = šedá

[isazi]

I reported this, it seems a backend/app issue of some kind because it affects watches with all firmware versions. Let me know if it happens again next week (it happened to me on Friday), but I believe it should be fixed soon.

[Squirrel]

@isazi said:

Let me know if it happens again next week

Still an issue today.

[isazi]

@Squirrel with a new route, or the same as last week?

[Squirrel]

@isazi said:

with a new route, or the same as last week?

Both, newly created and re-enabled old ones.

[SergioB]

@isazi said:

Let me know if it happens again next week

Don’t want to rush or be pushy, but this is still an issue as of today. If you need more logs or some particular tests, I’d be happy to help

[sky-runner]

@SergioB Yes, can confirm. I created a new route on Sunday and the first climb segment was grey. Also, once I was past that first segment, it disappeared from the overall profile - the route profile showed on the watch as if it started in the middle and I could not zoom out to full profile.

The official UTMB route downloaded from the race website has this issue too.

[isazi]

@sky-runner I asked again

[sky-runner]

@isazi Yep, I have just tried loading the official UTMB course again , and the issue persists:

Also, when zooming in the climb guidance doesn’t work. In my experience that applies only to the first climb segment, so I should be ok

[isazi]

I pasted your comment, and a link to your post, in the Suunto’s field testing chat. Good luck for tomorrow!

[isazi]

Too late for UTMB, but this (as guessed) it was an App and not a firmware issue. It has been fixed, not sure when everyone will get the next App version.

[SamppaP]

Android beta 6.13.6 is out and this issue seems to be fixed now. At least works now on my Vertical 1

[SergioB]

I’m also on beta (Android), and I can confirm it seems to be solved on my Race 1