Latest version. Problem 1: The route from Phoenix, AZ to Flagstaff, AZ leaves I17 on 69 and returns to I17 on 169. How do I get S&T to stay on the much shorter I17 route?Problem 2: The route from Homer, AK to Whitter, AK uses the marine ferry to Kodiak, AK. This is the shortest driving route but otherwise unacceptable unless one wanted to go to Kodiak. How do I get S&T to stay on paved roads other than adding additional stops?I've tried various S&T options to resolve this but maybe I missed some?

You can drag and drop a portion of the route to any highway. -Tom

Make sure you don't have any intermediate stops set in the Prescott area. You could also ask for a route between two points close to the 69/169 detour, maybe even the two intersections. There is, for a example a grade on that stretch of I17. Or maybe it has information (maybe old) on construction or blockage on that piece.Regarding the Homer to Whittier route, it could be that it lacks information the tunnel drive to Whittier. My old copy of S&T sends me through Anchorate and Valdez. What does it recommend when you add a waypoint near Portage Glacier?In the big picture, look at issues like shortest route v fastest route, tolls or not etc. But if a mapping program refuses to send me along a particular road, I play around with destinations close to that road, trying determine whether that road is in its database or not.

I think you found a flaw in the program.I use this program a lot and have not seen this before.Talking about the Flagstaff & Phoenix route.Pat

In your route planner, have you gone to "more Options" and changed it to "shortest route"?Have you set your "preferred roads" option?Whittier to Homer put in an intermediate stop, say Sterling.

I ran the Pheonix to Flagstaff route on 2013 S&T and it showed the route all on I-17. After changing the preferred route to to like other roads, the route changed to the SR69 and SR169. Changed the preferred route to dislike other roads and interstate to like, still SR69 and SR169. Shortest and fastest the same. It is a bug!

MS S&T Issues | Good Sam Community

27 Replies

CA_Traveler
Explorer III
Sep 28, 2013
GordonThree wrote:
CA Traveler wrote:

Problem 2: The route from Homer, AK to Whitter, AK uses the marine ferry to Kodiak, AK. This is the shortest driving route but otherwise unacceptable unless one wanted to go to Kodiak. How do I get S&T to stay on paved roads other than adding additional stops?

I've tried various S&T options to resolve this but maybe I missed some?

Right click and drag to draw a box around some of the land/sea encompasing the marine highway, and then right click again and choose avoid area. This will stop the auto router from choosing the marine highway. I found this bug too while routing from Glennallen thru Anchorage to Seward and then back to Anchorage.
I did exactly that. Thanks for confirming this bug.
GordonThree
Explorer
Sep 28, 2013
CA Traveler wrote:

Problem 2: The route from Homer, AK to Whitter, AK uses the marine ferry to Kodiak, AK. This is the shortest driving route but otherwise unacceptable unless one wanted to go to Kodiak. How do I get S&T to stay on paved roads other than adding additional stops?

I've tried various S&T options to resolve this but maybe I missed some?

Right click and drag to draw a box around some of the land/sea encompasing the marine highway, and then right click again and choose avoid area. This will stop the auto router from choosing the marine highway. I found this bug too while routing from Glennallen thru Anchorage to Seward and then back to Anchorage.
paulj
Explorer II
Sep 25, 2013
At leasts S&T isn't sending you across a Fairbanks runway!

Apple Maps flaw results in drivers crossing airport runway
mfinnerty
Explorer
Sep 20, 2013
The issue is the software gives the wrong route and any override you try will not assign the preferred route. I knew where I wanted to go but the DW got confused when following the strip map I printed. One of those "you're supposed to turn off here" as I pass the exit.
john_bet
Explorer II
Sep 19, 2013
mfinnerty wrote:
paulj wrote:
You are allowed to take an exit even if S&T won't route you that way. :)

In the Montana I15 case, what route did S&T give you?

Exit at 193 instead of 192. Exit 193 is Cedar St which changes to Airport Rd. Then right at Carter Dr and left at US12/287. That segment is set to "Preferred" with arterial roads disliked.
What was wrong with using the Prospect Ave exit? I used 12/287 a few years ago from Three Forks going North to Helena and got right on I-15N without using a gps.
mfinnerty
Explorer
Sep 19, 2013
paulj wrote:
You are allowed to take an exit even if S&T won't route you that way. :)

In the Montana I15 case, what route did S&T give you?

Exit at 193 instead of 192. Exit 193 is Cedar St which changes to Airport Rd. Then right at Carter Dr and left at US12/287. That segment is set to "Preferred" with arterial roads disliked.
jmckelvy
Explorer
Sep 19, 2013
CA Traveler wrote:
Latest version.

Problem 1: The route from Phoenix, AZ to Flagstaff, AZ leaves I17 on 69 and returns to I17 on 169. How do I get S&T to stay on the much shorter I17 route?

Problem 2: The route from Homer, AK to Whitter, AK uses the marine ferry to Kodiak, AK. This is the shortest driving route but otherwise unacceptable unless one wanted to go to Kodiak. How do I get S&T to stay on paved roads other than adding additional stops?

I've tried various S&T options to resolve this but maybe I missed some?

I also experience #1 with S&T 2013.

I DON'T experience #1 with S&T 2010. 2010 does show construction on the segment that 2013 routes around. My 2013 does NOT show construction on that segment.
paulj
Explorer II
Sep 19, 2013
You are allowed to take an exit even if S&T won't route you that way. :)

In the Montana I15 case, what route did S&T give you?
mfinnerty
Explorer
Sep 18, 2013
I ran into a similar issue this summer mapping my return home from Glacier NP. No matter what I tried MSS&T would not show a direct exit from southbound I-15 to eastbound US12/287.
CA_Traveler
Explorer III
Sep 18, 2013
Rats

Tried the 2013 est files on 2008 and they produce a error. So just entered the routes and they are OK on 2008.

But now 2013 will not display any driving directions. Looks like I'll need to delete both versions and reinstall 2013.