New update! (4.3.6) - offroad waypoints
-
@Corjan-Meijerink said in New update! (4.3.6) - offroad waypoints:
No not really
Starting online and then going offline won't work result in issues.Thanks for this correction. It is difficult (for me ) to understand that a track that has already been cached is being disregarded when a route (not track!) to the nearest trackpoint is calculated (which probably should not be done if recalculation is disabled anyway). Especially, like you mentioned to @Martin-Wilcke, the white line (thus the original track in this case) is not changing. I am clearly missing something
-
I certainly haven't completely understood everything yet, but I know how track/route-as-track navigation basically works. If you like, we can share our thoughts.
Here is a good example (posted initially by @UwB), the "Maira-Stura Kammstrasse" in the Alps:
https://www.myrouteapp.com/en/social/route/10444583?mode=share
The part between VP 2 and 5 is routable with OSM/TT, but not with HERE:
The route is stored internally in MRA so that the calculated path is completely modelled (I don't know how this works technically; it's probably similar to Basecamp with hidden SPs).
In MRA NN, the route is therefore displayed in its original shape both in the preview and after opening.
When it is started for "route-as-track" navigation, it is treated as a track and is not recalculated - not at the beginning or during navigation (white line).
However, a new route (blue line) is calculated, which follows the track as closely as possible. If the route deviates too far from the track, it is displayed in this area as the crow flies, and no information (turn instructions, ETAs, distances) is shown during navigation.
I suspect the issues discussed here arise when you rejoin the route at VP5. The actual path does not have to be re-determined in terms of "re-routing", but something may have to be "re-calculated" to show the adjusted ETAs and distances (and maybe turn instructions as well) - even if "auto-recalc" is turned off.
Do you agree so far? What are your thoughts?
-
@Corjan-Meijerink said in New update! (4.3.6) - offroad waypoints:
Fixed issue with BMW Carpe Iter controller
@Corjan-Meijerink Which issues exactly did you fix?
Because there where a few. The extra bar-buttons didn"t react properly and trying to go trough the menu the [ENTER] by moving the wonderwheel to the right didn't work.
Neverteless i still am impressed by al the updates and improvements you guys make.
-
Manual day / night changes from CarPlay / Android Auto changed the base map style incorrectly
Thank you for fixing this! It eliminates an annoying bug I encountered numerous times. And I can confirm this is no longer the case.
-
@Corjan-Meijerink Today was a test drive day, using Android Auto. When I pauzed the route, because of a fuel stop and the system came back on line The scree of Android Auto didn't show the map any more. The directions, speed and ETA were displayed. The audio was still working. I had to reboot the system to get the map visible again.
-
@Martin-Wilcke sounds correct indeed! Why exactly a straight line is drawn between 2 and 5 is a mystery to me. It should approach the track where possible.
My guess is that HERE really does not have a any suitable road in that area causing it to not calculate anything in that area.When rejoining at 5, it will all work as expected again and you can indeed manually follow the white line.
-
-
@Martin-Wilcke, like Corjan already stated, it sounds about right. I don't think however this has to do with the online/offline track issue. We should probably keep this thread on-topic though.
-
@Corjan-Meijerink This would be great if those features are working now. If have contacted you earlier with these little mallfunction.
-
@Con-Hennekens said in New update! (4.3.6) - offroad waypoints:
I don't think however this has to do with the online/offline track issue. We should probably keep this thread on-topic though.
The link to this topic is @Corjan-Meijerink 's recommendation to stay online when navigating a track (where automatic recalculation is turned off by definition) and the question of when and why there is a need for a recalc anyway.
My guess: Every time you switch from "off-route" (where the track does not match the route) to "on-route" (when rejoining the route).
If I'd plan this route with HERE and an offroad waypoint
I'm pretty sure the result and the "issue" would be same. (I'd better use this version as an example, but it's less noticeable as no track is outlined.)
I am clearly missing something
I'm sorry my post was not helpful, as this was my main intention. What exactly are you missing?
-
@Erik-Plaggenborg should work! I got confirmation from Carpe Iter today that everything works as intended.
-
@Martin-Wilcke looks good and as designed!