Garmin Adventures

Former Member over 13 years ago

Any scheduled maintenance on the Garmin Adventure servers will occur Tuedays at 7:45am CT. Most maintenance down times will be less than 20 min. If you are experiencing an issue with adventures during this time, please try again later.

More on adventures here: adventures.garmin.com

New firmware with adventure support has been released for:

Montana
62 Series (includes 78 series)
Oregon x50 Series
Dakota

“Garmin Adventures” is a new feature that allows you to easily share trips and photos and lets you find Adventures by other Garmin users. You can download a track from your GPS to BaseCamp, add some photos, videos and annotations; upload the trip as an Adventure and then share it via the Garmin Adventures web site with friends and family. BaseCamp allows you to author Adventures, and use a playback feature so you can re-live your trip. In the near future, Garmin devices will add support for Adventures as well.

The BaseCamp 4.0.0.4 gives you an early preview into Garmin Adventures. Please let us know how you like it and what you think we can improve. BaseCamp 4.0.0.4 will lead you to short surveys that will help us make Adventures a better product. If you have a minute to spare, please fill out these surveys. Thanks.

Finding Adventures

You can use BaseCamp’s find feature to locate other Adventures. You can download Adventures that you would like to take a closer look at. If you'd like to follow an adventure, just transfer it to your device.

Adventure Display and Playback

You can view details about an Adventure, and use the Playback feature. The Playback experience will be better if you have a Topo map and BirdsEye imagery. Check out http://www.youtube.com/watch?v=8al8CHqOBmg for an example.

Creating an Adventure

You can create an Adventure from any track, either from My Collection or directly from your device. BaseCamp will locate photos and waypoints in the vicinity of the Adventure track. You can add annotations, YouTube videos and additional photos. It is important that you enter a good description so other can better experience your Adventure. Note that you can pick from the prepopulated list of activities or simply enter your own.

Each Adventure has its own database, so you can play around with your Adventure’s data without making any changes in your data in My Collection.

Publishing an Adventure

Once you are happy with your adventure, you can publish it. You can share a published adventure with friends and family (http://adventures.garmin.com/en-US/by/eracerz/hanakapiai-falls-trail-hike-2), you can link the adventure to your favorite social media site, you can use it to back-up your trip and download it again on a different machine and you can help fellow Adventurers find interesting stuff to do.

0 Former Member over 12 years ago

Alright, that gives me something to work with! We'll try to fix that for 4.0.3.

Thanks a bunch.

Thanks very much. Let me know if you need anything else.

0 Former Member over 12 years ago

Well, it turns out I still cannot reproduce this. Even with the photo you sent and without publishing the adventure.

This is what I am doing:

1. BaseCamp 4.0.2. Oregon 450 with firmware 6.00.
2. I am importing the image you attached into BaseCamp, and then draw a track near it.
3. I create an adventure from the track I have just drawn and add the image to the adventure.
4. I send the adventure to the device (without publishing).
5. I still see the photo when following the steps outlined in my post here.

If you follow these exact steps, does the photo not show up? If your steps differ, how do they differ?

Your help is much appreciated. Trying to fix something we cannot reproduce is difficult.

0 Former Member over 12 years ago

Well, it turns out I still cannot reproduce this. Even with the photo you sent and without publishing the adventure.

This is what I am doing:

1. BaseCamp 4.0.2. Oregon 450 with firmware 6.00.
2. I am importing the image you attached into BaseCamp, and then draw a track near it.
3. I create an adventure from the track I have just drawn and add the image to the adventure.
4. I send the adventure to the device (without publishing).
5. I still see the photo when following the steps outlined in my post here.

If you follow these exact steps, does the photo not show up? If your steps differ, how do they differ?

Your help is much appreciated. Trying to fix something we cannot reproduce is difficult.

I appreciate your efforts.

I am also running BC 4.02 and have an Oregon 450 running firmware 6.0.

The only thing I did differently was that I imported an actual track following a hike. I didn't draw a track. Would it be helpful if I sent you the actual track?

I'm stumped. I clearly did something right, because when I downloaded the published Adventure, the larger images appeared.

I anticipate creating another Adventure this weekend, so I'll see if this issue arises again. In the meantime, if sending you the track would help, I'm happy to do so.

0 Former Member over 12 years ago

I appreciate your efforts.

I am also running BC 4.02 and have an Oregon 450 running firmware 6.0.

The only thing I did differently was that I imported an actual track following a hike. I didn't draw a track. Would it be helpful if I sent you the actual track?

I'm stumped. I clearly did something right, because when I downloaded the published Adventure, the larger images appeared.

I anticipate creating another Adventure this weekend, so I'll see if this issue arises again. In the meantime, if sending you the track would help, I'm happy to do so.

I thought I'd go ahead and upload the track in question. I hope it helps.

Thanks again!

0 Former Member over 12 years ago

Quote Originally Posted by CHEESESPREADBUTTIES
I have also updated the firmware in my GPSmap 62s from ver 3.90 to ver 4.40 and I've got 2 "Adventure" icons in the menu! Any solutions?

I'll investigate. Sounds like a device firmware issue.

I have this email from a customer:

I have v4.50 in my 78s and I have just discovered a major problem with that version. The Photo Viewer application (a Main Menu item) is now gone from the unit. aaaaaaagh! I keep a lot of photos in the Garmin>JPEG folder and they used to be able viewed on the gps screen.

Now they can't! They can only be viewed if I connect the gps to my computer and look at them via Irfanview or some other Windows photo application. As most of the photos I have in the gps are spoilers or photos of intricate trail maps that I use to help find geocaches the loss of the Photo Viewer is hugely felt.

I note that the Main Menu now sports 2 icons for Adventures and I suspect one of the garmin gurus who has been responsible for that appaling development has cocked things up by usurping the screen space previously occupied by the Photo Viewer.

v4.40 was a complete cockup when Garmin introduced Adventures and v4.50 was an endeavour to fix things. However, they have stuffed that up too.

I would like to move back to v4.30. I know that that will involve the loss of all my settings, but I am prepared to have to reset everything.

The only copy of v4.30 that I have been able to find is a gcd file that needs WebUpdater to install. But how does one force WebUpdater to install an OLD version?

I have emailed Garmin about the loss of Photo Viewer but have had no response. Last night I checked with my brother who has 4.50 on his 62s and he confirmed that he has no Photo Viewer but has 2 icons for Adventures in the 62s Main Menu!!!

Two issues here - the faulty version 4.5 update and is it possible to revert to an older version in the meantime please?

0 atlas_cached over 12 years ago

I've attached one of the images.

And I can confirm that the workaround suggested above (to publish the Adventure and then to download the published Adventure) works. I can see the image.

So, just to recap:

1. I created an Adventure on my PC and transferred it to my Oregon 450. I can't see larger versions of the images in the device.

2. I publish the very same Adventure, then download the published Adventure and transfer it to my device. I can then see the images in the device.

Is the image you shared the exact same, unedited photo you imported to BaseCamp for your adventure?

0 atlas_cached over 12 years ago

The only copy of v4.30 that I have been able to find is a gcd file that needs WebUpdater to install. But how does one force WebUpdater to install an OLD version?

if you have the gupdate.gcd file, simply copy it to your GPSr\Garmin\ directory, and reboot with fresh (well charged) batteries. WebUpdater is not required for gupdate.gcd files. Let me know if you need more help.

0 Former Member over 12 years ago

Is the image you shared the exact same, unedited photo you imported to BaseCamp for your adventure?

Yes it is. The original image (which was not imported to BaseCamp) was taken with a digital camera and was much larger in size. I resized the image using Irfanview, preserving the exif data of the image. I then imported the resized image into BaseCamp. It is the resized image that I shared in my post.

Thanks.

0 atlas_cached over 12 years ago

Yes it is. The original image (which was not imported to BaseCamp) was taken with a digital camera and was much larger in size. I resized the image using Irfanview, preserving the exif data of the image. I then imported the resized image into BaseCamp. It is the resized image that I shared in my post.

Thanks.

Just for fun, could you take the time to import one of those same images into BaeCamp without prior modification in any form (perhaps give it a different name such as 'v2'), create a simple "test" adventure with that image, and send that Adventure to your Oregon, and see if the image is properly viewable on the Oregon?

0 Former Member over 12 years ago

I thought I'd go ahead and upload the track in question. I hope it helps.

Thanks again!

I tried out the track and it makes no difference. The photo is still showing up for me.

So I would echo BABJ615 suggestion. Is there any difference if you import the original photo to BaseCamp vs. importing the photo that was edited by IrfanView? It looks like the image is being properly sent to the device, but then it's somehow unhappy about it and doesn't display it. It's just strange that I cannot get my device to do what yours is doing.