GPSrChive Discussion Forum

Thank you!

If I may ask, did you reported that issue too?

I am still researching this issue, as I suspect this is actually a limitation of BaseCamp being old and not updated while the Montana is much newer.

Most of the current Garmin GPSr were updated recently to prohibit using certain characters in track/activity names to resolve another issue, and this included the "." amongst others.

Now they need to update BaseCamp to also not allow the use of these same characters, or, leave it as is, and let the device 'substitute' with a default valid character to replace the "." when present.

gpsrchive wrote: Wed Aug 11, 2021 11:35 pm Most of the current Garmin GPSr were updated recently to prohibit using certain characters in track/activity names to resolve another issue, and this included the "." amongst others.

Could you tell me more? Which issue is supposed to be fixed here?

gpsrchive wrote: Wed Aug 11, 2021 11:35 pm Now they need to update BaseCamp to also not allow the use of these same characters, or, leave it as is, and let the device 'substitute' with a default valid character to replace the "." when present.

I am not sure, what Garmin will do. The last info, they replied to me, if they will be able to replicate, they will open a ticket. Nothing more heared.

ConiKost wrote: Thu Aug 12, 2021 6:29 am

gpsrchive wrote: Wed Aug 11, 2021 11:35 pm Most of the current Garmin GPSr were updated recently to prohibit using certain characters in track/activity names to resolve another issue, and this included the "." amongst others.

Could you tell me more? Which issue is supposed to be fixed here?

For some background information, see this Garmin GPSMAP 66i Forum post.

Also, read the second to last line in the firmware 5.30 change log at GPSrChive > Montana 7x0 > Firmware, or this GPSrChive Forum Post.

Only thing that matters is that those characters are not valid for use with track names (on the device), and when importing tracks that have them, these devices will substitute another character for them.

gpsrchive wrote: Thu Aug 12, 2021 11:25 pm For some background information, see this Garmin GPSMAP 66i Forum post.

Also, read the second to last line in the firmware 5.30 change log at GPSrChive > Montana 7x0 > Firmware, or this GPSrChive Forum Post.

Only thing that matters is that those characters are not valid for use with track names (on the device), and when importing tracks that have them, these devices will substitute another character for them.

Well okay, but this was changed long ago, so clearly, this is something different, as otherwise, the archived tracks have been shown already different in older firmware versions, which was not the case.

Based on the latest answer from Garmin, this is supposed to be correct, as this would be related to automatic/manual save of tracks. Tbh, I don't understand that, what they exactly mean.

gpsrchive wrote: Wed Aug 11, 2021 11:35 pm Most of the current Garmin GPSr were updated recently to prohibit using certain characters in track/activity names to resolve another issue, and this included the "." amongst others.

It seems, the change it not fully done. While you cannot save a new track with a dot in name, you can still rename it afterwards to have a dot in name.

ConiKost wrote: Fri Aug 20, 2021 10:11 am

gpsrchive wrote: Wed Aug 11, 2021 11:35 pm Most of the current Garmin GPSr were updated recently to prohibit using certain characters in track/activity names to resolve another issue, and this included the "." amongst others.

It seems, the change it not fully done. While you cannot save a new track with a dot in name, you can still rename it afterwards to have a dot in name.

This still applies for firmware 10.50.

Garmin software engineers have been advised.

Thank You!