BaseCamp 3.2.0.2 beta is available

Former Member
Former Member
A beta version of BaseCamp 3.2 is available (link below). Please read the following:

Warning

This is beta software, or an early peak at an incomplete product. We value your input, so we are providing this to you so that you can send us your comments and ideas. We have tested this beta version extensively, but that doesn't mean that there won't be bugs. Use at your own risk.

Notes

  • Please backup your existing data from BC 3.1 before running the beta.
  • The beta build requires you to allow Garmin to collect statistics on how you use BaseCamp to help us improve the application. This will be optional for the release of BaseCamp 3.2, but it is a required condition for using the beta.


Changes

Changes listed below are above and beyond the previous beta

  • Improved routing
  • BirdsEye downloads should now work
  • Added dragging photos onto the map views
  • Added dragging files into My Collection and the user data list
  • Added activity profile selection dialog at startup, improved migration of existing route settings and routes
  • Added better preserving app state when restarting (selected tool, selected folder, selected view modes, etc)
  • Added support for restoring backups from different computers
  • Changed drawing style of routes and tracks to use thinner lines
  • Fixed issue with adding and removing links on various property tabs
  • Various improvements to the draw order slider for imagery
  • Improved find address near center of screen
  • Removed filtered routes
  • Removed the "Route style" group box from the route options since it doesn't make sense to have multiple "Direct" route profiles.


Link
Download the beta here!
  • Former Member
    0 Former Member
    Just use the "erase"-icon. Move the cursor in the surroundings of the via-point. You then see a red cross over that point. If you click on that red cross, it will be deleted.

    In Mapsource you could rightclick, in Basecamp you have to click the "erase"-icon first.

    There is a difference in user interface, but we are used to the old way and have a bit of problems learning the new way.
  • Former Member
    0 Former Member
    To the developers: BUGREPORT

    If I edit a route on the map, I get thick gray line between 2 nearest points wich I can drag.
    If I am ready with it, the gray line stays on the map. If I zoom or move the map, the gray line sticks in the screen location. It looks to me, the cleanup after route-editing is not complete.
  • Former Member
    0 Former Member
    Another bug:

    If I look at my list of routes, imported from the Scottish Mounteneering Club, I see route-icons as 'direct'.

    If I doubleclick on such a route and get the proparties, it shows the "automotive". Yes, I can change the profile of the route, but why do I see a difference?
  • Former Member
    0 Former Member
    The clean up issue is what I was trying to describe above. I also get the thick gray line and when I click on the X (I had tried this previously) my route recalculates the entire route not just that part.
  • Former Member
    0 Former Member
    With cleanup I was referring to the thick gray line, not the route.

    @charlie: It looks to me, it would be normal to recalculate the (whole) route, because the algorithm could come to a new route before and after the edited section.
  • Former Member
    0 Former Member
    The problem with the recalculation that I have found is that it COMPLETELY recalculates the entire route even after I've put it where I wish it to be.

    It ends up entirely different from the original and my modified route. After recalculation it is an entirely different route altogether. I will try to post some before and after pictures this afternoon.
  • Former Member
    0 Former Member
    Maps and 276C

    Vista 64bit Home Premium SP2 w 4 GB. Today for the first time I connected my 276C to BaseCamp Beta. The Beta was already running. The 276C never showed up in the Devices section. Did a restart of the Beta and still it did not show up in the Devices. Killed the Beta and started MapSource it found the 276C. Closed MapSource and restarted the Beta didn't find the 276C. Killed the Beta and started the last version of BaseCamp and the 276C showed up in the Devices. Closed that and restarted the Beta and it showed up in the Devices. So, it appears that I must connect the 276C BEFORE I start BaseCamp in order for BaseCamp to see my device. Since this is different than the way MapSource does it I think that perhaps a note in the Help File would be useful.

    Maps: I wanted to see what maps I had installed on the unit while in BaseCamp. I went to the map transfer function and asked it to get the maps but they never showed up in the visual representation and it never showed the space utilization on my data card. I think it would be useful to have that ability.

    Search: I am using CIty Nav North America NT 2009. I was trying to find 1813 West 9th Street, Brooklyn NY. For some unknown reason in MapSource it tells me "the selected street is not valid in this map product. Please select a different street" In BaseCamp Beta it just searches and returns a whole list of unrelated streets with different numbers if I type "1813 West 9th Street". But, if I type "1813 W 9th Street" it finds the correct address. If I do the search on the 276C with the same map product loaded it just finds the street and address whether I type in West 9th street or W 9th Street. So in this case BaseCamp Beta can find a street that MapSource cannot since MapSource has no "W 9th Street" entry in the list of searchable streets when using CNNA NT 2009. But the real question is why can't BaseCamp Beta do what the 276C can do when searching for an address, i.e., give the correct answer whether I use West or just W in my search argument?
  • Former Member
    0 Former Member
    Track elevation profile colors

    I really like the new track elevation profile features in the 3.2.0.2 beta but I can't find a way to change the font color. Unfortunately the x and y axis scale text seems to be white making it unreadable (see the attached screen capture). Is there a way to change the font color? If not can it be changed to black in the final release.

    PS: I just brought up the same track elevation profile in BaseCamp 3.1.3, on two different machines (XP SP3 and Vista SP2) and on both the x and y axis text was black.
  • Former Member
    0 Former Member
    I have the black type of font. No problems here. Indeed colour not selectable.

    Maybe uninstall and re-install?
  • Former Member
    0 Former Member
    I have the black type of font. No problems here.

    Thanks for the reply. I guess there's something funky on the XP SP3 box that the 3.2.02 beta is on. That said BaseCamp 3.1.3, on the same machine, shows black text.

    I tried resetting all the Basecamp settings back to defaults and restarting but no change.