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 2.1.1 Beta posted

This update should fix Snow Leopard garbage characters, the symbol picking crash, and a few other issues. It also adds full sync data support for the Oregon 550s and Dakotas. Get it at http://www8.garmin.com/support/download_details.jsp?id=4732

The only reason this is called a beta is because there is crash that can occur when making long routes on Topo 24K map products. Fixing this issue will probably take a couple of weeks minimum, so we released this as a "beta" for now, as Snow Leopard users are justifiably tired of waiting.

As with all betas, we suggest you back up your data by exporting or you can copy the files found in ~/Library/Application Support/Garmin/BaseCamp/. You don't need to copy the directories, only the files. Once you update to this version, you shouldn't run the previous version, as the data files are not backwards compatible.
  • I hope the maintenance release comes before Basecamp 3.0 because I cannot afford to invest in an Intel processor mac at this time.

    It is my understanding that it will be in a Zumo firmware maintenance release. I'll give more details when I get them.
  • Former Member
    0 Former Member over 15 years ago
    Well this little thing gets more interesting the more I learn.

    Since I found out that i can use the invisible shaping points with my Zumo 550 within BaseCamp.

    I have found out if i prepare a route with the invisible/unannounced shaping points I can transfer and import those routes with my 550 and there is no problem navigating it, and the incredibly high milage thingie does not happen either. If I settle for the BaseCamp generated autoroute, or if I do not hold down option key while dragging the route the High milage bug shows up and if I hit the Go button on a route like that the Zumo 550 turns itself off.

    Another one of The things that make you go Hmmmmmmmm.
  • Former Member
    0 Former Member over 15 years ago
    Topos?

    Although I can upload and download data from my Oregon 400T with my waypoints and trails, I don't have the Topos on BaseCamp. Should the topos be visible on my Mac desktop?
  • Former Member
    0 Former Member over 14 years ago
    I cannot get the Zumo to turn itself off even using your data, though I can recreate the 25,000 mile error. I am sending the data onto our device team and see if they can figure out what is going on. I will say that I tried long routes other places and it didn't have the same issue. I suspect that there is map data around that area that is causing a hiccup in BaseCamp's gpx output code. In the meantime, if you recalculate the route once on the Zumo before pushing GO the problem should go away.

    I believe for the most part, BaseCamp works fine for sending routes to a Zumo. If other people are experiencing problems, please tell us.

    Edited: I forwarded the info about the 25,000 mile route to the Zumo software team and they indicated that they plan on fixing it in a maintenance release.


    Hello there,

    On this side, same issue when I create a route with BaseCamp (for Ppc)
    and transfer it to my Zumo 660 software 3.90
    The facts:
    Create a 75km route from point A to point B with 5 stops. Reviewing in BC all is fine but when I transfer it either to the 660 or the sd card the total distance goes crazy -> 9.128 Km :eek:

    Though I can it the GO button it doesn't turn the unit off, it looks like it will get me there but that crazy amounts ok Km just still there!

    If I recalculate the route it gives me some 8.900 km...

    Don't know if it is ok to answer this post which is few months old or better to start a new one?

    Cheers from Belgium
  • Former Member
    0 Former Member over 14 years ago
    UP please !

    In fact, no matter what route I create with BaseCamp none will be transferred to the SD card on the 660 with the correct distance. Just tried a route from my home to Maastrich (Holland) the correct distance is 86 km.

    When transfer done it shows 5700 km:mad:

    What to do... ?

    Would be gratefull for any help other than suggesting me to buy a Pc or a Mac (intel)

    Many thanks
    Bernard