Lately, I’ve noticed my cursor in the elevation profile doesn’t ascend, but rather continues along the bottom of the of the profile map. Also, the more specific elevation profile in the upper right will show the percentage of grade change no problem, but the diagonal line will eventually disappear up out of the screen so that all that’s left is a black box. Here’s a resulting picture (wish I had taken a “before” pic):
You can see my cursor near the KOM, kind of hovering below the grade, and you can see there’s no elevation profile in the detail box in the upper right - just a percentage. Prior to this point, when I was just entering Box Hill, the detail box clearly showed the diagonal line representing the grade.
The other ride was an event that took place in Watopia. I did my warm-up in London, in a rather flat section, so I can’t really tell if the issue was a one-off, London, or random.
To date, London is the only place I witnessed such.
Noticed the same thing today, also on a london route (Surrey hills). Orange rider marker at the bottom doesn’t follow the incline of the profile. Also found the black elevation profile at the top seems to be absolute elevation. If you are at low elevation it is fine. As you climb, the profile keeps going up out of the box on top of the screen. When you descend low enough, it reappears.
yeah I raised this too - it is really annoying and makes planning the hills and knowing what is coming up really hard - i use that little gradient graph a lot on climbs
Seen this in both free rides and tonight’s Tour for All race - the minimap/elevation goes wrong on Keith Hill as per the images below. Orange rider icon doesn’t follow the hill profile silhouette on either the climb or descent, and the gradient indicator turns into a solid block that goes off the screen instead of showing the current/upcoming gradient.
I’ve also noticed this the last two days, Surrey Hills TfA ride this morning and London 8 free ride yesterday. Did not notice it on TfA Stage 4 short ride on Watopia.
I have this too, also only in London. I don’t ride London that often but it looks like it started around the same time as the first post (May) as it’s definitely been more than a few weeks. I’ve raised a ticket with support but they obviously know about it already.
I have seen this for some time now, but didn’t report in to support before yesterday.
The reply I got was to update my system, and that my MAC only had 4GB of ram, not 8GB ram as is the mimimum requirement. I find it hard to believe that has anything to do with it, and now I find this post which tells me I am not alone, and I doubt you all have the as little ram as my old MAC.
Do you still see the same bug? I only see it on London, not any any other map.
That is my understanding as well Dave. The fact that more users experience it, and we all have different system should tell them the same. It also only shows this graphic error on London.
Forst they told me about my RAM, and to update my system. I did check for updates and reported back doing so. In my response was also the link to this post to show them. The response I got from them was to download the log files to zwift for them in order to help me more……
Something tells me they are not reading my e-mails…. The error is in their code. Not any of ours hardware.
Is that what zwift have said is causing it? that is madness!
I used to work then broke, only happens in London and happens to everyone so how could it possibly be anything other than a fault with Zwift?
I think they are leaving it as it is specifically to annoy me as I raised this over a year ago now and for some reason it really bothers me (a lot more than it should!)
