Quote from: slarti76 on December 21, 2017, 09:27:07Just for confirmation: Only happens in the Walk profile (I didn't realize at first, because the icons for Walk, Hike and Climb are the same). I tried a car profile (in the mountains), there I immediately get an error message. The message is a little technical "target island detected for section 0", but I assume it's coming directly from BRouter. Anyway, seems to be something wrong with Walk profile, still.
3.Something wrong with BRouter integration: When I try to force him to a track that BRouter doesn't recognize, Locus doesn't display an error message, but the "Wait circle" turns forever. I can't compare this exact location with old version anymore (why do I always have to update all devices at once?), so it might not be new in this version... Is this related to the Release Notes entry "Problem with Locus-based Walk routing in BRouter"?