Users with "holes" in your maps: we could use your help.

Former Member
Former Member
I've been seeing reports of shutdown crashes resulting in the app loading with a "hole" in the map that won't correct itself. We haven't reproduced this here, so I'd much appreciate some information. It's a bit technical, but if you can manage it we'd be much more able to address this issue:

1) Is there still a map tile at the bottom of that hole? Rotating the camera to look straight down or switching to 2D view should reveal a flat tile below your others if that's the case.

2) When you use Finder to browse to /Users/USERNAME/Library/Caches/com.garmin.BaseCamp/TileCache/ and sort by "Size", do any of your tiles have a size < 2 MB? If so, please zip them up and attach them in a reply so we can start exploring how to avoid loading these tiles in the future.

3) if and only if you don't find any suspicious (< 2MB) tiles like this, does deleting the /TileCache/ folder before starting BaseCamp fix your issue?
  • When I launch BC it often comes up with "holes" in the map. If I wait long enough they fill in -- up to 90 seconds in some cases. This behavior does not appear to be related to shutdown crashes, which in my case only happen if I try to quit while a hole is being filled in.

    If the map is "overzoomed" and I zoom out with any holes showing, that warning on the scale display remains until the holes fill in, even if I am zoomed way out (15 miles, for example, from 800 feet).

    If I delete the tile cache folder, on next launch the holes, if they even appear, fill in very rapidly ... once. Then it's back to slow and swiss cheese [g].

    All of the cache files are shown as 2.1 MB.

    -dan
  • Former Member
    0 Former Member over 13 years ago
    Same conditions as DANHAM reported.

    Observation:
    Disk Cache Size: 5GB

    Using CNNA 2012.30.

    Playing with the Detail Slider and Hide Map Features, specifically the "Points-Other" category, I noticed I could eliminate or significantly reduce the problem of "stuck" Tile rendering.

    Using CNEU 2011.30.

    I don't have the same issues with Tile "holes" or "stuck" Tile rendering even with all map features being "Shown".


    Overall rendering performance is still not up to the level it is in v3.2.2 ( which is nothing to write home about).

    Cheers,
  • Former Member
    0 Former Member over 13 years ago
    Removing the Tiles Cache folder helped initially. Redraw is quite slow when compared to 3.2.2

    Using CN NA 2012.3

    Core 2 Duo 2.8 GHz 4 GB RAM
    NVIDEA 9600m GT 512 MB Video RAM
    Seagate 320 GB hdd @ 7200 rpm