BaseCamp 4.4.4 Is Now Available

Former Member
Former Member
BaseCamp is 4.4.4 now available and can be downloaded here:

http://www8.garmin.com/support/download_details.jsp?id=4435

This release does not support XP.

Installation of this version will overwrite your previous BaseCamp installation.

Here are the changes made in this version:
  • Fixed several issues when using the Pan Tool and the <ALT> key to move route points
  • Fixed autorouting issue where straight line segments were inserted after each waypoint
  • Improved track to route behavior. Now supports preserving the shape of track sections that aren't near a road.
  • Improved handling in situations where the computer is low on memory
  • Changed displayed route times to take layovers into account
  • Fixed issue with 'higher education' map symbols showing up as airports
  • Fixed certain instances of route direction text where the text was 'turn left/right' instead of 'bear left/right'
  • Fixed issue when recalculating a route via the context menu in the data list
  • Fixed various issues sending data to memory cards
  • Changed to automatically unlock BirdsEye for a device when sending the BirdsEye to a card in that device
  • Fixed various issues with Adventure search
  • Fixed issue sending ADM files to cards for marine devices
  • Added the command line option /Disable3D to disable the 3D view in BaseCamp. This was added to prevent startup issues with misbehaving graphics drivers.


Post here if you have questions.

The non-English language version of the software will be available through the in-application software update check shortly.

Please post any bugs you may find here.

Thank you all in advance for any feedback you may have.

*4.4.3 as a version number was skipped to be in-line with the Mac version.
  • Former Member
    0 Former Member
    Yes, straight lines are fixed.

    But an old issue is still there:

    Issue: BaseCamp 4.3.3 recalculating an existing route, using the same map, is creating a longer route, having duplicate route segments and sometimes loops.

    This is a newly created Route (used for testing straight lines) and consists of two via points only. Route reverses back on its own trail.
    The second and last via-point is not regarded as last via-point by BaseCamp. So Route extension (by [Insert]) is not possible.

    This is one of the same locations where the straight lines issue did occur. Straight line route was identical to the current black [Insert] line.
    Issue is related to map being used: OpenStreetMap, more specific OpenFietsMap. Not to be reproduced on "OSM generic routable". Not to be reproduced on "City Navigator Europe NT 2008".

    The issue is not to be reproduced in MapSource.



    Is it possible for you to attach your gpx file to an e-mail sent to [email][email protected][/email] so that I may look at your route to see what is going on? Do you need assistance with this? I would like to be able to help you. Thanks!
  • Regarding the problem Ankeric mentioned: this seems to be map-related. The problem didn't occur in a previous version of the open bicycle map (OFM), nor in any other map. Mkgmap might be causing this. The maker of OFM is checking with mkgmap. If you want to check yourself you need to download a current version of OFM at www.openfietsmap.nl.
    But again: this probably is not a basecamp bug.
  • Former Member
    0 Former Member
    I assume those maps are 3rd party?
  • Correct. OSM-based.

    The map discussed above is the OFM. The maker of that map replied to this thread too. Pls. have a look at the quality of his (free) product; it's broadly used in Europe.
  • :)

    2.
    Via's are mostly set to 'alert on arival' automatically. It would be MUCH better is 'won't alert' would be default; esp. for motorcycling.
    Is it possible to change the default-setting? (would be happy to explain why current default is a major problem for many users).


    If "won't alert" meant that it would not alert I would agree with you. I don't know if this is different with different GPS units but with an etrex 20 and a GPSMAP 64s it will alert you ether way. The only difference seems to be the text that is displayed. I have found that as long as it's going to drive me nuts beeping I might as well have the better text displayed.

    I don't know if this is a bug in BaseCamp or the GPS. I have talked to tech support about this and he reproduced the problem using a GPSMAP 64. He agreed it's a bug and opened a case. I have not heard back.
  • It is different for for various devices. My understanding is that Basecamp adds a bit of code to tell the device not to announce, and not all units can use the code. For example, it has no effect on a Zumo 660 but does work on the newer Zumo 590.
  • I'm not seeing that ... see my screenshot above.


    Are you using CNNA 2015.3?

    1. On the first search after launching BC I get numerous tags appearing on the map but only a few entries in the list. The few entries in the list have duplicates. Selecting show more will remove the duplicates.
    2. After quitting that search and starting a new search with the same parameters I see a fully populated map & list but with the first 3 entries duplicated (1&2, 3&4, 5&6). Selecting show more will remove the duplicates.
    3 Quitting BC and relaunching starts the behavior over at # 1.


    To duplicate this center on Hickory, North Carolina and search for Food & Drink with subcategory Pizza.

    I tried to include a screenshot but something goes wrong. Is there a max size for an image inserted from the local computer? Any tips on inserting a screenshot?
  • If you build a new route in the correct mapversion for the zumo660 it will work too and won't announce the via's. What goes for the 590 goes for the 3xx and BMW nav5 too.

    BUT:
    The anouncement is not the main issue here:
    Let's call the announced points 'hard via' and the 'won't alert' points 'soft. - So: hard and soft via's:

    1.
    The newer units accept a max of 30 hard via's. If you download an existing route from the internet it's almost certain it contains 100 or more via's . The route often will be split in the device; sometimes is a lot of parts.

    2.
    There is no need for that: the new zumo's will accept a sequence of 125 soft via's! After every hard via the count starts again. So: the zumo's can accept thousands of via's in one route as long as we hve one hard via per 125 via's

    3.
    Hard via's are obligate to visit. If you have a via somewhere in a detour, but came back onroute further on: the zumo will keep sending you back to the missed via(s). You can use 'skip via' but that leads to full recalculation of the route; ingnoring orininal basecamp settings. This downgrades garmin to tomtom level (!)

    4.
    If you needed to leave the route; e.g. to get gas, and return back to it; even if you have the auto-recalculate shut-off: if you miss a hard via you will not have any (spoken or not) navigation instruction (untill you go back 10 mls to touch that 'missed' via).

    5.
    There is NO need for hard via's; except if it e.g. is a lunch stop. In Europe we use a via every approx 3 km or so. Does Garmin think we are that hungry that we have to meet up every 3 km's (2mls?)!!??

    So..... pls change the 'default' to 'won't alert' (and show you understand how your software is used....).
  • Former Member
    0 Former Member
    I've tried the update, extracting went well, however during the installation when the green bar was at appr. 60% it crashed displaying 'MSI Error: InstallFailure'. So far I have found no possibility to go back to a previous version (trying to install version 4.2.5 leads to the same error), trying to restore the computer to a previous point didnot fix the issue either.
    Any suggestions/solutions?
  • Former Member
    0 Former Member
    Uninstall everything (Back up your data first) and start from scratch with a fresh download and a fresh install. This happens to a few users and we are still not sure why. The work around for now is to just uninstall everything and start over. You won't lose your data but back it up just in case.