First of - thanks to Suunto for opening up the possibility to enrich the marvelous watch lines with features that many users has been missing! It is always amazing to see where the combination of ingenuity and a 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 in have participated in (Gothenburg area, Sweden) are most often pretty hilly and I have found that I waste energy in the wrong places and therefore needed an app that could help. The requirements were pretty close to “RaceWarden Pacer” - but I was still 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 you pacing strategy based on profile of the race and potentially other factors - this is all done outside of the app. Example from “Göteborgsvarvet”: [image: 1780124719773-2026-05-18_19-54-08.png] The pacing strategy is pushed to the app through user defined app settings: Segment Distances (m): 2450 1790 1360 1360 6590 7800 Segment paces (s/km): 318 303 337 295 312 314 (Is it possible to have two input fields in app settings?) With the user input the total race length is calculated by adding the Segment Distances (21350m) and overall race target time (6686 seconds) 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 Segment Pace: Calculated. Similar to Lap Pace but utilizes the user defined Segment Distances/Segment paces Total Seconds ahead/behind Race Plan: Defined as the deviation between race plan and completed distance/time 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

Play stupid games, win stupid prizes xd [image: 1779993859607-catastrophicfailure.jpg] TIL: the Duktape JS heap is 133,120 bytes (~130 KB), shared across all loaded zapps. At last in S9PP that is. Learned this the hard way today — Constantin crashed my watch three times, once into a full firmware restore. I merged my three view templates into one to fix a button-lock bug during route navigation. Bad idea. Each template is ~30–45 KB; all three loaded simultaneously at onLoad = ~130 KB = 99.4% of the entire heap before ZoneSense even shows up. The system tries to recover by force-unloading the offending zapp, which then reloads, fills the heap again, repeat, until Duktape can’t allocate 1392 bytes and crashes: WRN UI_FRAMEWORK : JsTotMem 132296/133120 ERR APPLICATION : Zapp: releaseMemoryCb → Zapp 3: ReleaseMem -> unload [×3] ERR APPLICATION : Zapp: ReleaseMem -> None avail. ERR DUKTAPE : JSalloc:1392 [×11] ERR FAULT : A302:duktapeFunctionCombiner.cpp EVT BOOTLOOP : Bootloop detected, sysmode 5->17 Good to know: ≤ 30–40 KB per feature zapp, one template at a time. With ZoneSense (~30 KB) and Weather (~15 KB) running alongside, headroom is very tight. The watch is fine. I’ve reverted to the multi-template build. The original nav overlay bug is still open — if anyone’s solved the unload/type="lock" gap problem without blowing the heap, I’d love to hear it.