BaseCamp 4.6.3 Is Now Available

The following is a list of changes:

  • Fixed crash when zooming into raster maps.
  • Fixed crash when loading a track with sporadic elevation data.
  • Fixed an installer signature issue...thanks to JaVaWa for finding :)



http://www.garmin.com/en-US/shop/downloads/basecamp

AppStore: https://itunes.apple.com/us/app/garmin-basecamp/id411052274?mt=12
  • Former Member
    0 Former Member over 9 years ago
    As of 10:00 EST still showing 4.6.2 on the download page and no auto-update for the program...
  • Auto-update should be working now. The Mac download page (http://www8.garmin.com/support/download_details.jsp?id=4449) is showing 4.6.3 for me. 4.6.2 is the latest for Windows. What page is showing 4.6.2
  • Former Member
    0 Former Member over 9 years ago
    I see, this thread was also stickied in the Windows subforum, so I assumed 4.6.3 was also for Windows. The sticky has since been removed. :)
  • Ah, I didn't know that was possible. As fyi, this 4.6.3 release was just to fix serious Mac only issues, which is why Windows is still at 4.6.2. But thanks for the auto-update heads-up! Probably would have been weeks before I noticed I forgot to add 4.6.3 to the auto-update server.
  • Time Machine Problems Continue

    Base Camp is still not smart enough to ignore network volumes mounted by Time Machine during a backup. Even worse, Base Camp seems to know about Time Machine as the pop-up says, "Time Machine Backups detected. BaseCamp needs your permission to use this device." The options are Skip and Allow. But lacks "remember this selection in the future".

    I don't understand why I would ever desire to allow BaseCamp access to my Time Machine archive?
  • Base Camp is still not smart enough to ignore network volumes mounted by Time Machine during a backup. Even worse, Base Camp seems to know about Time Machine as the pop-up says, "Time Machine Backups detected. BaseCamp needs your permission to use this device." The options are Skip and Allow. But lacks "remember this selection in the future".

    I don't understand why I would ever desire to allow BaseCamp access to my Time Machine archive?


    Which OS X version? I have not seen this problem in a long time (running 10.11.4).

    -dan

    EDIT: I'm now recalling this may be a USB vs. Firewire issue. My T.M. drive is FW 800.
  • BaseCamp will try to access any device that is mounted. 'Time Machine Backups' is just the name of that device, which I believe you could rename to whatever you want. You shouldn't be prompted to allow access every time though. I'll have to look into what's going on there.
  • BaseCamp will try to access any device that is mounted. 'Time Machine Backups' is just the name of that device, which I believe you could rename to whatever you want. You shouldn't be prompted to allow access every time though. I'll have to look into what's going on there.


    In case this helps, my WD 1TB external firewire 800 drive does NOT appear in the "My Garmin Devices" window. It has two partitions, one for cloning my hard drive, and one for Time Machine and both are always mounted on my desktop.

    I'm running OS 10.11.4 and BC 4.6.3.

    -dan
  • BaseCamp will try to access any device that is mounted. 'Time Machine Backups' is just the name of that device, which I believe you could rename to whatever you want. You shouldn't be prompted to allow access every time though. I'll have to look into what's going on there.


    Thanks. Has been every version of MacOS for many many years. Every BaseCamp. Time Machine runs every hour, Apple's default value. The destination is an Apple Server's time machine service. All latest software but hardware is Mac Book Pro 2011 and Mini Server is 2009.

    Don't see in release notes but another longstanding bug has to do with case sensitive file systems. My Time Machine archive is case sensitive but my boot volume is not. BaseCamp on Mac booted from case sensitive filesystem knows usb gps is attached but can not read or write. Yet Garmin Express can.

    Once Upon A Time I ran nm against the BaseCamp binary to extract strings and observed very poor filename case discipline.

    Guessing my Time Machine issue is another of filesystem case sensitivity.
  • Former Member
    0 Former Member over 8 years ago
    No updates or bug fixes approaching 6 months now...

    Where'd the dev team go?