[image: 1778681741189-img_7822.png] [image: 1778681761355-img_7821.png]

Just want to chime in that I also came across this today while preparing for an upcoming mountain trail 100k race. This is my first race using a Suunto watch instead of COROS or Garmin. It’s disappointing to: a.) not have an elevation profile in Suunto when importing the official GPX file (from UltraPacer, in this case) b.) not be able to use turn-by-turn guidance With COROS and Garmin, both of these things are non-issues for their users. I understand the bits about the GPX file not containing the elevation data itself, how I can find a workaround, etc., but this should not be my problem, and it never was before. And I don’t know of any fix to get myself turn-by-turn guidance, which would be great when running in the mountains at night, other than to spend hours completely recreating the route myself.

[image: 1778141561617-img_6711.jpeg]

@pavel.samokha said in problem with suunto Plus!: @DRezvoff OK, send logs and let me know your username/email in DM here. I cannot promise, but I’ll try to ask someone to take a look into the problem Hi! How to find application logs?

Update after field test (May 2nd): I have now confirmed that the real-time ZoneSense gauge on the watch itself (Vertical 2 / firmware 2.53.42) frequently shows Yellow (Anaerobic) during an easy run at avg 122 bpm — well below my Aerobic threshold (S1 = 130 bpm). This rules out a pure app-side recalculation bug. The issue appears to originate in the firmware 2.53.42 DDFA computation, which was the first version to include ZoneSense as a native function on Vertical 2. The app 3.9.1 seems to faithfully reflect these erroneous watch-side values, whereas the previous app version was apparently applying post-sync correction/smoothing that masked the problem.

@VoiGAS said in SA beta 3.8.1: Strange that there are different translations between the operating systems Yes, indeed. I always wondered why.

@Bigb0zz Thank you! I made two new attempts and I suppose that the problem is linked to a corrupted track I tried to upload. Thank you for the attention and help.

Too soon to celebrate. It’s still all duplicated. Great job, Suunto. Two updates and no improvement 🥺🥺🥺

@2b2bff said in [iOS 3.9.0] Speed details for a biking activity: @Egika that’s English, mate… haha, it was late and I did no realize, that my app was set to English… Will report it

@2b2bff me on iOS as well. Let’s see what Suunto says.

@suzzlo ups, no, you’re right, the plan is again the same as before the changes, I hadn’t seen it.

@Tieutieu said in Suunto app Beta test: Chech out there : test flight update link beta ios Thanks, invitation link what was published in this thread resolved it.

Would also love to see this. Coming from a different sports watch brand, small stuff like this is quite annoying.

@Egika Still “Jetzt sofort” in 3.9.0…