This needs to be addressed. I, nor does anyone have 5 minutes to waste every time the Galaxy Map is used to plot a course around 90 ly. If it's intentional then it needs to be fixed. I use the Galaxy Map non stop and it's a real pain in the ass to constantly waiting to plot a course that I have been to over 100 times.
Let us have Favorites. Allow us to save plotted courses for future runs. I shouldn't need to wait to plot a course I have traveled multiple times.
Let us plot courses over 100 ly. Seriously, it's the future and we have spaceships yet we can't plot a course past 100 ly ???
We would like to use our own Waypoints !!!
Not a bad idea, in theory. However, jump ranges are calculated each time opening the Galaxy map because the jumps your ship can make depend on its overall mass, which can vary greatly depending on whether your cargo hold is empty (or full, or somewhere in the middle), as well as if you have made any ship-related upgrades/changes (i.e. bought a higher tonnage ship, put in new modules that increase or decrease mass, etc.).
/
Basically, it takes so long because our desktop computer (not the shipboard computer) has to run the algorithms to calculate the various route jumps possible based on our current ship configuration and cargo hold levels.
/
Imagine this scenario: a favorites waypoint system is implemented, and someone in a Sidey goes "hey neato....I can plot a 200 ly course from Chemako to Achenar"! And they do so....and save it as a favorites/waypoint route for future reference. Later on they upgrade to a Cobra MkIII, and use same route, and get stuck in a system because of lack of fuel. They are going to then come back and complain that the waypoints/favorites are broken.
/
However, based on this, I
do believe that using the current system's method of calculation, it ought to be possible to restrict the algorithm calculations (or at least prioritize them) if we have selected a distant star as the "destination" from within the Galaxy map. Doing so really ought to trigger an electronic "flag" to tell the computer to prioritize calculating the jump leg distances (i.e. the "spiderweb") between current location and the long-distance destination before calculating everything else. That would go a
long way towards reducing route planning frustrations IMHO.