BaseCamp 4.3.0.1 BETA is now available

Former Member over 11 years ago

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

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.1.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.

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

Added waypoint categories to the waypoint and bulk waypoint property dialogs
Added the Task Based Startup Menu allowing users to choose what they want to do giving more help into what BaseCamp can do
Added an Address search UI that operates more like MapSource
Added richer context menus in most tools on the map
Added feature to calculate a route that tries to match the shape of a track
Added feature to optimize routes within trip planner
Added a way to make it easier to find recently downloaded BirdsEye imagery
Added a way to filter Adventures by activity when using Find
Added indication of Adventure selected on the map
Added display of route stats while editing the route on the map
Added display of track stats while editing the track on the map
Added a device information dialog
Added support for curvy road route calculation
Added "snap to" indicator on the map when drawing new points in a route
Added ability to exclude track portions in the track join dialog
Added an "Off Road" profile and clarified the difference between Off Road and ATV
Added a prompt to preserve the original tracks when joining tracks
Added a hotkey to open and close the overview map
Added display of distance and bearing in the status bar when drawing routes and tracks
Added elevation statistics to the route dialog
Added statistics display to the bulk route properties dialog
Added ability to remove shaping points from routes in the route dialog
Added display of rubber band when moving a waypoint on the map
Added display of state and country city search results
Added ability to create and delete lists in the "Send To" dialog
Added an "uncheck all" option when managing Custom POIs
Added support for Lat/Lon coordiantes that are missing cardinal direction indicators
Added a comment column for tracks in the data list
Added more descriptive messages if export errors are encountered
Added FIT file support to the Import dialog
Improved performance when device maps are discovered for the first time
Improved balloons on the map
Improved drawing performance of large tracks and routes
Improved performance of filtering a track
Improved waypoint search performance
Improved discoverability of Adventure Edit, Publish, and View Online actions
Improved display of individual track portions in the track join dialog
Improved device communications performance when transferring photos
Improved notification that a subscription is needed for a selected BirdsEye product
Simplified default toolbar layout to exclude some editing tools
Changed the map product selection combobox to be hidden in the default layout
Fixed issue with encrypted Custom POI search (for RV and dezl devices)
Fixed issues with routes that have multiple transportation modes
Fixed device calculated ascent and descent values not being displayed
Fixed Trip Planner crash when adding food stops to trips
Fixed Basestation not updating most recent update time for contacts
Fixed issue with reading photo waypoints that had missing photos
Fixed map points remaining on the map after turning off all points
Fixed Adventure playback not taking track speed into consideration
Fixed a possible error when creating backup files
Fixed various langauge translations
Various other fixes and UI improvements

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.

0 SUSSAMB over 11 years ago

I'm not seeing the Import error box that you posted, is there a setting to make this appear?

I note there's a box to be checked if you don't want to see errors if they occur in future, so maybe the error box only pops up IF you load a bad gpx file.

0 dpawlyk over 11 years ago

I'm not seeing the Import error box that you posted, is there a setting to make this appear?

I note there's a box to be checked if you don't want to see errors if they occur in future, so maybe the error box only pops up IF you load a bad gpx file.

Yes.

You get the message when BaseCamp has a problem loading a file.

The message could mean the gpx file is bad or it could mean that BaseCamp isn't working correctly.

The message box is pretty useless. If it indicated the line in the file where it found the error, it would be useful (at least, to people who don't mind poking around in the gpx file).

0 Former Member over 11 years ago

The message box is pretty useless.

It is. So is the one MapSource gives (no line # as well).

Unfortunately it's not unusual for some units to produce corrupt/mangled GPX files. My 1490T does it with Current.gpx all the time. However the GPX files recorded with the trip log hack are just fine (never had an issue) even with large ones.

I fix GPX files manually since I have the tools and knowledge. Sometimes the errors are minor and one can recover 99.99% of the data. Other times you lose it all.

0 guyvdv over 11 years ago

I noticed that yet again in the beta version the route points are represented by a small tiny black point. Would it be possible to either make it an option what symbol one wants to use? In the "normal" version I changed it to another symbol (the "old" black flag with thanks to JaVaWa)

0 Former Member over 11 years ago

Beta will not read my List Data file. Using the "Fix" option did not fix anything and no List Data was used.

0 SUSSAMB over 11 years ago

I noticed that yet again in the beta version the route points are represented by a small tiny black point. Would it be possible to either make it an option what symbol one wants to use? In the "normal" version I changed it to another symbol (the "old" black flag with thanks to JaVaWa)

An option would be good, although I'm perfectly happy with the 'small tiny black point' as you put it. I suspect most don't want the screen cluttered with 'flags'.

0 dpawlyk over 11 years ago

It is. So is the one MapSource gives (no line # as well).

Unfortunately it's not unusual for some units to produce corrupt/mangled GPX files. My 1490T does it with Current.gpx all the time. However the GPX files recorded with the trip log hack are just fine (never had an issue) even with large ones.

I fix GPX files manually since I have the tools and knowledge. Sometimes the errors are minor and one can recover 99.99% of the data. Other times you lose it all.

That it is not unusual to have corrupt/mangled GPX files is irrelevant to whether the error screen should report more information (if that information is available).

The file I had appeared to be fine.

It would have made it easier to find the stuff that BaseCamp was having a problem with if BaseCamp would report the line number with the error.

0 Former Member over 11 years ago

I noticed that yet again in the beta version the route points are represented by a small tiny black point. Would it be possible to either make it an option what symbol one wants to use? In the "normal" version I changed it to another symbol (the "old" black flag with thanks to JaVaWa)

Have you tried changing the ViaSymbol registry setting?

https://forums.garmin.com/showthread.php?1165-via-points-in-MapSource&p=131057&highlight=ViaSymbol#post131057

It's possible the setting has moved from the registry to the user.config file.

PS: My changed ViaSymbol setting (City, Small) is being honored in 4.3.0.1. Just tried it. Now I have a headache :D Creating routes in BC has that effect.

0 Former Member over 11 years ago

Have you tried changing the ViaSymbol registry setting?

https://forums.garmin.com/showthread.php?1165-via-points-in-MapSource&p=131057&highlight=ViaSymbol#post131057

It's possible the setting has moved from the registry to the user.config file.

PS: My changed ViaSymbol setting (City, Small) is being honored in 4.3.0.1. Just tried it. Now I have a headache :D Creating routes in BC has that effect.

Keep in mind that route points are not real waypoints. They are vias along a route. Real waypoints have symbols. You can always create real waypoints and use them, although that creates clutter. I will find out if this is something we can change but I do not believe that there is a case for it currently.

0 Former Member over 11 years ago

Um, not sure what you mean by "route points". I created a route and inserted a via into it. It had the symbol for City, Small (small green dot). It was NOT a waypoint. That symbol is NOT the default. The default is a small black square. BC uses the ViaSymbol registry setting to determine what symbol to use.