Related

BaseCamp is USELESS

Former Member
Former Member
** UPDATED **

BC cannot dispaly the Recreational Map of Europe (BaseMap) from my 550T. Crashes EVERY time the basemap is clicked on. Im running OpenGL 1.5 which is more than enough and have more than enough resource for the app to run. But it refuses to display any internal mapping of my 550T despite numerous reinstalls. Each time BaseCamp will quit after trying to display the BaseMap. In addition BaseCamp cannot import Garmin KMZ files as advertised, making BaseCamp totally useless for mapping!

Here is the Dump BC produces. (As yet Ive had NO reply from Garmin past few days).


App: BaseCamp
At: 01/04/2010 20:41:12 (UTC)
OS: Windows Vista Service Pack 2
Processor: x86, Processor Level: 6, Processors:2, Model: 15 Stepping: 11, RAM: 2086584
UNKNOWN-0-3.0.1.0

.NET FW Versions:
.NET FW 1.0 not installed.
.NET FW 1.1 not installed.
.NET FW 2.0 with SP2 installed
.NET FW 3.0 with SP2 installed
.NET FW 3.5 with SP1 installed

OpenGL Version:
OpenGL Version 1.5

Selected Map Product:
Recreational Map of Europe

Installed Map Products:
Name: Trip and Waypoint Manager v3
Id: xxxxxxx
Version: 3.0
Name: Global Map
Id: xxxxxxxx
Version: 2.0
Name: Recreational Map of Europe
Id: xxxxxxxx
Version: 3.0


Not enough storage is available to process this command
at System.Drawing.BufferedGraphicsContext.CreateCompatibleDIB(IntPtr hdc, IntPtr hpal, Int32 ulWidth, Int32 ulHeight, IntPtr& ppvBits)
at System.Drawing.BufferedGraphicsContext.CreateBuffer(IntPtr src, Int32 offsetX, Int32 offsetY, Int32 width, Int32 height)
at System.Drawing.BufferedGraphicsContext.AllocBuffer(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.AllocBufferInTempManager(Graphics targetGraphics, IntPtr targetDC, Rectangle targetRectangle)
at System.Drawing.BufferedGraphicsContext.Allocate(IntPtr targetDC, Rectangle targetRectangle)
at System.Windows.Forms.Control.WmPaint(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.SplitContainer.WndProc(Message& msg)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at bc.MainForm_t.HandleProductChanged()

*** Outer Exception:
Exception has been thrown by the target of an invocation.
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at bc.MainForm_t.WndProc(Message& aMessage)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at main(String[] aArgs)


Attached File: MiniDump

  • Former Member
    0 Former Member
    ZHENKLE,

    I managed to successfully update to the latest graphics drivers using your link! Unfortunately the problem with BaseCamp is still exactly the same! It even crashed on launch! Other times it runs but crashes immediately when i click on the BaseMap or select it from the pull down menu.

    I’ve checked other important drivers on my system and BIOS, and everything is up to date on a clean system.

    Update: Upon checking my system resourse monitor, I can see BaseCamp is using way too much memory.. averaging 75-80% when idle. This is crazy! I think BC needs a re-work, and fast!
  • Former Member
    0 Former Member
    Glad that the upgrade worked for you. I'm sorry that it couldn't solve the issues you were seeing with BaseCamp. We're continuing to work on all of the crashes we've seen so far in 3.0.1.

    I'll post again if I have any further updates or suggestions.
  • Former Member
    0 Former Member
    my help files don't show up.

    when i click on "help" up comes a normal help screen but when i click on ANY of the topics the html code ONLY shows up.

    i've done a dump and wipe, a fresh download and reinstall but still the same error.

    actually, if its not hooked up to my oregon 400t it doesn't keep any of what it apparently initially downloaded from the unit.

    i'm running windows 7 ultimate 64bit.
  • Former Member
    0 Former Member
    I have to agree

    I was able to make one custom map by using BaseCamp 3.0.2 to import a kzm file from Google Earth. Now I am trying to add another, but I get an error message saying "cannot import". I've tried reducing the file size (I understand 3 MB is the limit and I've tried much much less than that) and the image size, keeping below 1K by 1K. Tried KZM and KML. Tried setting opacity to 100%. Tried setting drawing order to 50 or 51. Tried copying the file into the \Garmin\CustomMaps folder on my Dakota. Tried changing the file name to remove the spaces. Tried everything I can think of.

    But hey, here's an idea. How about if BaseCamp gives me a tiny little clue about why it cannot import a file. For example, if the file size is too big, say "cannot import the file because the JPG image exceeds the maximum size of 3 MB." Is that so hard? I don't think so. One of the main reasons I bought the Dakota 20 was to use custom maps. Between the sparse documentation and buggy software, that feature is barely usable. I'm feeling nothing but frustration with Garmin today.
  • Former Member
    0 Former Member
    I think we've gotten as much as we can from the original discussion that started this topic. If you have additional issues please create a new thread.
  • Former Member
    0 Former Member
    Sorry didn't mean to cut you off Ireton. Improved KML import (with better error reporting) is a feature we're working on for an upcoming version of BaseCamp.