BaseCamp 4.3.0.3 BETA is Now Available

Former Member over 11 years ago

BaseCamp 4.3.0.3 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.3.exe

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.2 BETA will be replaced.

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

Improved UI for address search
Improved results for address search auto-complete
Fixed a bug where Top Results search didn't refresh in advanced
Fixed a bug where cancelling the address search find did not work
Fixed a bug where address searches were not yielding results on device maps
Improved matching of serach results if search results exactly match user entered criteria
Fixed inversion of route departure times
Update free-form search string whenever advanced search parameters change
Fixed a bug where attemping to do an address search forces a POI search
Fixed not being able to clear departure time on last via if set after inverting route

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

NOTE: We are aware of some issues with routing. Moving waypoints caused the route to leave roads unexpectedly. We know about this issue, and a fix is undergoing QA, however it did not make it into this build. There is no need to report on this issue, we believe we have that under control.

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.

Again, thank you for all who participate.

0 Former Member over 11 years ago

I think I found a bug that I mentioned in 4.3.0.2.

The "Sort" selection in the small object explorer pane does not persist between sessions. It seems to revert to "Name". This is fine for me, because that is my preference. Just thought you'd like to know.

Also, just to record it for the new version, the waypoint duplication on route divide is still an issue (Case 127052).

Old issue of naming waypoints the same in separate folders (such as BP) is still an issue, as I have several of these in my db, and it's becoming increasingly frustrating to find new names for gas stations.

The naming thing is known and is not a trivial change. We are aware of that.

I still think that the sort thing is related to the fact that this is a beta and doesn't retain all of your settings. If this can't be reproduced in 4.2.5 I am not as concerned about it.

The waypoint duplication is by design. I realize some users don't like that but we wish to preserve the integrity of both routes.

0 Former Member over 11 years ago

Actually, on the naming thing.... I see what you're talking about. That case is opened but hasn't been through triage yet. I'll keep you posted.

0 SUSSAMB over 11 years ago

Address search is broken.

Entering my test address, 1 Gorse Avenue, Worthing, BN14 9PG produces no results. Also just putting the post code in the search box, which used to work, also now doesn't, instead the first part BN14 is placed in the Street Number box and the second part 9PG, is put in the Street box.

This with CN EU 2014.40 selected as previously, all worked OK in 4.3.0.1

(And have just checked 4.3.0.2, which is on a different PC, it doesn't work there either ... didn't spot in as I was away on holiday a few days after its release so had no time to play, but it must have broken somewhere after 4.3.0.1)

0 SUSSAMB over 11 years ago

Search of user data doesn't work correctly either. Entering a letter string in the search box with User data selected and My collections also selected produces weird results, missing some user data with that letter string and including some without.

Drilling down and selecting just a list to search also misses some user data out.

0 SUSSAMB over 11 years ago

Further playing crashed Basecamp and generated an error report that I've sent. I'll give up for now.

0 SUSSAMB over 11 years ago

On the plus side route optimization now seems to work OK :)

0 Former Member over 11 years ago

I agree with SUSSAMB's findings.

If I insert my postcode into the search box at top RHS it correctly finds the location.

If I then select the address in the results area and open advanced, it shows that the first part of the postcode has been put in the 'street number' section and the second part in the 'street' section.

If I then rerun the search, putting the full postcode in the 'Postal Code' box, it finds nothing at all.

May I also suggest that the address search has the following additional shortcoming(s):
The first, 'street number' field will only accept a numeric value. Like many addresses in this country, my (rural) address has no street number, only a property name. In my postcode there are (only) five properties, each identified by name: there are no numbers. Therefore, whilst the (essential) postcode search gets one to the general area, the absence of any ability to search on the property name means that location is only identified to the order of square miles - hardly helpful!
That point is exacerbated by the fact that the next line of my full postal addresses (and the same for the other properties) is the nearest village, not a street or road. The 'street' field will not accept / does not identify the village. The 'city' is the nearest town (again part of the full postal address) which is some 20 miles away.

I don't believe the above is unusual for rural and semi-rural addresses in the UK.

0 SUSSAMB over 11 years ago

I agree with SUSSAMB's findings.

If I insert my postcode into the search box at top RHS it correctly finds the location.

Strange, that didn't work for me earlier but it does now :confused:

The rest is still as I reported and as agreed by CO21706F above.

Edit: Just a thought ... does a newly installed version of Basecamp need time to index the installed maps? This would explain why a postcode inserted into the search box didn't initially work but now does?

0 SUSSAMB over 11 years ago

May I also suggest that the address search has the following additional shortcoming(s):
The first, 'street number' field will only accept a numeric value. Like many addresses in this country, my (rural) address has no street number, only a property name. In my postcode there are (only) five properties, each identified by name: there are no numbers. Therefore, whilst the (essential) postcode search gets one to the general area, the absence of any ability to search on the property name means that location is only identified to the order of square miles - hardly helpful!
That point is exacerbated by the fact that the next line of my full postal addresses (and the same for the other properties) is the nearest village, not a street or road. The 'street' field will not accept / does not identify the village. The 'city' is the nearest town (again part of the full postal address) which is some 20 miles away.

I don't believe the above is unusual for rural and semi-rural addresses in the UK.

Unfortunately I don't believe the Basecamp team has control over this, unless the data is in the CN EU map. Are you able to enter house name when doing a 'Where to, Address' on your GPS/satnav? If not then neither can Basecamp.

0 Former Member over 11 years ago

I know this is a beta version but it will be great if the developers decide to add Greek language in the final version of BaseCamp. Until now up to 4.2.5 version Greek language isn't available and that's something we Greeks miss since the days of MapSource.