Well I tried the Lap Pace set up this morning on my 16km run. It was a disaster. One minute it’s showing at 5.40 then a few mtrs later it was saying 5.05, then 5.20. One lap had me at 5.45 but when the lap ticked over a few seconds later it said I’d run a 4.40 for that lap! My run ended up at 5.26 av
I was under some trees for some of it but there aren’t any leaves on them and that was only for about 5km.
Confused!
You need lap avg pace.
Doh! I knew I’d get it wrong haha
No, lap pace is the right terminology for Garmin. That’s what lap average pace is. I just checked.
No idea what went wrong for @FatPom, as by the very nature of the metric, its impossible for it to output an average lap pace different immediately before what it then shows you as the lap time for that autolap. In all the years with Garmin, where I have always used lap pace, that has never once happened 
hmm, I’ll try again tomorrow.
Clearly not impossible, because that’s exactly what it did. Just checked my laps on my GC account and none of them were recorded as 4.40, so it gets even stranger. Maybe Winchester has its own GPB Bermuda Triangle thing going on? 
Yeah, wasn’t doubting you. Was just saying it was super weird. The volatility you describe can happen at the start of a new lap, but my experience is always pretty good stability 30s or so into a new lap.
Yeah just added a bit to my post. The stats don’t show a 4.40 at all. I’ll give it another go tomorrow.
Lap pace can be a bit flakey at the very start of each lap as it’s basically instantaneous pace at that point. It should get more and more stable as the lap goes on. Did you look at it in the first few seconds of the lap to see the changes you did?
yeah I think mostly the beginning and end of laps.
The end should be fine as it will have stabilised but I’d probably give it 30 secs or so at the beginning to settle down.
How are people now finding the 945?
@jeffb I think you definitely have one? Are the early release issues with OW swimming etc now all fixed? I’ve read some stuff on excessive battery drain with a more recent update? But I know the positive reports often get a lot less traction than the negative ones.
Wiggle are doing discount on them this week - and my 920 has randomly started not connecting to my HR monitor. It connects to all other sensors immediately, but not the HR monitor I use for cycling. The Edge 530 and my phone on trainerroad, all connect fine
Following
I ended up buying. A friend of mine in my club was able to say its now working without the early issues. And surprisingly the wiggle loyalty bonus was working on the device. So I got nearly 20% off. 5% with my loyalty bonus and then a further 15% off that with the code I got emailed.
If anyone has the wiggle 12% loyalty bonus, they might be in for a bargain
What was the 15% discount for?
I got an email from wiggle with a personal code to “upgrade my Garmin”. I got it on two of the accounts I have registered with them. I’m not going to use the second one, so could likely share
I went from 910 to 945 and it’s been a great upgrade. My points from another thread:
Do you use a HRM strap at all? I have a 935 and wouldn’t rely on the wrist hr during activity, particularly run. Also, I think it needs the hrm run to calculate running power, although I find running power to be of only passing interest.
Wrist HR during swim would be a nice upgrade, the rest (over the 935) I can live without.
Yeah I use the strap for running and also harder bike sessions (for bike commutes the wrist HR seems reliable enough). I forgot my strap on a run once and used the wrist HR and it was about 10-15 BPM higher than normal.
I find with the 935, slower runs seems to show high HR, while on fast runs OHR is pretty close to me chest strap. Yesterday I ran 4 reps of 2km @ 5m/km and 1km @ 4m/km… I forgot my chest strap, so was relying on OHR, for the first 2 reps it showed a higher HR on the slower intervals, then seemed to settle down