This may apply to all versions of BC but I am on 4.4.6 and 2015.30 mapset today.
Test trip in BC using "Curvy Road" option from Silver Spring, MD to Tuscaloosa, AL basically routes down on mostly not very "Curvy Roads" to about Lynchburg, VA then after that its Interstate 81 and Interstate 75 the rest of the way to the destination. It seems to ignore the "Curvy Road" directive after a point and then focuses on fastest time to destination. I see this behavior on the majority of "Curvy Road" long distance routes created this way within BC.
On the other hand when routing this same trip on the Zumo 590LM directly, it works great and keeps one on as many non interstate and curvy backroads as practical that exist along the whole way (routing via Blue Ridge Parkway and other similarly sized two lane twisty backroads). Both Basecamp and Zumo have similar avoidances set.
Just wondering if the "Curvy Road" logic in the BC software will be examined for further refinement in later versions? Can the routing logic used in the Zumo 590LM (firmware 2.80) be ported back to Basecamp? I prefer to create routes in BC first then move to Zumo. In the case of "Curvy Road" routing the Zumo direct routing works better than Basecamp, but I cannot get that route back to BC for study before embarking.
