Mac/Windows Software

Basecamp Windows BaseCamp 4.0.0.5 is released

BaseCamp 4.0.0.5 is released

Former Member over 12 years ago

We are releasing another public Beta of 4.0. This release contains a bunch of bug fixes and a few added features.

You should be able to update from within 4.0.0.4. Or download it directly at http://developer.garmin.com/apps/BC/BaseCamp_4.0.0.0_Beta.exe.

If you had trouble updating from 4.0.0.4 to 4.0.0.5 please use the download link, don't update from within BaseCamp.

Please give it a spin, report any errors and leave feedback here or via feedback option within BaseCamp. Thanks!

The What is new in BaseCamp 4.0? Thread still applies. Adventures are still the focus of this release.

We disabled the 'Unlisted Data' list for now till we get it working correctly.

A long-standing issue with shopping card POIs showing up on the map even if users turned of the display of points has been fixed.

You can now import into folders and lists (before we would always create a new list in My Collection).

Full change list:

Added ability to import into folders and lists (and not always import into My Collection).
Added ability to archive/un-archive adventures.
Added header for the folder data list.
Added easy way to display elevation profile from adventure.
Added ability to duplicate geotagged photos.
Added link the BaseCamp license agreement in help menu.
Added info icon for adventures in folder list.
Added ability to undo/redo on supported devices.
Added ability to drag and drop folders with BaseCamp data from the file system.
Added ability to accept Google Maps coordinate format when centering map at position.
Added new dog icons.
Added more information to adventure find results.
Added ability to permanently hide the adventure group.
Changed the simple route dialog to transition into the route properties so the route can edited further.
Don't let scroll-wheel change detail setting after changing setting.
Made sure waypoint creation date is visible by default in the waypoint properties dialog.
Fixed an issue where turning off the display of points would leave a lot of "shopping cart" POIs on the map for certain map products.
Fixed an issue where the selection was lost when left-clicking on the map with the hand tool.
Fixed issues where BaseCamp erroneously allowed you to create waypoints and would crash.
Fixed issues with route/track creation and joining.
Fixed issues with deleting data on devices.
Fixed issues with creating routes from tracks.
Fixed transfer of waypoint categories to device.
Fixed issue when BirdsEye selection box was dragged too far North.
Fixed issue with displaying custom maps on devices.
Fixed various adventure issues.
Removed Unlisted Data list (it will be back).

0 Former Member over 12 years ago

Thanks Falagar,

Is there a chance that the Dakota will be released with the new firmware that is compatible with Basecamp (and the activity routing) soon?

I have very little visibility into the device side of things. Additionally, it's Garmin policy to not release any scheduling information about planned software releases. So I am afraid I don't have a satisfying answer.

There certainly is a chance, but I really cannot say if and when it might happen.

0 Former Member over 12 years ago

Hi Falagar
Just installed 4.0.0.5

Some (old) issues
- When duplicating routes waypoints are duplicated also. I know this a deliberate choice. What really would solve the problem is a distinction between a waypoint and a "private" poi which is of course fixed to a location (or a way to indicate that a user waypoint has a fixed location) . When a route contains (private) poi or fixed waypoints those should not be duplicated.
- When exporting routes to (in my case the Oregon 450) the via points (do not alert types) are displayed on the device with a blue pin: very nasty clutter of the screen: please make it in invisible or just a small black dot.
- Perhaps not basecamp: but I am not able to edit routes uploaded from basecamp on the oregon itself ?(the edit route button (or invert) is not shown in that case) Oregon firmware 4.8

Wishes
- support for poi files...

0 Former Member over 12 years ago

BaseCamp 4.0.1 will ask you if you want to duplicate the waypoints or not whenever you duplicate a route.

Check https://forums.garmin.com/showthread.php?1165-via-points-in-MapSource&p=131057#post131057 for a work-around regarding the via point issues.

POI file support is definitely on the list.

0 Former Member over 12 years ago

Hi Falagar

Thanks for reaction. Looking forward to 4.0.1.
Kind regards Rob

0 Former Member over 12 years ago

OK, I know the disclaimer that usually goes with beta software. But this thing is so buggy it is closer to alpha than beta status.

I cant list all the problems I have with it, so let me just point out the most serious things:

My 3.3 folder was 60 MB and contained 3000 files. I updated to 4.0beta on July 27. Now my 4.0 folder is 820 MB and contains 82000 files. And since July 27 I only added <10 tracks, <50 waypoints, <50 imported geocaches. There is something seriously wrong with your data management.

Also, since an hour ago, I cannot start BaseCamp anymore. It says the list file is corrupted. Right now I am making a backup of the folder (which takes ages due to the 82000 files), then I will start the "fixing" procedure. Hopefully this will fix the DB so I can export my new, recently added data, then go back to 3.3 and reimport them.

Considering that 4.0 adds almost no features it is really weird how you guys managed to mess up so completely...

0 Former Member over 12 years ago

Results:

- The "fixing" feature simply deleted EVERYTHING and reinitialied the DB to be completely empty (and deleted all files in the subfolders). Fortunately I had the backup.
- I was able to get AllData and FolderData back from Dropbox (fortunaltely that is where I store my BaseCamp database) in older versions before the crash.
- Putting them back I was able to launch BC 4 again and exported all the positive changes I made since the switch to BC 4.
- Of course negative changes (deleted objects etc.) and some folder re-org were lost. I will figure those things out over time when I encounter these errors in my DB.
- I was able to import these things into BC 3.3.3. Even now the 3.3.3 DB is only 60 MB, so that the hugeness of the BC 4 DB must clearly have been caused by a serious data management bug.
- The fact that the BC database now consists of thousands of files is a SERIOUS problem for the future. You can always restore two (or ten or twenty) files manually from your Dropbox to an earlier version, but you CANNOT restore thousands of them, because you need to do this for every file individually.

I am glad I am back with 3.3.3 now and will wait a while before any further upgrade. Probably not before 4.1 (non-beta).

In the future please dont release alpha software to the general public. Thank you.

0 DaveA_ over 12 years ago

May I ask where all these files are located? I've been intermittently running BC 4 and 3.3.3 and I don't think that I've accumulated multi-thousands of files.
Maybe I'm not looking in the right place(s).

0 Former Member over 12 years ago

BaseCamp\Database\4.0\GeocacheLogs (67000 files)
BaseCamp\Database\4.0\TrackSegments (14000 files)

as opposed to

BaseCamp\Database\3.3\GeocacheLogs\ (837 files)
BaseCamp\Database\3.3\TrackSegments\ (1800 files)
(Their number did reduce a little during my re-import sessions, not quite sure why; I did make some errors there, had to delete things and then re-import them; after that I had the numbers listed above; before I touched the 3.3 folder I contained 3000 files)

0 Former Member over 12 years ago

addendum: In total I have 290 tracks in BC 3.3.3. Not clear why that even corresponds to 1800 TrackSegments.

0 Former Member over 12 years ago

further addendum: Many of the TrackSegments in the BC 3.3.3 folder are tiny (e.g. 98 bytes). I do not have any tracks with as few points as that.

I suspect that those are tracks that were created when cutting of crap from other tracks, and that were then deleted. It seems that even BC 3.3.3 does not delete tracks from the TrackSegments folder when they are deleted from BC.

Of course that still does not explain why the number of track segments exploded astronomically in 4.0.