On the galaxy map there is a delay to route to extremely far places but after waiting a few minutes it works but only for things under 100LY. If its over it can't be routed to. SO usually I just route to a place nearby and then when I am closer to it later I route to my original destination. This is kind of annoying though.
How come you can't route to places over 100LY?
- Thread starter rupok
- Start date
I've noticed the distance I can route to seems to vary. Sometimes I can route about 80ly, sometimes I try to set a route 60 ly away and it won't do it... seems quite inconsistent.
It's still better than before routing was implemented though
It's still better than before routing was implemented though
I've noticed the distance I can route to seems to vary. Sometimes I can route about 80ly, sometimes I try to set a route 60 ly away and it won't do it... seems quite inconsistent.
It's still better than before routing was implemented though
Sometimes you need to give it a bit of time to work out the links, it'll always do 100ly for me, but sometimes needs 30 seconds or so to compute.
Deleted member 56127
D
This is what I like to call The Art of Navigational Computer Programming or NCP.
Path finding algorithms computation time grows exponential with the numbers of nodes in the graph (see Shortest_path_problem on wikipedia (i would post a link if the forum would let me)). By limiting the range it also limits the number of nodes in the search graph (given that there is a minimum of stars per volume of space).
Erm... LOL?
IF FD would have build a proper system you just could ask for a route to your target, so it wouldnt have to update every route on that way. Granted, still some punch on pathfining routines but way faster than the current wait for the map to upated their connections.
Elite is probably the only game so far it seems that there might be significant performance increase if we play it on a quantum computer
Ive been playing since beta one. I recently deleted my save and started over. I spawned in LHS 34447. I bought a fuel scoop, and an upgraded frame shift drive, which allowed jumps of a little over 11ly. I then headed first to Aulin, and then to Sorbago. I couldnt plan routes for those distances, so what I did was I went onto the galaxy map, and chose a point that was about half way between Aulin and Sorbago. Then when I reached the halfway mark, I went back into the galaxy map and set a route for Sorbago. I did the same from LHS 3447 to Aulin. All together that was roughly a 250 - 300 ly distance traveled during which time I had to enter the galaxy map only twice. I think factors such as jump drive limitations, and fuel limits probably make route planners quite difficult to implement. I think weve been lucky to get what we got.
Cargo mass is probably also an issue.
Cargo mass is probably also an issue.
Last edited:
Erm, what wait? Choose a star anywhere in the 100 LY "bubble" and you'll get a route to there as quick as you can press the button.
Nope, can't be.
My onionhead travels proved that I could go more than 160ly on a single tank via fastest route, but I still needed to re-plot route 3 times.
My best guess would be total amount of jumps required as the limiting factor(?)
I've noticed this too. It must be some type of limitation with the networking server instance capabilities. Not sure at all.
It's actually to do with the mathematical complexity of route planning. It's a well studied area of game development but there is no easy answer; you wouldn't actually believe how much processing power it takes to plan routes with as many nodes as there are stars within a 100Ly radius.
Apparently our experiances differ. For me, plot route is always disabled, until the routine that builds the routes in the background has reached the system in question (as in: until theres a path of blue lines connecting my current location to the selected one).
I am fairly sure that things like computation of path findings can and should be streamlined by algorithms simplifying the process