HR/ANT+ dropouts may be fixed with Sensor Version 5.8

Agreed this does seem better than before. Also from previous experience Garmin does seem to eventually get there. I got an Edge 800 right when it came out and it had a terrible issue with errant GPS data points(suddenly I became a tour de france rider and did 600 miles in a day.. it was amazing for my strava stats).. it took them a bit but they did eventually fix nagging issues.

Personally I wouldn't throw in the towel just as yet. Garmin seems to be making progress with it. I'm not happy they are there but love the VA3 enough to deal with these quirks until they get fixed. Also, at least my ride map appears accurate (no teleporting to other areas). And no, I don't work for Garmin.

Evidence from the sensor error log in the Garmin folder (SNS_ERR.TXT)
16 Sensor errors on 3/5 on version 5.50 vs 5 sensor errors on 3/7 on version 5.80 (This is what they look like).

Sensor Hub Reset, v580
03/07/18
23:34:01
6756,41581295
5885,41581923
6756,41582295
5885,41582923
6756,41583294

I'm also still seeing dropouts, heart rate seems to recover to the correct level quicker but still happening.
Can someone confirm my own limited test that dropouts only occur if using the workout feature? When I have started a run not using workouts I don't see dropouts but when I use workouts (which I do most of the time) I see dropouts.

Any sensor dropout improvements with software 3.40? Assuming no, but maybe an undocumented fix. I haven't been able to ride and test due to weather. Probably going to be a sensor hub update anyways.

Still getting drop outs with 3.40 and 5.80ciq.forums.garmin.com/.../1321352.png

Not to be "that guy who says Me Too!" but... me too! The conflict with the between the Ant+ devices and the oHRM do not hang the watch as badly as before but still result in the HR dropping to 80 (why 80 I have no idea) while the Cadence and Speed sensors reconnect. This does not occur if I use the Garmin chest HRM. Disappointed.

Even with a strap I'm still getting drops on speed/cadence occasionally. Not nearly as bad or as laggy but they are still there.

Unfortunately one more here. "Bike Indoor" gives me dropouts even with external Heart rate sensor. I have feeling that besides anything watch tries to use GPS (my calibrated height went from 102 meters to 352 meters). And while using GPS, internal heart rate sensor and connected to Speed and Cadence - overloads power source and drops all of it down.

Did a bike ride last night. Not sure if things were rolled back in software 3.40. Sensorhub is still 5.80 but the sensor drop issue is as bad as ever (even before the 3.30 and the sensorhub update). Still seeing a bunch of the oHR drops to 80 and sensor reconnects. Still seeing mystery teleporting in the GPS map. Looking at the sensor error log showed 12 sensor hub resets so pretty much confirms what I'm seeing when using. Will see if going back to an external heart rate strap helps anything but here we are 6 months after the product release. Frustrating!

It is definitely not fixed. Tonight's workout, On Board HR/ANT+ speed, 2 HR/Speed dropouts.

It seems to have something to do with the on board HR. It does not seem to happen when using a HR strap as Brontide tested. But who knows for sure.

That HR dropout is exactly what I'm getting with my VA3 with onboard HR though I'm not using any Ant+ sensors

The same here too...on everey 15 minute ride at least one dropout of cadence- and/or speedsensor. OHRM drops too. I got this to measure my rides and it doesn‘t really work. I even got some extra garmin branded sensors for my bike, thought that‘ll help.
If Garmin can‘t make it work properly why don‘t they find a way to interpolate the measured values so they would at least get close to reality? I know others can do so...ciq.forums.garmin.com/.../1324336.jpg