I hope that sharing my experience will help others with similar issues. I had created a number of custom maps with the help of the MAPC2MAPC program before BC ver 3.0.1. I selected the "Transparent KMZ" option during the tile build. They all worked fine in the previous software for the Oregon 550, with Topo US 24K West, as well as the previous BC version. Of course they work fine in Google Earth, also.
With the new BC version however, the custom maps produced an error and would either not show, or be missing tiles. Missing tiles also occurred in the Oregon 550 after the recent GPS software upgrade to a lesser extent.
After trying several things, I used Google Earth to set the transparency to the maximum opacity, by right clicking each tile, and selecting properties. Move the transparency slider to the far right to set this parameter. Then use the "save as" to save the tile set to a suitable name for transfer to the Oregon 550. Reconnecting with Basecamp now works without error, and all tiles show as expected. I have converted NOAA raster charts for most of the Columbia River from the Pacific Ocean to the Bonneville Dam with no further display issues on either the Oregon 550 or in Basecamp v 3.0.1.
I hope you can find this tip useful, if you experience similar problems.
-Dale-
Update:
I just now created a new map set using MAPC2MAPC, with the "Transparent KMZ" choice unchecked. The resulting custom map produced the same error in the latest Basecamp, although it works fine in Google Earth. So from Google Earth, I re-saved the file. This cleared the error in Basecamp, suggesting that the problem is a file format issue from within the MAPC2MAPC program.
