Base Camp issues

Routes transferred from Base Camp to my Nuvi 3790 LMT, now show some of the route not on the road but a straight line between to points and in one spot it shows both the real route and a straight line between to points. The route is correct in Base Camp. Travel time in Base Camp is 8 hours 5 minutes, but the Nuvi says 11 hours 55 minutes.

Have you tried recalculating the route on your device? Are your routing preferences and road and feature avoidances set similarly between BC and the device?

Were you using the device's maps in BC when you built the route, or do you have maps installed on your computer? If the latter, are the versions the same between the computer and the device?

Adding or deleting stops to a route, resets the date and time for everything back to the date and time on your computer.

This is with the route open in BC, using the new trip planning features? It's possible to get it confused if you work backwards through the route; also possible to give it conflicting constraints. Sometimes when it gets confused it sets the time to "now"; kind of like running home to momma. You might want to read this from another post (can't find the thread, but this was my summary):
I can't figure out exactly what it's doing either, but I totally concur that its ability to magically support Don's "work backwards" planning is limited (and buggy) when there's an intervening waypoint.

I did manage to get it to work by helping it out a bit.

Scenario: We're meeting some friends for lunch at the Hard Eight BBQ in Stephenville at 12:00. On the way there, we want to stop and have coffee with some other friends at Storm's in Lampasas. When should we plan to meet in Lampasas?

First, I set the 12:00 arrival time for lunch. I observe that BC now tells me to leave Storm's (coffee) by 10:42 to make it to the lunch on time. OK, so I manually then "lock in" the departure time at Storm's for 10:42, and manually set the arrival time at Storm's for 10:00 to allow 42 minutes for coffee. Then BC will automatically calculate my departure time as 8:43 to make it all work.

I have to manually set the departure and arrival times at the intermediate waypoint or it will not work correctly.

If I set only the arrival time for coffee at 10:00, it will show me leaving there at 10:00, which obviously is not what I want. In other words, it will not magically calculate a layover time to get me to lunch exactly on time. Fair enough...that might be asking a little much of it.

If I set only the departure time for coffee at 10:42, it gets totally wigged out, and shows me arriving there (at coffee) at 7:10. That corresponds to its calculation of 1:18 from my starting point, if I leave now. This is what Tom saw...it freaks and wants you to leave right now. Kind of like a nagging spouse (not mine, of course).

So here's my takeaway. If you want to use Don's approach to ride planning, working backward from arrival times, you need to do it a piece at a time. Set your arrival time, then work backwards through each waypoint, locking in its departure time to whatever BC calculated, and setting its arrival time to allow for whatever layover you want. It seems to work just fine using multiple waypoints, each with potentially different arrival and departure times (I'm avoiding using the term layover time to avoid confusion with the "layover time" setting in BC).

Corollary takeaway: don't try to use the BC "layover time" feature if you're planning backwards.

How do I get my custom waypoint icon/images back into the window to select?

Sorry...don't understand the question. Can you elaborate?

Re: your route problems, can you isolate the behavior by just putting a single, simple route over on the device? Does that work OK? As you add more and longer routes, at what point does the problem appear?

If you want to post a gpx file I'll be happy to load it up and see if I can find any issues with it.

Re: the waypoint symbols...sorry, but I've never messed with that. I just use the defaults.

This route is one day of driving part of the Blue Ridge Parkway. This section was the hardest to keep me on the Parkway and not be sent over to the expressway, so I have a lot of waypoints, but below the 200 max.

I also tried creating the route on the Nuvi using the Favorites sent from Base Camp and the Nuvi kept me on the expressway the entire time.

I took the Base Camp GPX and put it in Map Source and sent it to the Nuvi - same problem.

The GPX file is correct, the turn-by-turn instructions are correct, the display has something wrong since the Base Camp upgrade.

I then changed the Nuvi navigation calculation on the device from "FASTER TIME" to "SHORTER DISTANCE" and recalculated the route and it fixed the problem. I then set the calculation mode back to faster so it didn't change the other routes on the device or new ones being added.

This change did NOT fix a small section along I-95 at Palm Beach from skipping across a bend in the road, but all of the rest of the route is right on.

ATTENTION GARMIN: add a calculation button to all devices that says "FOLLOW BASE CAMP ONLY AND OVER-RIDE ALL DEVICE SETTINGS"