as discussed on the dev mailing list, i'm creatig this bug concerning the route manager selecting way points that are way off course... i plan to add more flight plans showing this problem if they are needed...
the first flight plan attached below was created at onlineflightplanner.org... we simply chose ENBR as the departure point and LOWW as the arrival point... start FG, open the route manager and load the flight plan... use the CTRL-M map to follow the route... there is at least one way point that is 4000nm off course... there are two others that are ~300nm off course...
here's a real good one... it explods and puts long unneeded way point segments all over the place...
Last edit: waldo kitty 2018-07-02
on the other hand, this one is fine...
Is this the same as the bug I filed November 2015? I know the bug I described still exists in 2018.2.1 because it happened again a few weeks ago. https://sourceforge.net/p/flightgear/codetickets/1814/
I just tested the problem route, since I made a fix in this area a few weeks ago, and it seems load correctly for me now: please can you check yourself with next or 2018.3.x and confirm, or let me know what is wrong with the route otheriwse (which segments/legs are not as expected)
And the fix was for ticket 1814 indeed.
The routes also work for my with current next, so this one is assumed fixed.