Arrive Continue

Thank you.

No sweat. Glad to help when I can.

Great!!

BaseCamp 4.2.4 (which contains the fix) is in the process of being released. So if all goes well it should be out within the next 2 weeks.

That's assuming testing goes well and no catastrophic events occur (the usual caveat).

I'll keep an eye out. Thanks again....

Using the latest BaseCamp and my new RV760 I did not receive a continue problem. The route was from Amarillo to Oklahoma City.

BC

Using the latest BaseCamp and my new RV760 I did not receive a continue problem. The route was from Amarillo to Oklahoma City.

BC

And you may not have. This problem was specific to a very specific route maneuver that does not happen in all cases. It depends on where you were routing to/from, what map you were using, etc. The issue has, however, been addressed and BaseCamp 4.2.4 is currently in formal testing. Hopefully it will be out soon and those users that are having issues with it will hopefully receive a correction.

Thanks.

This may be related and I haven't read this complete thread so if it has been noted before, I apologize.. but this is an issue that a few of us have noted on ZumoForums...

I have noticed this on routes that were previously created on older mapsets in Mapsource, I imported them into BC and looked over and fixed a few shaping points that were no longer right at an intersection (due to older mapset, etc. and of course it recalculates the route numerous times as I do this) I then sent the route to my Z660(which is set to NOT RECALCULATE) in Mapsource (as I have no confidence in transferring routes via BC!) then I'm riding along and all of a sudden I have caught the route "recalculating" (and I was totally following the route) with no warning/voice message and then sometimes after the recalculate it just continues on it's way, no issues.. but I have also noticed at other times it recalculates and then I've received this message: "Unable to calculate route. Destination not on the road." If I just restart the custom route, along it follows and everything is fine. These are perfect routes... all shaping/via/waypoints properly placed and again, my Zumo is set to NOT recalculate. I have noticed this only since installing BC 4.2.3

Begs the question ...

Does it do the same when you do everything in BC and don't import routes into BC from Mapsource, adjust them, recalculate them, send them back to Mapsource and then send them to your zumo :confused:

TBH I'm not surprised your method introduces the odd error :)

SUSS,

Well, that behavior is only since the 4.2.3 update and I am not the only one that has noticed it...

I've done that "reprocessing" of my routes many times... It is a PIA, but it "makes sense", at least to my logic ;-), I have hundreds of older routes that I need updating due to mapset changes (hate "flagged" routes) and BC is very good at fixing/seeing off-placed (if there is such a word!) shaping points, but BC has a way of changing routes compared to Mapsource, so I also can compare the route back in Mapsource (against the original) to see if the route was changed. (BC seems to be more demanding of shaping points... which I actually think is a good thing when sharing routes across multiple platforms, i.e. different version GPS's, as well as different date mapsets) as well as I don't like transferring routes to my GPS in BC.

But, I can imagine it sure would sound like that could introduced the error, but NO, it has only happened (at least to me) since the most recent "upgrade".