BaseCamp 4.4.7 Is Now Available

It would be very helpful if there was a publicly available running list showing, e.g., the cases that have been opened, the date of opening, the date of fix, the BC version number of fix and the date notification of the fix was published to this forum.

I'm not sure if I've seen this problem listed, but I was trying to print maps of several one-day trips and noticed that the route trace (the pink line) was often not on the intended roads but off to one side or above/below the actual road. The shape of the route traces were approximately correct but they were not aligned with the road they were supposed to be following. The problem is especially bad when I was trying to print a map of a whole day's travel.

Further investigation on my part reveals that route traces don't match the actual road path on the screen while viewing BaseCamp and is worse the farther out one "zooms". When close in, the matchup is pretty good but the more one looks at on one screen the worse the alignment is.

I'm using BaseCamp 4.4.7 and the map I am using is City Navigator North America NT 2015.4. I just tried NT 2015.3 and the "Global Map" and see the same misalignment between route traces and the roads. I have tried recalculating the route plans several times and it does not solve this issue.

Note that this problem is NOT the same as the one a little while back where segments of a route would become a straight line between two waypoints.

It has to do with the Map Detail Level as set on the tool bar. When set on "Lowest" hardly any trace matches the road. As you set the map detail level higher the match becomes better.

I just did a little experimentation and found that I still see significant errors in route trace vs roads on the map even with the map detail set to "Highest". It seems to me that older versions of BaseCamp would do much better at the overlay of route traces to roads on the map. I don't know if this is a difference in BaseCamp software or possibly some changes in the map software that we're now using.

Can anyone at Garmin help with this?

Thanks.

Bug

There's a bug in the the handling of text edit boxes of the Properties Tab of the waypoint tabbed dialog box.

When edting existing text, if you press the destructive backspace key more than once the cursor/caret does not delete the previous character as it should, instead it jumps to the beginning of the text string.

This becomes evident when the string contains spaces and the cursor hits one of them as it moves to the left.

To reproduce: enter address xx xx xx xx, place cursor at the end of the string and try to delete it using backspace.

I just did a little experimentation and found that I still see significant errors in route trace vs roads on the map even with the map detail set to "Highest". It seems to me that older versions of BaseCamp would do much better at the overlay of route traces to roads on the map. I don't know if this is a difference in BaseCamp software or possibly some changes in the map software that we're now using.

Can anyone at Garmin help with this?

Thanks.

Can you post here a screen shot of the problem you are seeing? I am curious about this.

I just did a little experimentation and found that I still see significant errors in route trace vs roads on the map even with the map detail set to "Highest". It seems to me that older versions of BaseCamp would do much better at the overlay of route traces to roads on the map. I don't know if this is a difference in BaseCamp software or possibly some changes in the map software that we're now using.

Can anyone at Garmin help with this?

Thanks.

This can happen if you've rotated the map at some point. Try rotating it again finishing with North up. That should correct it.

Can you post here a screen shot of the problem you are seeing? I am curious about this.

This is weird. I cannot seem to reproduce the problem from within BaseCamp today. However, when printing from BaseCamp to my HP Color LaserJet 2025DN, I still get the offset traces. I also tried printing to a .PDF file using Bullzip PDF Printer and that came out fine. I'm attaching a scanned .JPG of the print made by my HP printer to show the problem.



I've had no other printing problems that would be even remotely similar to this with my HP Color LaserJet 2025DN printer when printing from any other programs on my PC.

Additional tidbit: When I print a portion of a route, not only the route trace is shifted. The locations of any waypoints that I have entered are also shifted. I thought this might help the programmers.

Thanks.

Skip

This can happen if you've rotated the map at some point. Try rotating it again finishing with North up. That should correct it.

I just tried rotating the map in BaseCamp (4.4.7), then doing an "Align North Up", then printing to my HP printer. I got the same offset as before.

Thanks.

Anything from the development group on my printing problem?

Thanks in advance.....

Skip