Related

BaseCamp 3.2.2, The First Days

Killtimer_
over 13 years ago
After a few days of fairly heavy use, a few observation.

The "Total Time" estimation in routes of any length is inaccurate, sometimes by as much as 15% compared to MapSource with it's ability to designate road speeds. I've verified the MapSource routes as time accurate on separate occasions.

There's still a map glitch at the 50 mile zoom level where BaseCamp is showing roads that disappear at any other zoom level until you get down to 3 miles. The area around Rock Springs Wyoming is a good example.

Today, this.

  • Former Member
    0 Former Member over 13 years ago
    When you're talking about Mapsource being able to designate road speeds, do you mean via a manual process or just that Mapsource appears to do a better job of taking speed limits into account?

    What map are you using?

    For your error alert: Are you sure you're loading 3.2.2 there and not accidentally launching an older version? There are multiple bad things you could be warned about at startup, but that "file version is unsupported" warning means that BaseCamp tried to load data that was written by a later version of BaseCamp. If you're sure this was both saved and loaded with 3.2.2, I'd appreciate you getting us a compressed version of your /BaseCamp data folder so I could have a look at it.
  • 0 over 13 years ago
    When you're talking about Mapsource being able to designate road speeds, do you mean via a manual process or just that Mapsource appears to do a better job of taking speed limits into account?

    What map are you using?

    It's a manual process. MapSource has a "Driving Speeds" tab in the preferences that allows you to set an average speed for 5 levels, from "Residential Street" to "Interstate Highways" Over the years I've tweaked these from experience so the resulting duration of a route is fairly accurate on rides up to about 1000 miles. Very handy for route planning. On multiple 600 to 800 mile routes the times were off by up to 2 hours between the two programs. This is important to me.

    Maps in both instances are CityNAV NT 2012.2

    For your error alert: Are you sure you're loading 3.2.2 there and not accidentally launching an older version? There are multiple bad things you could be warned about at startup, but that "file version is unsupported" warning means that BaseCamp tried to load data that was written by a later version of BaseCamp. If you're sure this was both saved and loaded with 3.2.2, I'd appreciate you getting us a compressed version of your /BaseCamp data folder so I could have a look at it.


    You're right, 3.2.1 was still launching from my dock. Is this new? I don't remember having to change this in the past. Possibly due to the fact I downloaded and installed rather than updated.? As a data point, the older version did recover eventually and loaded the last backup.

    Thanks for the reply.
  • Former Member
    0 Former Member over 13 years ago
    You're right, 3.2.1 was still launching from my dock. Is this new? I don't remember having to change this in the past. Possibly due to the fact I downloaded and installed rather than updated.? As a data point, the older version did recover eventually and loaded the last backup.


    This would generally mean that the version of BaseCamp in your dock isn't in the same location as the version installed by the downloaded installer. You can check the app's location by right clicking on it in the dock, then clicking options>Show in Finder. Our installers will typically put BaseCamp at /Applications/Garmin BaseCamp.app.
  • 0 over 13 years ago
    This would generally mean that the version of BaseCamp in your dock isn't in the same location as the version installed by the downloaded installer. You can check the app's location by right clicking on it in the dock, then clicking options>Show in Finder. Our installers will typically put BaseCamp at /Applications/Garmin BaseCamp.app.


    That's where they both were. "BaseCamp.app" (3.2.1) and "Garmin BaseCamp.app" (3.2.2)

    I have no idea how the name got truncated, but it does explain the error message.
  • Former Member
    0 Former Member over 13 years ago
    That's where they both were. "BaseCamp.app" (3.2.1) and "Garmin BaseCamp.app" (3.2.2)

    I have no idea how the name got truncated, but it does explain the error message.


    Was BaseCamp.app potentially installed by a map installer? We test our installers to make sure they write the correct executable, but we don't test all of the various map installers.
  • 0 over 13 years ago
    Was BaseCamp.app potentially installed by a map installer? We test our installers to make sure they write the correct executable, but we don't test all of the various map installers.


    I don't think so. It would have been installed at the end of the 3.2 Beta. Any map installs within the last year would have been via my lifetime subscriptions and AFAIK, they don't install any software.
  • 0 over 13 years ago
    Every time I start Basecamp 3.2.1 I am prompted to download the latest version, then when I close and restart BC I get these messages:

  • Former Member
    0 Former Member over 13 years ago
    Every time I start Basecamp 3.2.1 I am prompted to download the latest version, then when I close and restart BC I get these messages:



    I would suggest manually downloading 3.2.2 from our website (http://www8.garmin.com/support/download_details.jsp?id=4450) and running the installer.