BaseCamp 4.2.0.4 Beta is available

Former Member
Former Member
You can download the new Beta at http://developer.garmin.com/apps/BC/BaseCampBeta_4.2.0.4.exe or, if you already have an earlier 4.2 Beta installed, you can update from within BaseCamp. There have been quite a few changes, so it should be worth checking out:

Added various improvements and fixes for Trip Planner
Added support for changing the location of BaseCamp's database
Added ability to create waypoints from Yelp find results. Note this only works if you are using a map with address search capability
Fixed an issue where roads from the base map were displaying along with roads from the detailed map
Fixed an issue where BaseCamp was not displaying properly localized map labels
Fixed an issue with inverting mixed-mode routes
Fixed an issue with certain file names for Adventures and Garmin Cloud
Fixed various find issues
Removed Utilities menu, moved Options to Edit menu, created main menu entries for Adventures and BirdsEye
Removed maps drop-down box from default toolbar, also removed sub-menu for maps, maps are now directly accessible from the Maps menu

As usual, we are very interested in your feedback, please report any errors you might encounter. Thanks!
  • Former Member
    0 Former Member over 12 years ago
    Tried a couple of times but the Beta version will not start once loaded.
    Says Windows has a problem with the application, searching for a solution to the problem.
    Then blank screen and nothing happens. ??

    Leif/Sweden
  • Former Member
    0 Former Member over 12 years ago
    Hi,
    I have the same issue as DANDEMAn described...
    First inserted way-point is OK, the next one you add does not insert in the selection but between 2 other way-points.
    Cheers
    Luc
  • Just ran into a new (to me) search issue. Using BC Beta and CNNA 2013.4 I searched for the city of Waynesville, NC using the Find Options/Points of Interest/Cities. The map was recentered to clearly show Waynesville, NC in the center but the search results list shows "No results found". Several others cities I searched for seemed to work correctly. So far, I can only reproduce the problem using Waynesville, NC.
    The released version of BC works correctly. It shows a populated list containing Waynesville plus a number of other locations.

    Never mind. I had to reboot my PC for another reason and now I can't reproduce the problem so I guess it was a local issue.
  • Former Member
    0 Former Member over 12 years ago
    With BaseCamp 4.2.04 Beta when I insert additional waypoints into a route, I click on the route so I know I'm at the correct point along the route, then click on the insert point icon, then rubberband over to the new waypoint to be inserted and click on it.. Works fine on the first inserted waypoint, in that it goes into the proper place (order) in the route with respect to other waypoints already in the route.

    However if I pull the rubber band over to a 2nd nearby waypoint to be inserted, instead of placing that waypoint following the 1st one inserted, it inserts the 2nd waypoint down the route (skipping forward) over several existing waypoints in the route. In last case I tested, it inserted the 2nd waypoint down past two existing route waypoints. And of course when the route is recalculated, with the second inserted waypoint out of order, it creates a route backtrack.

    I haven't had this happen using the same procedure with BaseCamp 4.1.2

    btw with the maps loaded on the computer instead of accessing them in the attached 3597, I don't get the crash I reported earlier when using the insert point icon..

    thanks


    This should be fixed in the 4.2 non-Beta release. Thanks for reporting.
  • Former Member
    0 Former Member over 12 years ago
    New issue just popped up for me in 4.2.0.4 (win7 computer)

    All has been working good except for a few crashes when moving way points (sent error report in on that a while back).

    The new issue is when I close then re-open 4.2.0.4 Base Camp doesn't remember the folder I was working out of, it also re-opens with the data filters closed.

    It (4.2.0.4) basically opens on a different list with the waypoint list showing & the data filter closed.

    It just started doing this for me lately so something has changed. (might be route I have imported or a list name or ???)
  • Former Member
    0 Former Member over 12 years ago
    This should get fixed for 4.2.1 (the first "real" release of BaseCamp 4.2).

    Thanks for letting us know.
  • Former Member
    0 Former Member over 12 years ago
    How do users 'file' bug reports and other issues?

    Falagar,
    Do you have a 'formal' way for (beta and regular) users to file bug reports?
    Or do you just read posts in the forums?

    BTW, I know that Garmin's software team have their own tools that they use for planning software and tracking issues.
    But I'd like to recommend Jira from Atlassian Software as something you might check into.
    It's a great tool; I've used it internally in several organizations where I've worked.
    The reason I mention it is because it is very easy for organizations to set it up to allow its software users to create accounts and file issues themselves. A great example is Atlassian itself - they have a Jira system set up for all their software for their users to use. Give it a look!

    Meanwhile I'll give the new/beta release a try. I hear you've added some ability to control the location of the database.
    -cj

    This should get fixed for 4.2.1 (the first "real" release of BaseCamp 4.2).

    Thanks for letting us know.
  • Former Member
    0 Former Member over 12 years ago
    Falagar,
    Do you have a 'formal' way for (beta and regular) users to file bug reports?
    Or do you just read posts in the forums?

    BTW, I know that Garmin's software team have their own tools that they use for planning software and tracking issues.
    But I'd like to recommend Jira from Atlassian Software as something you might check into.
    It's a great tool; I've used it internally in several organizations where I've worked.
    The reason I mention it is because it is very easy for organizations to set it up to allow its software users to create accounts and file issues themselves. A great example is Atlassian itself - they have a Jira system set up for all their software for their users to use. Give it a look!

    Meanwhile I'll give the new/beta release a try. I hear you've added some ability to control the location of the database.
    -cj


    Thanks for the question and your feedback.

    There is a "Send Feedback" option in the Help menu for our Betas. That is probably the best way to give feedback (ideally you'd send feedback for each issue separately). The forums work as well, I try to make sure that each feedback item gets transferred into our bugs/features database. It's just a bit more work for me. If you send feedback, a case gets created automatically.

    Also, if you notice crashes, please report the crash in the error dialog that will hopefully come up. All errors that are reported in that way get automatically recorded and accumulated in our system. You are helping us even more if you provide steps to reproduce the crash.

    I am afraid that Garmin has probably no plans to make the feature/bug tracking open to the public.

    P.S. Garmin is certainly no stranger to Atlassian's tools. We use them quite heavily.
  • Former Member
    0 Former Member over 12 years ago
    old habits die hard .....

    Thanks for the info about how to send Feedback, bug and crash issues.

    Not surprised that you use Altassian tools.
    Was not suggesting that you open your system to us users (that way lies disaster!).
    But a parallel system of only user input might be considered.
    People could see if issues had been reported; they could add to existing issues; user workarounds could be posted.
    It would require

    Sigh ... I stopped when I realized that it requires the users to think like QA engineers.
    They would need to categorize the issue correctly (assuming Garmin defined all the appropriate components in Jira) to see if the same issue already existed. It so, add new info accordingly. If not, then create a new issue, categorizing it correctly (computer system/version, BC version, software component(s), specific feature(s) etc ...). Filing discrete issues and not saying "searching doesn't work". Provide steps to reproduce. Otherwise you just get a lot of garbage.

    But then again, perhaps you could identify people on the various forums who provide good feedback and make them a deal. Instead of opening up the user issue system to anyone, it is somewhat 'by inviation'. But then again, maybe you already have a cadre of folks who do real world user beta field testing and give you that kind of feedback.
    Sorry, I just put on my old QA manager hat and got carried away.

    Now I'm off to download beta software!
    -cj

    Thanks for the quest and your feedback.

    There is a "Send Feedback" option in the Help menu for our Betas. That is probably the best way to give feedback (ideally you'd send feedback for each issue separately). The forums work as well, I try to make sure that each feedback item gets transferred into our bugs/features database. It's just a bit more work for me. If you send feedback, a case gets created automatically.

    Also, if you notice crashes, please report the crash in the error dialog that will hopefully come up. All errors that are reported in that way get automatically recorded and accumulated in our system. You are helping us even more if you provide steps to reproduce the crash.

    I am afraid that Garmin has probably no plans to make the feature/bug tracking open to the public.

    P.S. Garmin is certainly no stranger to Atlassian's tools. We use them quite heavily.
  • Hello,

    I seem to experience a problem when £I import GPX data into Basecamp BETA. Everytime I try this, Basecamp shuts down. Opening the report dialog. I get my gpx tracks from different sources for hiking, e.g. Routeyou and the like. Using BETA 4.2.0.4 revision 38519 on Windows 8.
    Does anyone else have this problem?