However, I was really using yesterday's planned ride as a test for Audaxes. To swap calculation methods, of course, you have to know the points at which you need to do that. That rather prevents your using the GPS to do all the navigating.
For your own use? or for constructing a route for sharing?
You might consider just making a Track instead:
* Do your autorouting thing in Mapsource, temporarily disregarding the off-road bits. Save it.
* Use WinGDB3 (free utility) to convert this to a Track. 1-click process. Reload in Mapsource.
(Or use Google Maps, or Bikely, to get to this stage)
* Downsample to <500 points (or split the track into sections).
* Use the Track edit tool to cut out the wrong bits and draw in the correct path at these places.
* Name and
colour the track, and save it.
* In the GPS, maybe use 'Trackback' to follow the track - this puts up turn prompts and bleeps, similar to a Route, whenever it detects an upcoming change of course of more than about 30 degrees.
For sharing, I've come round to the view that a Track is much more appropriate than a Route. If someone wants a Route (as I certainly would), it is better all round if they construct their own, by all means using the shared Track as a template. This is why only Tracks were offered for LEL recently.