Quick adjustment to hyperspace pathing calculation

At the moment, as soon as you go to the galaxy map your ship computer starts calculating ALL possible jumps your ship can make. This is very nice, but i would like to suggest an addition to this behaviour: Once you select a system, the jump calculations are ONLY carried out to that star, all others are stopped immediately. This should make it much faster to calculate those 100-200ly jumps, and lead to much less time spent staring at that slowly growing bubble of lines on the map.
 
Yes, this could certainly use some optimisation. Every time I need to go 50ly or so, it takes forever go get the calculations done, if they every get that far at all. I usually have to jump to something randomly and hopefully "on the way" and then plot again from there. I don't think the current system can plot a course from fx. Sol to Achenar at all. It's just too far for the brute force jump calculator.
 
Yes, this could certainly use some optimisation. Every time I need to go 50ly or so, it takes forever go get the calculations done, if they every get that far at all. I usually have to jump to something randomly and hopefully "on the way" and then plot again from there. I don't think the current system can plot a course from fx. Sol to Achenar at all. It's just too far for the brute force jump calculator.

The current system can supposedly plot up to 100ly. I don't think anyone has ever had the patience to wait and find out if it can, though, as it takes ages :). With the proposed solution, you could plot courses for several hundred ly in seconds. I'm kinda surprised it doesn't work like this already.
 
http://www.reddit.com/r/EliteDanger...e_copilot_v013_now_does_basic_routing_on_top/

Someone already made this, with voice navigation.

I've tried it, and plotted a 300 LY jump in less than 5 seconds. Spent more time trying to spell the systems correctly.

My understanding is that the guy who wrote the software would be wiling to let Frontier use it , as it's freeware and he put the source code up on GitHub.

But yeah, the current method for plotting jumps is ludicrously bad, if you're going more than 20 LY away, ESPECIALLY if you have a 25+ jump capacity.
 
Back
Top Bottom