When multiple courses share a common part, the profile at the bottom of the minima is not always showing your selected course.
That is correct. Not a bug, just the design.
Iâd argue that itâs a bug if youâve selected a route to ride (and havenât manually turned off that route), since Zwift knows where youâre going and should be able to show the correct profile.
But itâs been like this forever, so I canât see it being fixed any time soon
2 Likes
Well, technically speaking, itâs not a âbugâ, since it is functioning as intended. Could the functionality be improved, though? Most certainly. This, of course, would also mean more âassetsâ to load to the game if each route has itâs own profile to show in the mini-map. And what happens if/when you make a manual turn?
The elevation profile only shows the road you are currently on, not the profile of the route you have selected. You will notice it changes when you turn at an intersection.
So the gradient graph in London isnât buggy either then, since someone may well have intended the graph to go off the screen, and thatâs certainly how the code has been written?
1 Like
No Steve London is different, it used to be correct. But the other profiles has been like that since Zwift came out of beta. I would guess there is one profile that is in the correct order in every world, but I have not tested it.
Zwift show the profile of the road segment you are currently on it does not look at what the next section will be.
It would be nice, but I think that will just pull even more CPU resources.
Itâs already using CPU resources to update that profile as you gradually move along it. It would be a fairly trivial task to piece together the correct sections of profile for the route instead of just assuming particular different turns. It already redraws the profile at some turns anyway (often incorrectly).
Itâs a very confusing thing for new Zwifters in particular.
This really isnât a difficult task, but of course we all know how seemingly trivial bugs donât see to ever get fixed (e.g. London gradient graph), presumably due to the code concerned being a nightmare and no-one dares to touch it.
2 Likes
I would not say trivial. To do it correctly you will need every route section in both directions and then have Zwift look forward.
But it is definitely not impossible.
Is it not? You need current route and section, already have these of course. Then you just need the next connection sections and check which section is in the selected route. I donât see how you would need all sections in all directions, unless Zwift is made up of sections that are in no way linked to eachother. Of course around many intersections it gets more difficult but looking ahead one intersection is a small section check.
Not at all what I said. Thatâs definitely a bug. It used to work correctly, even, but was âbrokenâ at some point. The terrain profile in the mini-map has always worked that way. It appears that there are, effectively a few routes with their profiles set up in the game, and when you move from one to another the displayed profile changes. If you stay on one of the âpre-programmedâ routes, though, it would actually be correct for your entire ride. (I think Hilly Route is one of these, for example.)
Zwift is made out of sections, I am not 100% sure how they are defined but what I have seen is there is at least one section between every turn. That is how you can turn in random directions.
This is most annoying in France when ven-top means everything else is completely useless.
3 Likes
This basic course profile confused me for so long, especially when my location pointer started going in the opposite direction. At that point I just realized I had no idea what it was actually trying to represent and gave up trying to understand it.
Iâve always chosen specific routes to ride, so never just free-rode, so it was inconceivable that this gradient profile was anything other than the gradient profile of the course I specifically selected. Once I realized it wasnât, then it just became useless to me since I can no longer trust it to actually show what is coming up longer term even though the game definitely knows which sections I intend to run unless I override my course selection.
I have no idea how this can be the intended design, I actually donât know what it currently shows specifically, since it seems to span multiple segments, what actual segments is it showing? Why does it go in both directions? Who finds this exact design useful?
I figured it out the first time I did a route going up the Epic KOM, burned all my matches to get to the KOM banner, thought I was done climbing per the elevation profile, and then turned up the radio tower climb⌠That was not a surprise I was ready for that day!
I posted recently separately focusing on the âRoule Ma Pouleâ that Zwift used in Tour de Zwift Defect: Minimap and KOM/sprint incorrect, even in events since it so super-annoying to have the Ventoux KOM profile almost the entire time.
I donât get why you canât just click on it to choose the scale you want like you can with the actual map bit.