Waypoints are ignored for route exported to Copilot

[mhw01]

Routeconverter is so easy to use. I use it to create routes on a pc and copy these .trp files to my phone for use with the Android Copilot app. I almost always insert waypoints to force the route I wish to use. For some reason, Copilot often ignores a waypoint and calculates its own quickest route.

The route initially looks correct when performing a Load within Copilot, with all the waypoints correctly placed. Then while actually driving, I notice that when a waypoint is passed and recalculation takes place, the next waypoint on the route may simply get ignored and a 'quicker' route is created. How is it possible for this to happen as I thought that all waypoints must be approached to within 200 feet? All the Waypoints on the route are far more than 200 feet apart and I have turned off Optimise final stop.
How is it possible for the app to ignore waypoints?

I have found that the only reliable way to force the route is by changing Waypoints to Stop points within the Android app. At present, Routeconverter always exports any route positions as Waypoints. Is it possible for points to be changed to Stop points?

Android Copilot  9.6.4.144

Ps: There was an old thread on the same sort of topic posted by Daisy -       Forum suggestion was to edit the windows registry and insert: [HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\copilot]"write/Targets"="true"

So does this mean Routeconverter will somehow change the trp files which get created? Into stops rather than waypoints?

[routeconverter]

Ps: There was an old thread on the same sort of topic posted by Daisy -       Forum suggestion was to edit the windows registry and insert: [HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\copilot]"write/Targets"="true"
[/font]
So does this mean Routeconverter will somehow change the trp files which get created? Into stops rather than waypoints?

Yes, that hidden option makes every position a stop target.

[mhw01]

Ps: There was an old thread on the same sort of topic posted by Daisy -       Forum suggestion was to edit the windows registry and insert: [HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\copilot]"write/Targets"="true"
[/font]
So does this mean Routeconverter will somehow change the trp files which get created? Into stops rather than waypoints?

Yes, that hidden option makes every position a stop target.

Thank you for that info. Exactly what I was trying to discover. I shall give this a test as I think it may be the easiest answer to the route forcing problem, ie just use stops. I am not sure how well this may work.

The thing is, it seems very odd that Copilot ignores waypoints in this way. A major error in the algorithms it would seem.
I have just received a reply from Copilot support regarding this error. If they can explain what is happening, I shall post any info back to this forum as it may help many other users.

[mhw01]

Ps: There was an old thread on the same sort of topic posted by Daisy -       Forum suggestion was to edit the windows registry and insert: [HKEY_CURRENT_USER\Software\JavaSoft\Prefs\slash\navigation\copilot]"write/Targets"="true"
[/font]
So does this mean Routeconverter will somehow change the trp files which get created? Into stops rather than waypoints?

Yes, that hidden option makes every position a stop target.

I have found another way as well. Use Routeconverter to create waypoints as usual and Save. Open the .trp file in a text editor and change every instance of show=0 to show=1. This changes waypoints to stops and avoids editing the Win registry which is a bit more difficult to do for most users.