Mac/Windows Software

Basecamp Windows BaseCamp 4.4.7 Is Now Available

BaseCamp 4.4.7 Is Now Available

Former Member over 10 years ago

BaseCamp is 4.4.7 now available and can be downloaded here:

https://www8.garmin.com/support/download_details.jsp?id=4435

Installation of this version will overwrite your previous BaseCamp installation.

Fixed not being able to insert track points at the end of a track
Fixed GPI files not being read from SD cards
Fixed not receiving FIT locations from the fenix 3
Fixed Trip Planner printout not showing correct times
Fixed error calculating statistics when multiple tracks are selected

Post here if you have questions.

The non-English language version of the software will be available through the in-application software update check shortly.

Please post any bugs you may find here.

Thank you all in advance for any feedback you may have.

0 Former Member over 10 years ago

Can you export your route and send me the file to [email][email protected][/email] and can you tell me what map you are using in that e-mail? I would like to reproduce here with your data if at all possible.

0 TXBobcat over 9 years ago

I'm not sure what the popups are all about as I have not noticed any. However, one thing that has ticked me off in the last few versions of Basecamp is how the purple line representing a route/trip (whatever you want to call it) path totally covers highway markers on the map. That makes it really lousy when reviewing a route to make sure it's doing what I want before sending it to the GPS unit.

Something I found out some time ago. If you have selected the route it will show up bright on the screen covering up the information. However if you click the mouse off the route it becomes lighter and you can see the information beneath the route

0 Former Member over 9 years ago

...if you click the mouse off the route it becomes lighter and you can see the information beneath the route...

It doesn't always work that way. This can be a problem sometimes, selected or not. The picture below shows the same route, selected and not selected.

0 Former Member over 9 years ago

Bug

Trip Planner wrongly adds 30 minutes to the last point of a trip when printing the itinerary.

To reproduce, create a simple two point trip and print the itineray.

0 Former Member over 9 years ago

Thank you for the feedback. I have entered a case for the 30 minutes issue.

0 Former Member over 9 years ago

Bug

In Trip Planner, when you select a waypoint from the left pane, the list scrolls all the way to the top, for no good reason.

If the list contains only a few waypoints this is minor, because they are all visible in the pane, but with long list of waypoints this bug becomes a major irritant, because it forces the user to scroll all the way down, again and again, with every small change you make.

To reproduce: create a trip with several waypoints, more than can fit in the left pane; scroll down to the bottom; select the last waypoint. The list will scroll up and the selected waypoint will become hidden below, forcing a manual scroll to the bottom.

0 Former Member over 9 years ago

Unwanted double CR/LF on export to CVS

Single carriage returns (CR/LF) in the text of waypoint Notes are exported by BaseCamp as TWO carriage returns when exporting to comma-delimited text (*.csv) and gpx.

So, when exporting to *.csv/*.gpx

a
paragraph like
this

Becomes

a

paragraph like

this

0 Former Member over 9 years ago

Crash on export to a locked file

BaseCamp crashes when exporting to a file that is locked by another application.

To reproduce: open test.csv with Excel; in BC export to test.csv; BC will ask permission to overwrite; say yes; BC will crash.

0 Former Member over 9 years ago

Trip Name on export

If I create a trip in Trip Planner, BC gives it the default name "Trip to xxxx". If I change the name of the trip to something else, say "My trip xxx", Trip Planner accepts the new name and displays the new name everywhere within BC, as it should. So far so good.

But, if I export the trip the resulting gpx file retains the old name ("Trip to xxxx"), not the new ("My trip xxx").

For reference, see the node <tmd:TripName>.

0 Former Member over 9 years ago

This is likely because the name given trip planner is really for just display but the underlying data is still referenced by the default name. I'll investigate and find out if this is by design. Thanks for the feedback.