BaseCamp 4.3.0.2 BETA is Now Available

Former Member
Former Member
BaseCamp 4.3.0.2 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.2.exe.zip

You will need to unzip the file before installing.

This release does not support XP.

You do not have to uninstall BaseCamp 4.2.5 and it will not overwrite that installation. The BETA and an official release of BaseCamp will live side-by-side but must be used separately. However the 4.3.0.1 BETA will be replaced.

Below is a list of changes. This is only a BETA release.

Added “Find Intersection” to the Find menu
Added parsing of the primary find text into address search fields
Improved ordering of auto-complete results
Improved street auto-complete results when searching for streets with prefixes and suffixes
Improved some usability issues with address and intersection searching
Improved recovery from corrupted cache information from device maps

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

Please post any bugs you may find here. This release is to assist us in testing with a wider user base and wider set of devices. Bugs may be present, and any feedback is welcomed.

NOTE: We are aware of several issues with address searching on devices. We ask our users to please test this very well and let us know of the issues you find. Some of them will be duplicates of issues we have already found, but the advanced address search is new for this release and we need a good test bed to be sure that the feature is working correctly when we do the full release.

Again, thank you for all who participate.
  • Yes, we can only expect the BC developers to make changes to Basecamp. They have little control over how the units act/re-act.

    I know I have to be careful in how I send or receive data for my z660. That is why I rely so heavily on Basecamp, and also why I felt Mapsource handled this task better before BC v4.3.x.
  • Former Member
    0 Former Member
    I know I have to be careful in how I send or receive data for my z660.


    I don't let MapSource or BaseCamp access my 1490T or Oregon 450 directly (my 76CSX uses the USB protocol so I've no choice with it). Instead I use clone devices (SD cards) and transfer (GPX, IMG and other) files, in both directions, manually (i.e. with Windows Explorer). I'm sure many consider that too much trouble but it does prevent unexpected changes to my units. If anything gets added or deleted it's because I did it.
  • I am still trying different ways to manage my GPS data, but I haven't had a full-scale mess-up in a long time. Personally, I've been using the import/export(send/receive) tool until recently. Now I'm trying the drag n drop, but am being very watchful on what's on it before/after.

    Personally, I manage it by having a folder set that represents what I keep on it for 90% of it's use in the local area.

    When I go outside that and need to add, I've either added (moved) a folder with the local info and added that to the gps, or, if it's a long trip, I replace the file of local data with a file of specific trip data.

    I've not been a fan of the "import routes/points" functionality within the GPS, so using the drag n drop from within Basecamp to my z660 has been a better experience, in my opinion. I do wish I had more capability to live edit what's on the unit through Basecamp,but I don't think that is possible based on previous discussions in other threads. I think it has to do with the different filing conventions used through the years, but really not sure.

    I don't know if my experience is scalable, though. I know I try to keep my GPS fairly pared down so that I don't have to sift through a lot on the road. If I had more data on my zumo on a regular basis, I would probably use your method.
  • It's because unlike handhelds nuvis and zumos store their data in inaccessible files. When you look in the GPX folder you'll see current.gpx and any other gpx files that you/Basecamp/Mapsource/any third party program has sent there. On boot up the GPS merges those additional .gpx files with what it has in its own internal memory, then writes a copy (current.gpx) into the GPX folder ... but it's a one way copy. You can actually delete current.gpx and it'll be rewritten.

    So Basecamp can't do anything to delete data on a nuvi/zumo.
  • I've just finished planning a 16k mile motorcycle trip that I will leave on in 4 weeks - Denver>Florida>Maine>Alaska>Washington>California>Denver. It was first planned as a single route to create the overview so I could budget time and money, then Divided into 18 legs using the Divide tool. With my 3,000 database objects (yes, backed up 3 ways!), what a PITA to insert the primary (first created) Waypoint at the beginning of each newly created "next" leg, deleted the Appended Waypoint from that leg in the dialog box, the search for and delete each newly created superfluous and redundant DBO with the dreaded appended number from the database.


    Well of course you needn't do any of that. You could simply leave it 'as is'. The routes would still work with the appended numbers. Maybe I have a less tidy mind :)
  • I've read your business case and, to be honest, I don't get it. Divide, by its very nature, implies a split "whole" - starting the second leg from a different point than you ended the first is simply traveling two unconnected routes.


    I guess if you're not a hiker you wouldn't get it, but then I don't get the need to rename waypoints just so they don't have 1 in them. Each to their own :)
  • Former Member
    0 Former Member
    ...I try to keep my GPS fairly pared down so that I don't have to sift through a lot on the road.


    I currently have 132 waypoints in my 1490T (and the same ones in my 450). It supports categories (I have 12 I think) so I use those to keep the list manageable.

    For special trips (vacations etc) I do that same as you. I load waypoints/routes and then remove them afterwards. I also assign a new category to those points to make deletion easier. However all the data from such trips (waypoints/routes/tracks) is saved in a MapSource file for future reference.
  • I'm going to assume you are aware that the BC 4.3.x beta has an awesome upgrade to categories where previous versions using "lists" as categories was horrendous for large collections. This was a HUGE improvement to managing waypoints on the device.
  • Former Member
    0 Former Member
    Yes, I've been using the 4.3.x betas instead of 4.2.5 when I do BC stuff.
  • For me, I didn't use BC much before the 4.3.x betas. They were just too frustrating in too many areas.

    I switched out my XP machine, loaded 4.3.0. whatever, and I haven't even loaded MS on the new machine. For me, BC has now replaced MS. BC still has a few things I like to see changed, but I now have fewer concerns with BC than MS, so I use BC.

    This is a pretty huge leap for me, evidenced by some of my older rants about BC. :)