BaseCamp has a long way to go!

I didnt see the purpose of closing down the "BaseCamp is USELESS" thread as the program clearly has a long way to go before even its basic functionality is working properly. ISSUES:

1. BaseCamp STILL cannot import Garmin KML files
2. BaseCamp still very, VERY slow on start up, and is STILL prone to crashing here.
3. OSGB Exp maps STILL do not show up on BaseCamp
4. Trying to display the BaseMap CRASHES the whole system.

So, apart from downloading BirdsEye maps (which is also still painfully slow), BaseCamp doesnt actually work!

I strongly suggest that Garmin SCRAP BaseCamp altogether and incorportate the BirdsEye functionality into MapSource. MS is time-tested app that worked on just about every computer I put it on.. BC is just a MESS and is 10 steps backward. BC just doesnt have any purpose to exist. PERIOD!

Hear, hear!
The program is still in Alpha stage, so they shouldn't be selling memberships to BirdsEye with BaseCamp implying that it's a finished product. Most annoying. But most of all, personally speaking, I am tired of using MapSource AND BaseCamp to do stuff that should be handled by one program alone. I always wondered why there are two programs performing the tasks of one, but before BirdsEye I just didn't care and never used BaseCamp. Now I have no choice but to use it. :(

I'd prefer if user with issues that haven't been address yet opened up a new thread instead of them getting buried on page 3 or 4 of a very broad thread.

• This is something we're already working on. We're adding the ability to import additional files that don't follow the KML standard and improving the error reporting when we cannot import.
  
• Our current efforts are focused on bringing down the memory footprint of the application which should also increase the speed and responsiveness.
  
• The maps can be read and used for routing, displaying the embedded raster imagery is still a work in progress and we hope to have a solution very soon.
  
• Still don't have an update on the graphics related crashes. One avenue we are exploring is related to how we are using memory but I don't have additional details at this time.
  

You guys are welcome to post what you want (within limits), but I'm not personally interested in having a "BaseCamp sucks, Map Source rules" discussion. As I've said before, we'd be interested in hearing what you can do in MapSource that can't be done in BaseCamp but we're looking for specific features or tasks.

I'm with the Basecamp developers on this one. The "basecamp sucks" crowd is not being constructive at all. If you would just report bugs as you encounter them it would make their job easier.

I agree, but...

I agree that threads about the software sucking and being awful, etc, are somewhat useless in themselves. Having people rant and rave about how bad the software is will not help matters.

I do however hope that the development team is taking the complaints seriously. I am sure that there are far more people who are experiencing performance issues with Basecamp that are not reporting them here or to Garmin's support number.

What bothers me is that I paid a $30 fee for a subscription for a service that I cannot reliably use because of software related issues.

I am hoping that the memory and compatibility issues are being investigated by Garmin's developers and not just being passed off as a few people with problems. No software is perfect, but it would definitely seem there is a considerable amount of people with issues. Hopefully Garmin recognizes this and gives us a better working version of Basecamp.

The curious thing is, I have had remarkably few problems, slowdowns or crashes running BaseCamp on my Core 2 Duo/2.8ghz Dell Inspiron with Intel integrated graphics, 6GB RAM and Vista 64.

This makes me think that BaseCamp is happier on 64 bit systems. Is there something in the code which would support that theory, or am I just lucky? :)

I'd prefer if user with issues that haven't been address yet opened up a new thread instead of them getting buried on page 3 or 4 of a very broad thread.

• This is something we're already working on. We're adding the ability to import additional files that don't follow the KML standard and improving the error reporting when we cannot import.
  
• Our current efforts are focused on bringing down the memory footprint of the application which should also increase the speed and responsiveness.
  
• The maps can be read and used for routing, displaying the embedded raster imagery is still a work in progress and we hope to have a solution very soon.
  
• Still don't have an update on the graphics related crashes. One avenue we are exploring is related to how we are using memory but I don't have additional details at this time.
  

You guys are welcome to post what you want (within limits), but I'm not personally interested in having a "BaseCamp sucks, Map Source rules" discussion. As I've said before, we'd be interested in hearing what you can do in MapSource that can't be done in BaseCamp but we're looking for specific features or tasks.

ZHENKEL,

If you look back at my threads you will see that I'd pasted application dumps and had tried to explain in detail the problems I was experiencing in a constructive way. If the title of my 'Threads' cause upset then to those users I say "Thats Your Problem" it got your attention!

Now, lets get to the nitty-gritty:

KML/Z STILL has an issue.. your remark here was the same before 3.0.2 release.. so its still not been addressed.

Raster Mapping not showing is a BIG issue. For many this will be the sole purpose to use BaseCamp to plan routes. This should have been working before BC's release. After spending hundreds of pounds on a Garmin GPS device, users will be understandably frustrated that they still cannot plan routes properly... what did you expect?

Stability issues affect just about everybody.. this is still a MAJOR issue for most by the looks of this forum.

So where does that leave me as a user? BaseCamp with NO map? What can I do with that? Come on.. ive spent over £700 on my Garmin GPS!

Issues reported by Phone to Garmin (Several times!).

I'm with the Basecamp developers on this one. The "basecamp sucks" crowd is not being constructive at all. If you would just report bugs as you encounter them it would make their job easier.

I second this. I do agree that having BaseCamp as the sole delivery vehicle for BirdsEye is a problem: Garmin shouldn't be selling subscriptions on a service that is not out of alpha or beta, however you want to define those terms. But I don't see how bashing the development team helps matters. On many a product forum, the developers lurk in the background, presumably so as to avoid getting constantly flamed. I'm pleased to see their active participation here and want to continue to encourage that.

I bought my Dakota 10 strictly for the Custom Maps feature--replacing an eTrex Vista. In my experience, the feature has worked remarkably well: delivered as originally promised, with substantial improvements (such as KMZ viewing on BaseCamp, thereby letting me dispense with Oziexplorer.) that go beyond my original expectations. I look forward to new revises and appreciate the conduit to participate in those revises.

I'm with the Basecamp developers on this one. The "basecamp sucks" crowd is not being constructive at all. If you would just report bugs as you encounter them it would make their job easier.

And what makes you think they're not doing so already?

One thing I do know. If I was a developer and saw a poster putting up posts like this, they would be on my ignore list in 5 seconds.

This is a great forum and the actual developers come on here trying to work through the problems. They work with a lot of constraints within their jobs that cannot be discussed here and the last thing they need is public abuse.

This is a great forum and the actual developers come on here trying to work through the problems. They work with a lot of constraints within their jobs that cannot be discussed here and the last thing they need is public abuse.

Well said - I completely agree. :cool: