Ascent remaining

Only me having this issue? 

Same here. It's completely useless.

I have noticed if you are routed on trails the ascent remaining is way wrong.  We rode 20 miles on the KatyTrail ( it is dead flat ) and it showed 1500fr remaining  On other rides it seems to be correct.

Not uncommon.  As best I can tell the when the unit computes ascent remaining, it is doing it off of a crude elevation topo in its database.  I say crude because to have detailed topo data on every point along a road or trail would make a much bigger maps storage database than they hve memory for in the unit.  I live in the Colorado Rocky Mountains, trails and road often can be in a canyon or on an edge that has a dropoff.  If the road or trail line is slightly off, that can look like it climbs the side of the canyon wall and back down (just being off by 10 feet) or vice verse.  The unit calculates that into the total ascent.  After you have passed that point in the route, that spot is behind you and not in the calculation anymore.  So by the end of the ride you are down to 0 of these left and the elevations match.

Just a reality of the level of detail the system can work with.  

If you are on a dead flat road, one would hope this is not an issue, but who knows what's in their database.

I'm guessing the course has come from Garmin Connect?

There is a know issue that is working in that the elevation gain shown on the course in GC and the value seen once exported do not match.The error is being introduced as part of the FIT file generation that GC does when it builds a course to send to your device. 

Yes, it comes from GC. And the total ascent for the course is correct, only the remaining is from the beginning wrong. I think you are right. Hope this will be fixed soon. 

Still no fix. Garmin is not really caring about customers. Sorry, but ascent is one of the main information when doing a mountain bike tour. 

Any update on this? I've seen a a couple of SW releases including 6.2 which says "Fixed issue with ascent accumulation." yet this issue remains. 

I have an IQ app called Elevation + which uses a full width field and has 3 fields within the full width.  It also has 2 more displays ( panes ) to make the total fields 9.  It has Accumulated ascent, descent, elevation, ascent minus descent, heading, course total ascent, course total descent, remaining ascent ( course ascent minus total ascent ) and remaining descent ( course descent minus total descent ).  You can enter the last course ascent and descent  values on the IQ settings before each ride.  You can select which fields display in which panes and the order.  You can control how many seconds each pane is displayed and you can force it to change panes by tapping the screen on the field.  The total ascent and descent will replace the course ascent and descent when the activity is saved.  I use these values the next time I do the same course.

I have noticed that the garmin ascent remaining is always a lot more than the total ascent and adjusts downward by more than the total ascent as the ride progresses .

Ronnie

Still not fixed in version 6.2. My edge shows a remaining ascent at least 3 times bigger than the real remaining ascent of the route...