Related

BaseCamp 4.3.0.2 BETA is Now Available

jm47048
over 11 years ago
BaseCamp 4.3.0.2 BETA is now available and can be downloaded here:

http://developer.garmin.com/apps/BC/BaseCampBeta_4.3.0.2.exe.zip

You will need to unzip the file before installing.

This release does not support XP.

You do not have to uninstall BaseCamp 4.2.5 and it will not overwrite that installation. The BETA and an official release of BaseCamp will live side-by-side but must be used separately. However the 4.3.0.1 BETA will be replaced.

Below is a list of changes. This is only a BETA release.

Added “Find Intersection” to the Find menu
Added parsing of the primary find text into address search fields
Improved ordering of auto-complete results
Improved street auto-complete results when searching for streets with prefixes and suffixes
Improved some usability issues with address and intersection searching
Improved recovery from corrupted cache information from device maps

Post here if you have questions.

The BETA is currently only for English users.

Before using this release, back up your data.

Please post any bugs you may find here. This release is to assist us in testing with a wider user base and wider set of devices. Bugs may be present, and any feedback is welcomed.

NOTE: We are aware of several issues with address searching on devices. We ask our users to please test this very well and let us know of the issues you find. Some of them will be duplicates of issues we have already found, but the advanced address search is new for this release and we need a good test bed to be sure that the feature is working correctly when we do the full release.

Again, thank you for all who participate.
  • 0 over 11 years ago
    For me, BC has now replaced MS.


    Whatever floats your boat :)

    ...
    Another one bites the dust
    And another one gone, and another one gone
    Another one bites the dust
    ...
    Queen, 1980
  • 0 over 11 years ago
    " />">
    I am able to produce this artefact with my 1GB sized map of the alps:
    1. Open Basecamp Beta and the map: result: no problem
    2. Close Basecamp Beta, open Basecamp and open the map: no problem.
    3. Close Basecamp and open Basecamp Beta and the map: Now you will find such an artefact in some sizes.
    4. Close Basecamp Beta and delete the folder "user\xxx\appdata\local\garmin\Basecamp" and reopen now Basecamp Beta: the atrefacts have disappeared.

    Obviously Basecamp and Basecamp Beta use the same cache with different rules.
  • Former Member
    0 Former Member over 10 years ago
    Erasing or moving a Via-Point brings BaseCamp to recalculate the whole Route. This ist not practicable.
    A Via-Point has a wrong Name after moving.
    ViaPoints can not have the same Name. For Example Highway 27 is used 5 times, the Via Points names "Highway 271"...This ist wrong.
  • 0 over 10 years ago
    The via point name should likely be fixed. I will open a case.

    Routes though will recalculate after moving a via.
  • Former Member
    0 Former Member over 10 years ago
    ...

    Routes though will recalculate after moving a via.


    Is this really necessary? Insert a ViaPoint recalculate only a Part of the Route, not the whole Route.

    Route:
    A - B - C - D - E

    remove or delete C -> BC recalculate from A to E
    insert x between C and D -> BC recalculate only between C and D
  • 0 over 10 years ago
    Does it really matter? Isn't the end result the same? I suspect the BC team have far bigger matters to worry about :)
  • 0 over 10 years ago
    What you could do is set your routing type to "Direct" while you're adding/removing/moving points (so BC doesn't recalculate) and change it back to what you want when you're done. Then recalculate the route once your points (waypoints/vias) are where you want them. Rinse and repeat as needed :D
  • Former Member
    0 Former Member over 10 years ago
    Does it really matter? Isn't the end result the same? I suspect the BC team have far bigger matters to worry about :)


    A 55km MTB-Route takes 18 sec to recalculate. This is unnecessary, cause the result is the same! 18 sec is a long time to wait. That sux!
  • 0 over 10 years ago
    The routing algorithms need a frame of reference in order for the next waypoints to be correctly calculated going forward. Going to direct first and doing all of your edits before a recalc will ultimately solve that problem. The calculations are the same as on the devices. We use the same algorithms.
  • Former Member
    0 Former Member over 10 years ago
    What you could do is set your routing type to "Direct" while you're adding/removing/moving points (so BC doesn't recalculate) and change it back to what you want when you're done. Then recalculate the route once your points (waypoints/vias) are where you want them. Rinse and repeat as needed :D


    I want to see promptly wich way the Route takes ;)