I have turned off recalculation for testing purposes, using latest Trekking-poutnik.brf profile template.having GPS off, screen of Locus placed near of the middle of the route.

If the route is generated by Brouter and imported as GPX file , it works as expected, switching between navigation ( hints ) and navigation-guidance ( question mark ), if I move the pointer around the route.

If the same route is calculated via Locus navigation interface, it switching to pure Guidance mode ( The guidance icon )and will not revert to navigation when on the route.

Edit: Also, for route calculated via the interface, there are not displayed the hint points........

Thanks Poutnikl... as written my tests without installed brouter app. (I'll wait to install until reports = 99% stable).Sometimes (rarely) using Graphopper experimental until now. Not seen such behaviour. ( Well, or I did not notice because always using autorecalculation = on while using grapHopper) Thanks for observation and report. Willy.

Question: (hints missing ?) Do you mean exported that track into gpx file (or tcx ?) and then reimported ?

I have not mentioned any export. Also, BRouter does not generate TCX. Brouter can pass the route to Locus Either as GPX to import, either via Locus navigation API. The latter probably chokes on the hints for now.

Route generated by BRouter as GPX and then imported to Locus from MapItems is fine, with hint points attached to route and navigation<>navigation-guidance works fine - as worked well before for testing Locus and Brouter versions..

The issue I found for Locus Brouter Interface routing. Hint points are NOT placed on the route and Navigation switches to pure Guidance mode.Like if Locus interpreted somehow the route provided via interface like guidance waypoints set.

Edit> Perhaps I have misinterpreted a Menion notice the interface is hint ready, as it was not before yet.He may have just meant he GENERALLY uses Brouter only via interface, but interface is not hint ready yet.

I know brouter has no direct tcx output...but Locus has. I reported (without brouter app !) no changes in new Locus 3.17 version standard behaviour. Andrew said: I never had that issue before...but before there where no hints generated ? Anyway you pointed to the exact brouterapp/Locus combination problem..so nice report.

I have not mentioned any export. Also, BRouter does not generate TCX. Brouter can pass the route to Locus Either as GPX to import, either via Locus navigation API. The latter probably chokes on the hints for now.

@poutnikl - no I am pleased to say that Locus displays the hints (you mean waypoints as navigation commands?) when track generated with BRouter is imported via Locus navigation API.

I know brouter has no direct tcx output...but Locus has. I reported (without brouter app !) no changes in new Locus 3.17 version standard behaviour. Andrew said: I never had that issue before...but before there where no hints generated ? Anyway you pointed to the exact brouterapp/Locus combination problem..so nice report.

Before, hints were generated by Locus from the route shape only.

GPX based hints are fresh, but worked for last few Brouter and Locus updates.

API based hints were added just recently, I have not experiment with them until now.

Thanks 0709. That's very interesting that you could go into navigation mode with my long track. To my surprise I could go into navigation mode with your test track 100% reliably too (attached). That now suggests to me the bug has something to do with the imported track. Not much to do with any Locus navigation or guiding settings. @Menion, are you following this discussion?