@sky-runner You’re right… ! I see it similarly… it is certainly very difficult not to overload the Maps… POI like water points would certainly be useful on larger zoom levels… But they don’t care about trash cans at all…

@EzioAuditore Do you know if raw RR-data is available from the firmware to allow you to do your own algoritms in a Suunto Plus app? Checked the Developer documentation, but could not see anything there.

@Steven-Hambleton These are the font sizes available. There is plenty of options for larger size … f-d-xxxl: data field font, 85px for medium, 155px for large display f-d-xxl: data field font, 65px for medium, 118px for large display f-d-xl: data field font, 57px for medium, 103px for large display f-d-l: data field font, 50px for medium, 91px for large display f-d-m: data field font, 42px for medium, 78px for large display f-d-s: data field font, 35px for medium, 65px for large display f-d-xs: data field font, 25px for medium, 46px for large display However there is not much room for fine tuning at the lower end. I tried rendering text on a canvas and displaying that. It works but takes a bit more effort to program.

@2b2bff I think there may be some confusion between the standard running dynamics already available on the watch and the additional metrics provided by the Suunto Spark. The Race series can already record metrics such as cadence and some running dynamics. However, one of the new metrics provided by the Suunto Spark is Ground Contact Time Balance (left/right balance), which shows how evenly you load your left and right foot while running. As far as I know, this specific metric is currently only supported within the Suunto ecosystem when using the Suunto Run. I have not seen it being recorded or displayed in the activity summary on the Race 2 yet. So if Ground Contact Time Balance is the data you’re looking for, that may be the reason it is missing rather than a connection problem between the Race 2 and the Spark.

@Łukasz-Szmigiel No I do not think so, there is only a single output in the manifest and three inputs. It seemed more load related as staggering canvas refreshes removed the problem. Worth nothing, on at least one occasion the canvas went black first then as a consequence of the load resulting in handling of that exception (we think) we got the pool full.

@Petr-Manek yep It is the same on Android. Although the help talks about total calories as well…

@matram the HRM DUAL got its last firmware a couple of years ago…

@Masnyband You need to have navigation turned on for LOOP to work… another option is to use my S+ aLOOP which doesn’t require that and is more accurate at detecting your position, preventing false positives.

@mssjk the water temperature. Or maybe I don’t understand your question…

This may not help you directly. But I posted around font positioning and differences in font rendering between watch and simulator here … https://forum.suunto.com/topic/15262/precise-alignment-of-text-and-numbers What you see is probably a result of this effect, where the app author maybe only tested on the simulator (the image you see on the web). There is nothing much you can do apart from pushing the developer. For the future more information about rendering differences between watch and simulator in the documentation would help developers get it right.

@dimitrios-kanellopoulos can this be related to the crashes. https://forum.suunto.com/topic/15193/activities-end-by-itself-when-the-destination-reached-message-appears

Hello, Is there any timeline for the next update. I experience the issue when backlight stays on even when it’s not activated in settings. This drains batterry extremelly fast. I did not find a way to replicate the issue - it happens from time to time. If anything is to be prioritized I suppose this is it Thank you