BaseCamp 4.2.5 is now available -- LAST XP RELEASE

BaseCamp 4.2.5 is now available and can be downloaded here:

http://www8.garmin.com/support/download_details.jsp?id=4435

Below is a list of changes. This is only a MAINTENANCE release. New features will be available in an upcoming 4.3.X version.

Fixed strings being displayed in multiple languages in the UI
Fixed long delay when changing the activity profile of a route on the route dialog
Fixed long delay when converting a track into a route
Fixed issue where changing the activity profile of an individual route leg wasn't applied unless one of the via times was also changed
Fixed issue clicking Next on the geotagged photo properties dialog when there is only one photo in the list
Fixed long delays when selecting many points in the track point list
Fixed long delays when pasting many points in the track point list
Improved robustness of auto-saving user data


Post here if you have questions.

The update server for non-English language will be updated as soon as possible.
  • Sounds like you could be opening the installer ... Look in All programs, Garmin and see if Basecamp is listed. If so open it from there.
  • Former Member
    0 Former Member over 11 years ago
    Hi there
    the "update is ready" dialogue shows only after I have opened BC from the usual desktop/start menu icon..

    ***************** edit update***************

    I see that when the installation of 4.2.5 is reported as "completed successfully".. the version of BC is still actually 4.2.4.

    what is going on here.. anyone!????
  • I am not sure what's going on. You might go to the link in my signature and download the installer fresh. We did tests of the updates and it seemed to be okay.
  • Former Member
    0 Former Member over 11 years ago
    Hi there
    I bit the bullet and uninstalled 4.2.4 then ran the same 4.2.5 installer.. success.. the new version opens without any message and all my contents are there.. several Gbs of Birdseye, tracks, routes and 1000's of waypoints..
    lucky me...
    cheers
    CD
  • Glad you're up and running. I will check on the update process and see what did not work for you. I am not aware of others having this issue but I am indeed glad that you're working and on 4.2.5. Thanks for the feedback.
  • Greetings,

    I had to install Basecamp 4.2.5 on my new Windows 8.1 PC and it works fine, fast, except for one thing. I imported a pocket query of all caches in the area where I am headed with another cacher, so I have both found and unfound caches in the pocket query file. As in the past on the other 3 XP machines, I was able to have both found and unfound caches displayed on the screen from a single import. Now, in this 4.2.5 version, all imported caches are displayed as unfound, despite the logs within the displayed unfound cache that have my found logs. Is there something I missed in a set up on the new install?
    Thanks,
    BikeNfind - Jerry
  • Same File loaded into Nuvi500

    Greetings,

    I had to install Basecamp 4.2.5 on my new Windows 8.1 PC and it works fine, fast, except for one thing. I imported a pocket query of all caches in the area where I am headed with another cacher, so I have both found and unfound caches in the pocket query file. As in the past on the other 3 XP machines, I was able to have both found and unfound caches displayed on the screen from a single import. Now, in this 4.2.5 version, all imported caches are displayed as unfound, despite the logs within the displayed unfound cache that have my found logs. Is there something I missed in a set up on the new install?
    Thanks,
    BikeNfind - Jerry


    I thought about it, and loaded the same GPX file into the Nuvi500 as I always do, and it discriminates the found and unfound caches properly from the same data. Maybe something in Basecamp 4.2.5 ?

    Jerry
  • Mapsource works...

    Greetings,

    I had to install Basecamp 4.2.5 on my new Windows 8.1 PC and it works fine, fast, except for one thing. I imported a pocket query of all caches in the area where I am headed with another cacher, so I have both found and unfound caches in the pocket query file. As in the past on the other 3 XP machines, I was able to have both found and unfound caches displayed on the screen from a single import. Now, in this 4.2.5 version, all imported caches are displayed as unfound, despite the logs within the displayed unfound cache that have my found logs. Is there something I missed in a set up on the new install?
    Thanks,
    BikeNfind - Jerry


    Ultimate test for Basecamp. Deleted the imported pocket query. Loaded the same PQ into Mapsource on the same 8.1 machine and it worked normally, showing the found and unfound caches. Re-loaded the same PQ file once again into Basecamp and it failed to identify the found caches. SO, copied the found only caches from Mapsource and pasted them onto the Basecamp map to overwrite the same data and now the icon is correct. Looks like 4.2.5 isn't reading the data for the GPX file showing FOUND for the proper Icon.?

    Hope this helps.
    BikeNfind - Jerry
  • BaseCamp doesn't really care about your geocaches. BaseCamp users have been requesting improved geocaching functionality since the original BaseCamp was published, but Garmin have never made geocaching a priority for BaseCamp.
  • I came across an issue after transfering waypoints wirelessly between a Garmin Oregon and a Garmin Fenix, after the transfer, the new waypoint is visible on the watch under Waypoints, also a new gpx file starting with a blank space and a Number ( 2.gpx) is added to the fenix /garmin/gpx folder (looking at the gpx text content the file includes the transfered waypoint details). Later when the fenix is connected to a PC and BaseCamp is launched, an error message is displayed: (There was a problem communicating with fenix (Unit ID XXXXXX) ( An error ocurred while reading the following files(s): Garmin/gpx/ 2.gpx). I am able to continue, but Basecamp under fenix internal storage does not show the recently transfered waypoint

    Again when a waypoint is sent from the fenix to the Oregon 450, a new gpx is added to the oregon garmin/gpx folder (1.gpx no blanck spaces in the name), then when launching Basecamp
    an error message is displayed: (There was a problem communicating with Oregon 450 (Unit ID XXXXXX) ( An error ocurred while reading the following files(s): Garmin/gpx/1.gpx) I am able to continue, but Basecamp under Oregon internal storage does not show the recently transfered waypoint