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.

0 Former Member over 15 years ago

Oops, I should have said [email][email protected][/email].

Thanks, I resent it.

0 georg-l over 15 years ago

Thanks for the beta of BaseCamp, Team Garmin!
I was eagerly waiting for a RoadTrip update on my SnowLeo Mac, since the recent version of RoadTrip killed all my tracks/data.

So far BaseCamp runs smooth and it seems as it can replace RoadTrip completely.

Thank you for that pre-chrismas present! You guys made my day! :)

0 MattyTheGaul over 15 years ago

Strange... Take the post just above, swap RoadTrip with BaseCamp, and it'll give exactly my own situation... :)

But as long as RoadTrip works fine, it's OK for me. Just hope that I'll soon see a fixed version for BaseCamp as I miss the 3D.

Best regards,
Mathieu

0 Former Member over 15 years ago

Denny Henderson,
I am unable to recreate this problem with the Zumo. Please send your shaped route to [email][email protected][/email]. It would help if you would give your myGarmin forum tag in the email to help give it context. Thanks.

I received one message back from your team.

Did you experience the same route corruption when you imported that route to a Zumo 550? If you did not, then I must have some kind of problem with my Zumo and I need to figure out how to resolve that.

0 Former Member over 15 years ago

Hello, I'd really like to know if the file I sent you produced the same type of route corruption on your test unit?

All I have received is a confirmation that you received the route, still no information.

I received one message back from your team.

Did you experience the same route corruption when you imported that route to a Zumo 550? If you did not, then I must have some kind of problem with my Zumo and I need to figure out how to resolve that.

0 azdrmn over 15 years ago

Will manipulation of multiple waypoints be possible in the final release?;)

Editing multiple waypoints will not be in the 2.1 release. We plan on having that feature in BaseCamp 3.0.

0 azdrmn over 15 years ago

So the problem starts when I go to WhereTo > Routes

Select one of these Routes and hit GO......

The Zumo turns itself off ... black Screen...
same thing happened with both routes.

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.

0 Former Member over 15 years ago

Editing multiple waypoints will not be in the 2.1 release. We plan on having that feature in BaseCamp 3.0.

Great! It would be nice to know the scheduled release date for 3.0.

0 until 1st half of 2010
0 during 2nd half of 2010
0 2011 or later

or even the month if you like;-)

0 azdrmn over 15 years ago

While it is our policy to not comment on the schedule of future releases, Garmin has announced BirdsEye Imagery will be available in March and it requires BaseCamp 3.0. Given that, I can say that is is scheduled to be released in the first half of 2010.

0 Former Member over 15 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.

Thanks for the update I've been able to reproduce the Zumo turning itself off on every thing I've tried so far. Different locations, etc.

I tried the recalculate option, while that does allow the route to load
it changes the route, which is very undesirable.

I hope the maintenance release comes before Basecamp 3.0 because I cannot afford to invest in an Intel processor mac at this time.