Software Update 2.43.8/.12 (2025 Q2)

Egika

@Inge-Nallsson as the .12 hofix was addressing steps, resources and sleep representation, it is likely that this was solved now. Or did it happen already with the 12?

Inge Nallsson

@Egika said in Software Update 2.43.8/.12 (2025 Q2):

did it happen already with the 12?

These phantom steps came with a bootup on 2.43.12 But I have no idea if such a resource-less (no data/history) watch start exhibited the same error on previous FW versions.

GiPFELKiND

@GiPFELKiND okay 2 likes for this @Dimitrios-Kanellopoulos @pavel.samokha Can someone share a link please with Firmware 2.37.48 or private Message have a great weekend

Pavlas

@sky-runner I don’t understand the change either. I’ve mentioned it before. I found the maps beautifully clear. But now zooming in 100, 50 and 25 meters is very ugly and opaque. Especially in the city. It’s not too bad on the amoled display, but I don’t like it at all on the Vertical

Tieutieu

@Pavlas I agree under 100m it’s a bit ugly, but at 100m zoom and above, I find it much easier for guiding.

MirkoP

@pavel.samokha
Not available in Italy

Dimitrios Kanellopoulos

I find the new maps also strange. Asking for you why this happened and if we can do something in the meantime.

Dimitrios Kanellopoulos

@sky-runner as usual I understand your frustrations but,

Remarks like : has anyone who does trail running tested this ?

They don’t belong here. I am sure it’s not intended.

Anyways I agree with you so we will get to the bottom of this.

Fenr1r

@Dimitrios-Kanellopoulos Could you also remind the map people (if such exist) about contour lines above 200m zoom for those areas still missing them, please?

Egika

@Fenr1r rest assured, they are aware!

duffman19

@Dimitrios-Kanellopoulos said in Software Update 2.43.8/.12 (2025 Q2):

I find the new maps also strange. Asking for you why this happened and if we can do something in the meantime.

This seems to be an issue with OSM tag priorities. I don’t recall exactly how they appeared before the update, but as @sky-runner said, the zoom level renderings definitely haven’t improved.

On the current software, trails (footpaths, sidewalks, etc.) disappear at the 500m level. Service roads (driveways, parking lanes, alleyways, etc.) disappear at the 1.00km level. And residential roads disappear at the 2.00km level.

I think this is backwards for an outdoor, trail-focused watch. I’d much rather be able to see trails at larger zoom distances than driveways and side streets. And contour lines as well.

GiPFELKiND

@Egika since 2 years

kriskus

@Artus-Diver (@ or anyone else swimming a lot) Can anyone who uses their watch for swimming confirm if there are any improvements to the swim distance / style detection algorithm? And how the swim drills app works?

Miroslava

@kriskus @Artus-Diver
I’m also very interested in this, as I won’t be able to get into the pool until next week. I’m mainly interested in whether it calculates the pool lengths correctly breastrokes. Ďakujeme

Stavrogin

Did I read somewhere that there were going to be new watch faces coming out soon not attached to the update, but following soon after?

larrybbaker

I’m seeing the issue with the HR graph not working in the watch also. Data sent to the app seems fine but the watch only shows current HR.

ElectronBadger

@ElectronBadger said in Software Update 2.43.8/.12 (2025 Q2):

@pavel.samokha said in Software Update 2.43.8/.12 (2025 Q2):

@TrailEyes yes, hotfix should come. 2.43.12 probably

Installed 2.43.12 on my SV. The problem with manual laps not being displayed properly is still there

My mistake, sorry. After installing the update, settings for activities got reset to defaults and autolapse became active. When I disabled autolapse for the activity, manual lapses are displayed correctly.

sky-runner

@duffman19 said in Software Update 2.43.8/.12 (2025 Q2):

On the current software, trails (footpaths, sidewalks, etc.) disappear at the 500m level. Service roads (driveways, parking lanes, alleyways, etc.) disappear at the 1.00km level. And residential roads disappear at the 2.00km level.

It is even worse in imperial units as trails disappear at the 0.2 mile level, which is just 320 meters.

@Dimitrios-Kanellopoulos, I apologize that I let some of my frustration through, but nevertheless this should have been caught during beta testing.

Since I keep finding issues, maybe I should apply to be a beta tester. I am a very experienced software developer myself with keen attention to details. I’ve noticed this issue the very first time I used maps on a trail run. I have two Suunto watches (Race and Race S). I offer to use one of them for early beta testing. Please sign me in or let me know how to apply!

seanvk

No problems with either update on my Suunto Vertical. Lots of hiking with it of planned routes. Sleep data good. Anyway. Appreciated these regular updates from Suunto.

thanasis

It seems to me that something has changed on the altitude measurement.
for similar paths and knows tracks, i get lower altitude measurements despite having similar elevation gain (ascent descent is quite ok). At ±600m altitude with 170m ascent I still get similarish ascent but with significantly lower altitude measurements! the map lines indicate that previous measurements where right , but the recent ones are not (see below)
current shows

map