Related

BaseCamp 3.3.0.3 Beta available

Former Member
Former Member
We decided to release another Beta before 3.3.1. This release fixes some of the shaping point issues for Zumo 4x0 and 5x0, so we are especially interested in feedback on that (please use https://forums.garmin.com/showthread.php?t=24732 to provide feedback regarding that topic). We also fixed some other issues, and added a few more features that weren't done at the time of the first Beta.

Download the Beta here: http://developer.garmin.com/apps/BC/BaseCamp_3.3.0.3_Beta.exe. If you used 3.3.0.2, you should also be able to update from within BaseCamp.

If you haven't tried 3.3.0.2, make sure to check out https://forums.garmin.com/showthread.php?t=24413, there have been a lot of changes!

Change list from BaseCamp 3.3.0.2 to 3.3.0.3
  • Fixed zumo 5x0 and 4x0 route transfer issues. Note that this may cause route transfer issues on the zumo 660. A future firmware update on the 660 will address this issue
  • Update waypoint references to map data when recalculating routes. Advice for the first beta that said that shaping points only worked for brand new routes can now be ignored
  • Added hiding of Activity profiles
  • Added creating OpenCaches from waypoints
  • Added calculating ascent and descent for direct routes
  • Added indication of data filter visibility state on the data list
  • Change to prevent property dialogs becoming lost off screen after screen resolution changes
  • Fixed any profiles from BaseCamp 3.2 that have invalid routing preferences (ie invalid vehicle types and incorrect avoidances)
  • Fixed list in-place rename requiring pressing enter to complete the edit
  • Fixed the "Reset Headers" context menu being displayed after renaming an item
  • Fixed issue writing out altitude when exporting to the GDB file format
  • Fixed track filtering "automatic mode" for tracks with no time information


Known issues
  • Doing a “Send to” from the root device folder to “My Collection” crashes. This is when selecting the entire contents of the device in the folder list, and only when selecting the root My Collection in the folder/list picker dialog.
  • Sending geocaches to some of our older devices (first generation Oregons and older) fails when there aren’t already geocaches on that device (a geocaches.gpx file).


These will be fixed in the final release.
  • Former Member
    0 Former Member
    Falagar,

    Thanks for checking into my problem. Do you think in time the support for my unit could be added to BaseCamp?

    Mark


    I can't promise this, because waypoint category support for Garmin-mode devices would have to work quite a bit differently. But we'll see what we can do. It definitely won't make it into 3.3 (we've pretty much wrapped up that version).
  • Former Member
    0 Former Member
    Wow, I've been humbled. As tech savvy as I am, I never thought I'd have to mess around with default windows theme settings to "un-hide" windows highlighting in cases like this...... Problem solved!

    It's actually the reason I generally don't mess around with default display settings like this in the first place. I'm wondering (suspect) whether some other program (during installation) changed this 3d setting to white/clear?[/INDENT]

    THANK YOU!

    I've never changed any of the setting of the default theme, and before doing this there was no highlighting in this particular situation. (Selecting an item in the list did highlight, so I thought it was a programming oversight.) ~ I wonder what else I may have been missing over the years.... :eek:


    RE:
    Absolutely no indication of any outline exists on this win-7 Pro 64bit system. It a standard aero theme, 1920 x 1200 using standard /medium (125%) dpi text sizing. (nvidea discrete video card) ~ HMMMM...


    1. Let's say you have My Collection selected. When you click on the map with the pointer tool, is My Collection still highlighted?

    2. You can tweak the Windows color to see if BaseCamp is not working properly, or if the highlight color is just not noticeable on your monitor.
    a) right-click on your desktop -> Personalize
    b) click Save theme to save your current settings
    c) click on Window Color (at the bottom)
    d) Advanced appearance settings...
    e) change 3D Objects -> Color 1 to yellow
    f) change Window -> Color 1 to blue
    g) apply the settings and BaseCamp should look like this:


    If you're seeing something different, please post a screenshot.
  • Former Member
    0 Former Member
    Route Avoidances

    Hi,
    Will Route Avoidances, similar to that in Mapsource, be included in the new release of BaseCamp?
    Thanks
  • Former Member
    0 Former Member
    Message to FALAGAR

    Just wanted to let you know that some (many?) of the windows default themes assign the 3D color attribute to white. When this occurs, it effectively hides the background shading/highlighting within the list. (when user is selecting items from the map)

    Absolutely no indication of any outline exists on this win-7 Pro 64bit system. It a standard aero theme, 1920 x 1200 using standard /medium (125%) dpi text sizing. (nvidea discrete video card) ~ HMMMM...

    UPDATE: There is no outline appearing on previous version (non beta) either. (never was) I wonder if the method used is just not supported property of the video card. This was a top end graphics card in it's days a few years ago. Possibly even aero is the problem, who knows?

    Can anyone else confirm this problem on Windows? - Select a waypoint from the map (using the pointer tool) in Basecamp, and see if the waypoint gets outlined in the lists. ~It appears in the search box at bottom, but it does not become outlined (highlighted etc.) in the list directly above.
  • Former Member
    0 Former Member
    Hi,
    Will Route Avoidances, similar to that in Mapsource, be included in the new release of BaseCamp?
    Thanks


    No, that feature didn't make it into BaseCamp at this time.
  • Former Member
    0 Former Member
    Just wanted to let you know that some (many?) of the windows default themes assign the 3D color attribute to white. When this occurs, it effectively hides the background shading/highlighting within the list. (when user is selecting items from the map)


    I am glad we could identify what caused what you were seeing. We'll take a look if there is something we can change.
  • 0
    I just installed 3.3.3

    at end of installation, with the check box selected to launch BC, BC opens fine.

    If I close BC and try to reopen, I get an error log. I reinstalled BC (and rebooted my PC), and the same thing... launches once, then error.

    Here is the log, which I sent using the utility the pops up

    App: BaseCamp
    At: 1/13/2012 5:44:27 PM (UTC)
    OS: Windows 7 (64-bit) Service Pack 1
    Processor: x86, Processor Level: 6, Processors:4, Model: 26 Stepping: 5, RAM: 12565732
    MAP.DISPLAYCOLLECTION_T.{CTOR}-1288-3.2.2.0

    External component has thrown an exception.
    at map.DisplayCollection_t.{ctor}(DisplayCollection_t* , MapFactory_t* )
    at bc.MapDisplayCollectionImpl_t.{ctor}(MapDisplayCollectionImpl_t* , MapDisplayCollection_t aMapDisplayCollection)
    at bc.MapDisplayCollection_t..ctor()

    *** Outer Exception:
    Exception has been thrown by the target of an invocation.
    at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck)
    at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache)
    at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache)
    at System.Activator.CreateInstance(Type type, Boolean nonPublic)
    at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
    at System.Type.InvokeMember(String name, BindingFlags invokeAttr, Binder binder, Object target, Object[] args)
    at clr.Singleton_t`1.get_Instance()
    at bc.MainForm_t..ctor()
    at main(String[] aArgs)
    .NET 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 Unknown


    edit: tried to uninstall beta and reinstall 3.2. Cant get 3.2 to run at all now. Reinstalled 3.3 and can get it to launch once at end of install... but thats it
  • Former Member
    0 Former Member
    I apologize for the trouble. Can you post an error log for 3.3.0.3? The one you posted is for 3.2.2.

    And out of curiosity, can you try running BaseCamp as an administrator and see if it makes a difference?
  • Former Member
    0 Former Member
    Bulk Lists...

    Successfully imported almost 400 Lists at one time into my collection without issue. Would really appreciate a new feature in the product to allow multi-select on lists or alternatively direct import into a selected target folder. Extremely painful to organize bulk Lists one at a time :( .
  • 0
    I apologize for the trouble. Can you post an error log for 3.3.0.3? The one you posted is for 3.2.2.

    And out of curiosity, can you try running BaseCamp as an administrator and see if it makes a difference?


    thanks for the reply. I've got egg on my face. The icon on my desktop was pointing to 3.2. So, once the Beta was installed, it was generating the error. Once I went in and saw there was a different "beta" icon under Garmin, I was able to launch the Beta successfully.

    Sorry about that.
Copyright © 1996-2025 Garmin Ltd. or its subsidiaries