@withManish said: The map gets disabled on the watch. The map is already downloaded on the watch; you are just showing me where I am. This does not make any sense to disable map display. The map is enabled only in Performance mode. According to discussions that I’ve seen in this forum, the cost of preloading loading map segments from the storage is such that if it was enabled in modes other than Performance, the battery use would still be almost the same as in Performance mode. @withManish said: I don’t understand why I am forced to use a performance mood every single time, even though I don’t need to. Honestly I don’t understand why anyone would want to use a battery mode other than Performance. We are talking about 30 hours in Performance mode vs. 40 in Endurance. For everyday training that doesn’t make much difference because the majority of the battery use comes from the smartwatch usage outside of activity, which comes close to roughly 10% per day with raise to wake display activation. Let’s just assume that someone trains 1 hour per day with GPS. When using Performance mode, in a week 70% of use will come smartphone mode and 23% from recording activities. And if someone uses Endurance mode - 17% of use would be from recording activities. So at the end, it is a difference of 93% vs. 87% - not a significant difference at all. When I used Race S I didn’t bother and just used the Performance mode every single time. The only case when I’d consider Endurance mode is if I was doing a 100 mile ultramarathon with Race S.

First of - thanks to Suunto for opening up the possibility to enrich their marvelous watch lines with features that many users have been missing! It is always amazing to see where the combination of ingenuity and a (somewhat) open development platform takes us. Being a road-runner with some sort of ambition to optimize races I have been missing a race pacer that allows for freely defining pace segments. The races I have participated in (Gothenburg area, Sweden) are quite often pretty hilly and I have found that I waste energy in the wrong places and therefore needed an app that could provide some guidance. The requirements were pretty close to “RaceWarden Pacer” - but I was missing the possibility to define the distance for the various segments of the race. And. With age comes poor eyesight, so I needed BIG (and clear) numbers to control the pace. The logic/thinking: You define your pacing strategy based on the elevation profile of the race and potentially other factors - this is all done outside of the app. Example from “Göteborgsvarvet” where I decided to try Jack Daniels’ Running Formula which roughly translates to -8s/km/%-gradient (uphill) and +5s/km/%-gradient (downhill). But that is outside the app, just the background to the pacing strategy. [image: 1780157300180-2026-05-18_19-54-08.png] The pacing strategy is pushed to the app through user defined app settings: Segment Distances (km or mile): 2.45 1.79 1.36 1.36 6.59 7.8 Segment paces (min/km or min/mile): 5:18 5:03 5:37 4:55 5:12 5:14 (Is it possible to have two input fields in app settings?) With the user input the total race length is calculated by summation of the Segment Distances (21,35km), and overall race target time (1:51:26) as well as target pace (general) is also calculated. Then comes the tricky part. What is really needed / what can be displayed to help pacing (remember: poor eyesight)? I removed heart rate as I have found it does not work (for me) during races, and landed in the following configuration: [image: 1780125397727-2026-05-30_00-06-13.png] Segment Target Pace: Derived from user input and displayed once a segment is recognized/completed. In essence this is a pretty static value, that only changed when a segment is completed. Segment Pace: Calculated. Similar to Lap Pace but utilizes the user defined Segment Distances/Segment paces, so it’s dynamic and updates as you run. Total Seconds ahead/behind Race Plan: Defined as the deviation between race plan and completed distance/time; naturally dynamic. Needed Pace: Based on initial user input finishing time and total race length are calculated. This is the pace needed for the remaining part of the race to reach the target What would you see as missing? The remaining challenges: I would like to have (I believe) at least some indication on heart rate - but I am not able to get the standard zone gauge to work and lack the skills to create one by myself with the canvas mysteries Compatibility - I believe maximizing fonts will be problematic for smaller watches but have not really had the energy to investigate what/how to make sure it works also for smaller displays Contrast - to me it seems yellow offers the best contrast, but is it just my eyes or a more common phenomenon? All input welcome! (unfortunately it seems my application for the partner development has got lost in the mail, as I applied many weeks ago) Also - I used the app (very successfully) during a recent race!

There aren’t many women in the room! I’m Marie-Lise, a French-speaking Canadian woman from Quebec City, almost 50 years old, trying to stay in shape and maintain a bit of performance in a busy family and professional life. I’m a multisport enthusiast: snow pentathlon, ski touring, hiking, running, cycling, etc. Username: MLM