Bike: 80 minutes, 0.4 miles. (I actually averaged 23 mph.)
T2: 902 hours, 13 miles.
Run: is correct!
W.T.F? I cleared the previous activity. Watch read zero. I started it when the horn went off. I didn’t use auto multisport. I don’t trust it. I consistently lose cadence and speed sensor in multisport. (Doesn’t happen in plain vanilla bike mode.) I manually switched sports.
I understand if I were in run mode and lost GPS and the distance came up short. Should not happen on the bike because my speed/cadence sensor was working. I never lost cadence. Also the real time data as seen on the screen was good throughout the race. It kept time and speed and HR and distance correctly, but recorded the activity all wrong?
How the hell is a problem like that one EVEN POSSIBLE? That’s an epic firmware/software fuckup. Epic.
Bike: 80 minutes, 0.4 miles. (I actually averaged 23 mph.)
T2: 902 hours, 13 miles.
Run: is correct!
W.T.F? I cleared the previous activity. Watch read zero. I started it when the horn went off. I didn’t use auto multisport. I don’t trust it. I consistently lose cadence and speed sensor in multisport. (Doesn’t happen in plain vanilla bike mode.) I manually switched sports.
I understand if I were in run mode and lost GPS and the distance came up short. Should not happen on the bike because my speed/cadence sensor was working. I never lost cadence. Also the real time data as seen on the screen was good throughout the race. It kept time and speed and HR and distance correctly, but recorded the activity all wrong?
How the hell is a problem like that one EVEN POSSIBLE? That’s an epic firmware/software fuckup. Epic.
That is messed up (but on the bright side, your swim speed is awesome). I know that T1 and T2 were long, but that data is ridiculous.
My Suunto on my wrist, started it in multisport mode when I entered the water and warmed up, then hit start at the horn. I had 2000 yards swim (might have included the warm-up yards), no bike data because my cadence sensor crapped the bed so both Suunto and bike garmin were wrong, and had a 5.93 for the run so 1/4 mile short (not including the ridiculously long transitions).
On the bright side, your cumulative yearly mileage on Strava just got a nice boost!
But seriously, did anyone actually get good data on the distances of the race? Every single split seemed off by a decent margin (based on times) for the athletes I know. Swim seemed long, bike seemed REALLY short, and run seemed a tad short.
That is so funny - because as we were walking back to transition, we were chatting to a guy from Yugoslavia (sic) and he had similar numbers - must have been a long day eh?
(Or, link to a GC activity files, be sure to set activity to public using the little lock icon)
Let me check…
Spurious lines shooting off from the course. GPS signal loss? It doesn’t explain the times though. Why on Earth would it think I was racing for hundreds of hours?
Wait. Huh? On the map view on the watch the data appears in small text to the right of the map. And that data appears correct! Then when I go out of the map back to the lap view the data there is miraculously correct. When I step to the next lap, and then go back to this lap, then yet again the data is wrong.
On the bright side, your cumulative yearly mileage on Strava just got a nice boost!
But seriously, did anyone actually get good data on the distances of the race? Every single split seemed off by a decent margin (based on times) for the athletes I know. Swim seemed long, bike seemed REALLY short, and run seemed a tad short.
With transitions that long, I think a slightly short run is justified. Bike was definitely short. I got something around 23.5. Others, iirc, got high 22s.
