New beta! 4.3.6 (380) - offroad waypoints
-
Hi all!
It is time for new beta again!
This version is all about the support of offroad waypoints!Offroad waypoints
Within the online MRA Routeplanner you can very conveniently mark some waypoints as "offroad". The main idea behind this is to skip a section of road that is unknown to the selected routing engine (HERE / TomTom / OSM). Ideal to avoid roads marked as closed (either seasonal or long term damaged) or things such as ferries.
The app had no idea how to work with these "offroad" waypoints and just treated them as normal ones. Causing the route to be different than planned
As of now, the app does support the offroad waypoints!
In the planner you can edit any route you like and mark any waypoint as offroad! Just as in the website.
If you then choose to navigate a route with offroad waypoints, you will see straight lines on the offroad sections. Just as planned!
These sections will be made extra clear with a nice dashed line.
While navigating over an offroad section, some things are however different:
- No visual instructions
- No audio instructions
- Possible loss of ETA information
- Automatic recalculations disabled
You don't need them anyway, as you're offroad.
Android Auto / CarPlay do not support the disabling of some visual elements. This can result in a slightly suboptimal experience when on an offroad section. Do let us know how you experience this!As offroad waypoints rely on track navigation under the hood, you do need to be online for an optimal experience. When offline, you will receive an appropriate warning
By introducing this feature in the app, we now support all the crucial features that the website has
Compass changes
A lot of users were unaware what the selected camera mode was. Not entirely their fault as the icon remained the same and you did not receive any other confirmation.
Now when tapping the compass, the icon will change based on the selected mode. Also, you will receive a short textual confirmation of the selected camera mode.
Bluetooth controller changes
- Support for Remotek firmware version 2.x
- Fixed issue with BMW Carpe Iter controller
Minor fixes
- iPad export option
- Manual day / night changes from CarPlay / Android Auto changed the base map style incorrectly
- Missing pause icons
- Not showing the same warning multiple times
Minor changes
- Added a loader in the in-app planner
- Not including current location when calculating routes that are far away
- Showing original route just before starting navigation (not only while navigating)
- Open route from RouteXpert library or activity feed by tapping the image
- Flow for starting routes created in a map other than HERE
What's next
That's it for now!
We are currently working on a complete rework of the home screen of the app Expecting a beta of this early February!
The idea behind this is to improve the visual appearance of the app, less clicks for the user, smoother transition to navigation and offline availability of the home screen maps too.Cheers,
Corjan -
@Corjan-Meijerink Absolutely amazing update!
-
Nice one again! Marvelous job, well done!
-
@Corjan-Meijerink great update!
-
@Corjan-Meijerink Fantastisch. Ik wacht met spanning het verschijnen voor Android af!
-
@Corjan-Meijerink Great release but I think I may have found a bug that also existed in the previous build. Whilst the iPhone display is correct, the CarPlay display does not re-centre or track correctly if you disconnect from CarPlay, stop navigation on the phone and then resume navigation on CarPlay connect after the No or Navigate prompt is selected on the CarPlay screen.
You can change the compass settings on the phone and/or in CarPlay but this does not resolve the route tracking picture on CarPlay. You can select the 'overview ' button in Car Play and this displays correctly but a second selection back to the previous compass view does not rectify the problem. The CarPlay cursor will eventually go off the screen unlike the correct picture on the iPhone:
The only way to solve the problem appears to be by disconnecting and reconnecting from CarPlay during the nav session. This problem appears to be fairly consistent for me with the sequence described above.
I can provide more information if needed, including logs.
