Is now available here. Noted changes from 6.16.1 are:
◦Improved handling of invalid gpx files from devices.
◦Improved handling of missing components, MapSource will now display a message indicating the missing component.
◦Changed number of most recently used files from 4 to 10.
◦Fixed some untranslated strings.
◦Fixed an issue with saving as gpx and dxf in the Dutch localization.
◦Fixed a routing issue with third party map products.
◦Fixed several other routing issues.
◦Fixed an issue where MapSource would not remember the icon size setting correctly.
◦Fixed an issue with deleting waypoints from a route.
◦Fixed a map drawing issue.
◦Fixed display of ampersands on the map.
◦Fixed an issue with creating waypoints on certain features
The display of 22's and 71's instead of street labels at certain zoom levels that some people are experiencing is not fixed in this release, but Garmin say they are able to reproduce the issue and will hopefully have a fix soon.
The most important change in this release doesn't get a mention in the release notes though: Garmin have changed the way the Road Selection slider works on the Routing Preferences tab. Below is an explanation of the change from one of the developers that I have cross-posted from the Garmin forums:
◦Improved handling of invalid gpx files from devices.
◦Improved handling of missing components, MapSource will now display a message indicating the missing component.
◦Changed number of most recently used files from 4 to 10.
◦Fixed some untranslated strings.
◦Fixed an issue with saving as gpx and dxf in the Dutch localization.
◦Fixed a routing issue with third party map products.
◦Fixed several other routing issues.
◦Fixed an issue where MapSource would not remember the icon size setting correctly.
◦Fixed an issue with deleting waypoints from a route.
◦Fixed a map drawing issue.
◦Fixed display of ampersands on the map.
◦Fixed an issue with creating waypoints on certain features
The display of 22's and 71's instead of street labels at certain zoom levels that some people are experiencing is not fixed in this release, but Garmin say they are able to reproduce the issue and will hopefully have a fix soon.
The most important change in this release doesn't get a mention in the release notes though: Garmin have changed the way the Road Selection slider works on the Routing Preferences tab. Below is an explanation of the change from one of the developers that I have cross-posted from the Garmin forums:
The most obvious change is that now there are only 5 settings where there were 7 before. But that's not all, we've actually changed the way this slider works and we hope this will work better for most of our users.
There were some issues with the old slider:
1. Setting a route to "shorter route" and "prefer minor roads" would yield really odd results.
2. Using the slider in conjunction with "faster route" would not really work at all with NT maps.
3. A feature most people are interested in: reliably avoiding highways, did not really work.
If you do not care about the road type, please leave the road slider in the middle. This will yield the best results and the fastest route calculation times.
If you would like to avoid major highways, set the slider into position 2 (between "minor roads" and the middle). This works fairly well now.
If you would like to avoid major highways and other larger roads, set the slider all the way to the left.
The two settings to the right will try harder to avoid small roads. But it is not necessary to set it if you just care about a fast/short route. MapSource will use Highways preferably already in the middle setting.
Now, some caveats: the slider works well if the map data contains enough roads for each road class. If there are not enough smaller roads the algorithm might fall back to highways even if you picked "minor roads". You might get better results by using position 2 in that case.
It is likely that MapSource will recalculate routes differently now for the "minor roads" / "prefer highways" setting. Sometimes the route might be a "better" one, sometimes it might get "worse". But overall we hope this change will allow users to calculate scenic routes more reliably.