I wonder if thats related to the strange quirk they had with the left-window nav tab. My Asp has a fully laden range of 24ly but the nav tab would only ever show systems upto 19.5ly.
Seems to work for me.
Have you tried it more than once? It worked perfectly for me the first time but after that I get the same issues as the OP: when I pick a destination the first intermediate system doesn't always get selected, and even when it does it still tries to jump to the final destination directly.
When I select economical route and plot a course it works. But I can do 10 jumps before I reach the destination that could be 40 LY away.
if I set it to fastest route it does not work, I don't get any jump points.
The route planner seems to work within a maximum radius of 50Ly from your current location, and this seems to be by design (probably to restrict the number of nodes they are graphing, I'd guess).
It also seems to be bugged if you are plotting the fastest route, and doesn't activate the next waypoint if the individual jump distance is too great. For example, my maximum jump range is currently a little over 24Ly. I am currently in Haritana and want to plot a route to Shudun Sector KC-V B2-5 (LOS distance 45.30Ly). It correctly plots a 2-jump route: Haritana > LTT 5553 (23.95LY) > Shudun Sector KC-V B2-5, but the first leg doesn't activate, probably due to the range. I'm not sure what the cut-off actually is; the longest plotted jump that has worked properly was a little over 17Ly.
This is very close to the maximum range I can see via the in-cockpit navigation panel. The furthest system from Haritana that is listed there is LTT 5855 (18.1LY). I just upgraded my FSD last night, and I don't remember whether the navigation panel was unable to display systems all the way out to my maximum jump range prior to gamma 2.0 or not, but it is possible that there may be a link between the planner not working for longer jumps and the navigation panel not displaying longer jumps.
This is my experience... I can make routes up to 50LY with small jumps, but set it to fastest and it will show a route in the map but not actually map any waypoints.
Surprise surprise, ambitious patch is ambitious.
Yes, there's something strange going on with case. If you type 'Jaro' it works as expected. I'll try and take a look at it this morning.I think there is a bug in the autocomplete code. I typed "jaro" in the destination expecting to see "Jaroua" but the only options were "Jaroere" and "Jarowair". Typing the full name worked for finding a route so the system does exist in TGC.
Maybe it's to stop servers grinding calcing all these routes