Jump to content

intolerable

+Premium Members
  • Posts

    1556
  • Joined

  • Last visited

Posts posted by intolerable

  1. I didn't really know Brian, but seemed a very nice guy the few times I met him. Earlier today, I saw that a local comic store posted some kinds words about him also and I thought I'd share that I had. He's obviously someone who will be missed.

  2. Alright, I've been downloading Birdseye to my SDcard pretty constant since I've signed up for it. As of the last couple, I can only get approx 106MB/5300 images before it states that the limit is exceeded. Where as in the past I've gone up to 400MB and 13000 images on one map. My resolution setting has always been High, not Low or Very high. What do I need to do to get back to downloading larger areas again?

     

    Could it be that the latest Basecamp update changed this? Although, since the update, I think I had a download at near 400mb/13000+ images. Or maybe I need to clear my list of already made maps to do larger areas again? Of course, then I wouldn't know where my areas were, and my be downloading the same images again............ The smaller downloads are obviously quicker time wise, but I like to let my computer work for me while I'm sleeping or working, as the download times are around 8 hours that way.

     

    Any help please?

     

    I think they have just simply changed the limits on what we can download. For what it's worth, since the change and with the last update, I've managed to download more in the last few days than I have collectively since launch. No time timing out and having to restart, which is nice when restarting sometimes meant having to completely restart...

  3. i thought i read that garmin connect was supposed to be able to read the heart rate monitor information recorded by the oregon and colorado, so you might want to try uploading a tracklog there to see if that's the case. apparently this was not the case on motionbased, but was supposed to be a feature introduced with connect. i'd be interested in knowing if it does.

     

    connect.garmin.com and accounts are free

  4. Still think they should take the QA guys (or whoever does the regression testing) and stick THEM in the seats to answer calls today as their penance for releasing this code!

     

    I can tell I've been using Facebook too much lately, as my brain was immediately screaming, "'Like' it! 'Like' it!"

     

    Sadly though, I don't think you can really blame the QA guys for this. It all seems so horribly flawed that I think only management/business could have made the poor decision to release...

  5. I thought all was going good, updated my Colorado, then basecamp, then grabbed a birdseye area that finally wasnt too big, but boot up the gps and first thing it says is invalid birdseye file....

     

    I received the 'Invalid Birdseye File' error when I transferred the Birdseye data onto the SD card rather than my Oregon's internal memory. Putting it onto the device worked without issue for me. Also, once on the device, I was able to cut/paste the Birdseye directory from the device and onto the SD card and then use it without getting the error.

  6. I had the same problem and was concerned it was just not doing anything. I opened up the directory where the data is stored on my Garmin and could see that it was indeed moving stuff over... it just takes an *amazing* amount of time to move very small amounts of data... hopefully they will address the many issues quickly and will add some sort of progress bar so we'll at least have some idea that something is indeed happening and maybe even some idea how long it'll take to happen...

  7. Also note - Birdseye imagery seems to be available for INTERNAL MEMORY only, no SD Card downloading. I picked an area just bigger than Metropolitan Toronto and ran out of device memory to put it in. Not sure I'm interested in the low res Birdseye for geocaching ... so I am envisioning a lot of downloading.

     

    All you have to do is "cut" the "BirdsEye" folder from internal unit memory and paste it onto your SD card. It will load.

     

    I just saw the cut/paste method for getting Birdseye onto SD cards over at the Garmin forums and tried it out. Fortunately, you don't have to cut the entire folder, as it takes *a long* time to transfer to the device and then to the SD card (so you don't have to do it all at once). Works though.

  8. Well, this is sort of out now... software updates for the compatible units and a software update for BaseCamp (at least for PC) have been released. I've managed to download some imagery and transfer a chunk of 'low' quality data to my Oregon 400t and I have to say... wow. The 'low' quality data looks excellent. Really impressed and wish that I was able to purchase a subscription...

     

    The new BaseCamp is working well and the imagery I am downloading is great too for the US. You can download anything you want in BaseCamp. It will send a small 'demo' file of Birdseye imagery to your Oregon. Can't figure out why Garmin isn't selling subscriptions yet-- I am ready to buy!!! Garmin, please add an "add to cart" icon on the Birdseye page so we can subscribe.... Please!!!

     

    Wow! Great imagery, looks great on the Oregon 300! Super easy to use...just draw the box on the screen and it downloads...waaaaay easier than the DeLorme map-cutting and downloading. I have screenshots but don't know how to post them.

     

    It is really easy to select and area and download and looks really impressive.

     

    So far, it appears that once you select an area and download that selection, you have to send it to the device all as one selection and cannot send just part of it (like selecting only half of the imagery). Hopefully this is just something I haven't figured out yet.

  9. Well, this is sort of out now... software updates for the compatible units and a software update for BaseCamp (at least for PC) have been released. I've managed to download some imagery and transfer a chunk of 'low' quality data to my Oregon 400t and I have to say... wow. The 'low' quality data looks excellent. Really impressed and wish that I was able to purchase a subscription...

  10. Tracklog elevation gain will differ from the total ascent reported by the altimeter (although I'm not sure how the former is calculated).

     

    FWIW, I've always found the total gain reported by my Oregon 400t to be off compared to my 60CSx, which usually gives extremely accurate results.

     

    Yes, on the Oregon, total ascent and elevation gain appear to be two completely different numbers. It's frustrating, because elevation gain from a tracklog from the Vista makes sense whereas the Oregon is some incredible number that makes no sense whatsoever (elevation gain is usually over a 1000ft more than actual gain)

     

    If I take the Oregon tracklogs and look at them in Sportracks, the climb +/- makes sense and are what i would assume elevation gain and loss would be, but they aren't.

  11. Is elevation gain and total ascent the same thing on the Oregon? That seemed to be the case with my Vista HCx, but on my Oregon, it's consistently drastically different.

     

    An example is a recent hike where I made track logs with both the Vista and the Oregon. The Vista ended up with a elevation gain of 1541 ft, which is right around what I know we hiked. Also, throughout the hike, the Oregon's elevation profile 'total ascent' reflected what would be the correct number and at the end of the hike was pretty close to the Vista's 1541 ft.

     

    But when I check the elevation gain for the track log on the Oregon, it's 2,276 ft elevation gain. We walked around town the other day and did around 600 ft according to the elevation profile, but when I get home and look at the track log, it's showing up as 2,559 ft???

     

    Anyone have any ideas what I might be doing wrong?

  12. I've been trying to update but keep getting a corrupt file error. Any suggestions? If it matters, encountering issue on both 32 and 64 bit Win7.

    I'm getting the same error. I emailed Garmin, waiting for a response...

     

    I was just about to do the same after trying on a WinXP machine and receiving the same error. Thanks for noting here :-)

     

    This is probably happening because your unit is not in mass storage mode when connected to your computer.

     

    As for the magenta goto line issue my 550t and DK 20 came up w/o any issue. My 400t did not work however I was able to get it to work.

     

    On my 400t I had the default topo maps and the US TrailMaps Whitewater maps enabled (I had many maps disabled). When I disabled the Whitewater maps the goto line started working. Reenabling these maps didn't seem to cause the problem to happen again so it sounds like some sort of initialization problem. But if you are seeing the issue I would play around with the maps you have enabled to see if you can get it to work.

     

    I assumed, apparently incorrectly, that it shouldn't be in mass storage mode (when connected to USB and not in mass storage, it correctly identified my unit and reported updates, so figured that was correct way :P ) I did update to 3.5, just bypassed WebUpdater.

     

    On my 400t, updating from 3.42, lost the go to line also.

  13. Custom settings and purple navigation all OK on my oregon 300 under 3.5. I also came from 3.42.

     

    What maps are you using when the line vanishes?

     

    No Magenta "Go To" line here either on 400t. Using CN NT v2010.1, all other maps are disabled.

     

    I'm suddenly glad I keep getting the corrupt file error...

     

    I updated my 400t from v3.4 to the 3.42 beta, but still just corrupt file error for me.

  14. Last week we received the first coin to cross our path in far too long. Thanks gardengorilla, we loved the Gardengorilla Goes Bush coin!

     

    Especially appreciate it as it's got us all excited to get back out there caching after a (too) long break... As soon as mightyzinn saw it he was all "let's go!" :-) It's just what we needed to get us back in the game!

  15. Can't get the broad view that was available the other way. If you back the view out on the maps you end up with an exceeded 500 caches message. In Google Earth it would show fewer caches but maintain relative densities. Cities showed more caches that rural areas. A good overview that you could then zoom into.

     

    Also was very nice being able to use the other features of Google Earth, such as planning routes, seeing the terrain, being able to view any number of overlays, all at once.

×
×
  • Create New...