Time taken to plot 100ly jump

Is this influenced by client speed? e.g. is it faster on an SSD?

Or is it server side? In which case....any chance of giving it a boost?

I have written this thread while waiting for a route to be plotted...

...still waiting...
 
It is calculating possible routes between a large number of locations based on your current weight / jump distance, I normally just zoom out and watch it populate, what is the rush?
 
I do appreciate that there are a few combinations to calculate and that it happens a bit faster than I could do it.

But still...seems very slow! Is this a limitation of today's computers, or a limitation of client-side hardware, or server side?
 
It is calculating possible routes between a large number of locations based on your current weight / jump distance, I normally just zoom out and watch it populate, what is the rush?

Limited play-time, seen it do it before, already know the route, naturally impatient, haven't got an asp yet. Among other reasons :p

- - - - - Additional Content Posted / Auto Merge - - - - -


Helpful, thanks!
 
God I wish I could actually plan my route picking the stars to jump to instead of waiting for this thing to complete. By picking stars I mean in the map so I get the same line the routing planner gives and the have the next star already locked after warping. Yes I know I can warp, select my next star by name (if it even shows in the panel)
 
One thing FDEV could do to speed it up is to only calculate routes in the direction towards the selected destination - basically within a cylinder instead of the sphere. The coding of that is a bit tricky though. It's certainly doable, but definitely not a 5 minute fix.
 
What's disappointing is that there are web tools (written by wizards no doubt) that very quickly calculate a route across hundreds of light years. My preference is http://www.miggy.org/games/elite-dangerous/routes/. I just don't understand why the in game route planner can't work as well. Or why I can't hand build my route.

Jumping into a star and then having to go to the galaxy map to type in the next destination is annoying and in open play, nerve wracking. (For long jumps they don't show up as available on the system list on the right panel.)
 
These calculatings are very complex and needs a high amount on CPU time. The calculation exponentially rises with the number of jumps.


Those web tools aren't used frequently, so most of the CPU is available. Frontier has thousands of players plotting routes simultaneously. Even a Rack with 256 CPUs has it's limits. And you need those when plotting a course to the galaxy center for a single player;) So it's limited to "short" routes.
 
Last edited:
Someone hasn't watched Star Wars - A New Hope :)

Obi-Wan: How long before you can make the jump to light speed?
Han Solo: It'll take a few moments to get the coordinates from the navi-computer.
[the ship begins to rock violently as lasers hit it]
Luke: Are you kidding? At the rate they're gaining...?
Han Solo: Traveling through hyperspace ain't like dusting crops, boy! Without precise calculations we could fly right through a star, or bounce too close to a supernova and that'd end your trip real quick, wouldn't it.
Darth-Vader-I-FIND-YOUR-LACK-OF-FAITH-DISTURBING.jpg
 
Yeah the spider web thing is a bit odd , rather than just doing the route desired or the vague region.
 
I play on an SSD, but surprised that would matter. It is literally instantaneous for me always - takes just a tiny fraction of a second. Didn't know this was an issue, to be honest. If it's client/CPU driven then perhaps it's the 4.5Ghz OCd CPU that's working its magic? Not sure.
 
Last edited:
Someone hasn't watched Star Wars - A New Hope :)

If we're using this as the basis of all-things-scientific, we may just as equally use Red Dwarf, and ask why we can see planets in SC.

Holly: Look, I'm trying to navigate at faster than the speed of light, which means that before you see something, you've already passed through it. Even with an IQ of 6000, it's still brown-trousers time.
 
uhm ive got an i7 4770K @ 4.5ghz and 2x280X crossfire - SSD 100ly route takes abt 30 secs from opening galaxy map. u need to let the white routes calculate..
 
One thing I noticed when I went abotu 1500 LY out, was that in regions of very low star density, I was able to plot jumps of up to abotu 150LY.

Then when I came to a star cluster with stars every 1-1.2 LY, the time to plot rose immensely (as expected), but also the maximum range drops to under 50LY.

So it's looking to me like the range limit is dependant on a maximum number of stars to consider, or routes to plot in the web, rather than straight distance limits.
 
It is not based on CPU speed I think. I have a 5ghz eight-core processor. So that definitely is not the issue. However my GTX 780 Ti died on me last weekend and I have been playing with a 520 since. :(

So it could also do with the graphics or SSD. I do not have either of those at the moment.
 
Back
Top Bottom