This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BaseCamp 3.3.0.2 beta posted

Just to prove that we are listening, we are releasing 3.3.0.2 which fixes several issues that have been reported from the first beta.

The beta is downloadable from: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.2_Beta.dmg. If you are already running BaseCamp 3.3.0.1, it should automatically update to 3.3.0.2.

We are very interested in your feedback, please report bugs and oddities you find, and comment on the new features.

  • Fixed + and - to correctly zoom in and out
  • Fixed crash that could occur when ejecting a device
  • Fixed issue where columns in the Detailed User Data View could get repeated
  • Fixed issue where Undo and holding the Alt Key would terminate the current route creation using the Route Tool
  • Fixed to be able to read waypoint categories from newer devices.
  • Added ability to edit phone numbers in the Waypoint Contact Info tab.
  • Fixed zumo 5x0 and 4x0 route transfer issues. Note that this may cause route transfer issues on the zumo 660. A future firmware update on the 660 will address this issue
  • Fixed any profiles from BaseCamp 3.2 that have invalid routing preferences (ie invalid vehicle types and incorrect avoidances)


Known Issues:
  • Proximity waypoints sent to SD cards in outdoor devices will not have the proximity show up in the device. Sending the waypoints directly to the device does work.
  • Reading routes from a Zumo 660 may cause a crash. Issues is being investigated, but the circumstances seem to be rare.


Edit: Link changed to a different server that should work
  • P.S. Please excuse my frustration...


    It's shared Dan. Early on in the BaseCamp evolution many of us were clammouring for MapSource based functionality as a minimum in BaseCamp. One of the dev. team at that time told us up front that the last thing they (the Mac Team) wanted was to port MapSource to the Mac. They felt it was dated code and the feature set was too complex for their users. My hope is that if enough of us continue to be vocal about BaseCamp's regression in some areas, the functionality might get restored. I really hate having to run MapSource in conjuntion with BaseCamp, but for the foreseeable future it looks like it's the way it is.
  • Former Member
    0 Former Member over 13 years ago
    It's shared Dan. Early on in the BaseCamp evolution many of us were clammouring for MapSource based functionality as a minimum in BaseCamp. One of the dev. team at that time told us up front that the last thing they (the Mac Team) wanted was to port MapSource to the Mac. They felt it was dated code and the feature set was too complex for their users. . .


    Thanks and yes, I recall that post as well. I had a few exchanges with the team "off-line". The fundamentals of coding haven't changed in my lifetime: Complexity exposed to the User is indicative of poor workflow not the breadth of features or function.

    MapSource features are far from complex - it just has crappy workflow. Just like the old GPSMAP Chartplotters and 60 series GPS's. They were no more complex than the current Handheld GPS's (Montana, Oregon, etc.) with respect to features and functions. But, those old units had the worlds worst workflow - no one could remember where menu's and functions were unless they used them everyday.

    It is harder to do right but optimized workflow will win User's.

    I've been told by well over 50 individuals that they won't change to BaseCamp because of the regression in functionality compared to MapSource. Since I certainly don't talk to every potential customer for BaseCamp, I have to believe that there are a lot of people out there who will never consider using BaseCamp given the current feature set: or lack there of.

    Cheers,
  • What has happened to the "show on map" button that was in the lower L pane? I know I can R click on a highlighted item in the pane but it was more convenient to have the button. Is there something I need to do/set to bring it back or was it removed from this version? Thanks
  • Former Member
    0 Former Member over 13 years ago
    What has happened to the "show on map" button that was in the lower L pane? I know I can R click on a highlighted item in the pane but it was more convenient to have the button. Is there something I need to do/set to bring it back or was it removed from this version? Thanks



    I'd like to see that button restored.

    That is the most common thing I do from that screen, so a right click is awkward.

    It does clean up the interface. Maybe a Command Key Shortcut would be a Good way?
  • Former Member
    0 Former Member over 13 years ago
    I'd like to see that button restored.

    That is the most common thing I do from that screen, so a right click is awkward.

    It does clean up the interface. Maybe a Command Key Shortcut would be a Good way?


    There already is a command-key shortcut (CMD+D). We'll look into making this more obvious in the UI. Right now the shortcut is shown in the View menu.
  • Former Member
    0 Former Member over 13 years ago
    Sure hope we'll see v3.3.1 released soon. My installation won't even "Export" data at this point - it use to! It will still "Send to Device" so I'm OK for a while.

    Cheers,
  • Are we still stuck with BC's inability to display multiple waypoints with their identical names? i.e.. some kind of folder structure to store them So that the names can appear the same in BC as I have named them on my 62st.
  • Former Member
    0 Former Member over 13 years ago
    Sure hope we'll see v3.3.1 released soon. My installation won't even "Export" data at this point - it use to! It will still "Send to Device" so I'm OK for a while.

    Cheers,


    I believe you're on what's commonly called "the bleeding edge"! :)
  • Former Member
    0 Former Member over 13 years ago
    Sure hope we'll see v3.3.1 released soon. My installation won't even "Export" data at this point - it use to! It will still "Send to Device" so I'm OK for a while.

    Cheers,


    I am curious how many items, or routes you have contained in your collection? My problems with the legacy version always started when my collection started to get large. I've not worked with any of the Intel versions long enough to have a Large collection, well not yet...
  • Former Member
    0 Former Member over 13 years ago
    I am curious how many items, or routes you have contained in your collection? My problems with the legacy version always started when my collection started to get large. I've not worked with any of the Intel versions long enough to have a Large collection, well not yet...

    I don't harp to much on CPU performance because most of the time I'm using my MacBook Air.

    I have two database (AllData.gdb) collections. One for my personal data and one for our business data.

    My personal data:

    Waypoints = 72K+
    Tracks = 6K+
    Routes = 284 (I don't use routes much at all)
    Photo Waypoints = 600+ and growing
    Geocaches = a few thousand and growing
    BirdsEye Imagery = 320+ and growing

    Maps Installed = 14 currently but it varies

    Key for me is the ability to segment my data into Folders and Lists so that I never (unless I want) have a huge amount of data displayed on the Map.

    The only performance issues I really have is the Map redraw speed of the current Beta. I thoroughly expect that to be fixed in the "released" version.

    Cheers,