Galaxy map> system select> Faster route calculations

[stevelee]

Currently there's little point getting a massive FSD because the navcom cuts the list off after 50 systems.

Currently the Galaxy map only plots a course of 100LY.. and it takes a long time to do it.

Suggestion;

You select a system in the galaxy map, the navcom prioritizes the calculation, instead of waiting around for 10 mins it could be done within seconds.
Even with a 100ly limitation, it wouldn't be as downright painful as it is currently.

Jumping 30ly at a time and having to wait 10 mins to plot a 100ly course.. is madness.
(it takes as long to plot the course, as it does to traverse the course)

you could do it by eye but as mentioned, the navcom list cuts off after 50 systems, leaving u with a max range of 15-20ly unless u use the dreaded galaxy map.

 

[Rein Quest]

I'm not sure I know what you mean on 50 systems limit but I do agree that something needs to be done to make flight plans render quicker. I'm not sure why it takes that long to connect the dots on a 100Ly limit.

 

[stevelee]

hi

it takes that long because it's computing them all.
doesn't need to compute them all.

(the 50 limit i refer to is left panel, navigation, list of destinations)

 

[dementia]

As has been mentioned in the news letters and discussed countless times in these forums. The current limit of 100ly will be increased to 1000ly as part of the 1.1 release. More optimisations will like follow that will further increase this limit and there have been many valuable suggestions on how best to do this.

 

[Agony_Aunt]

And currently it will go higher. I can map out about 140 LY if i leave the map open long enough for it to calculate all the routes.

I have heard, given long enough, it will calculate all routes up to 200LY providing a full tank would take you that far, but that could be hearsay.

Still, sounds like 1.1 will improve things.

Oh, and there is a very good reason to get a bigger FSD anyway. Further jump range. When you are where the stars are thin, they can really save on dead ends and travel time. 30LY+ Asp FTW

 

[stevelee]

As has been mentioned in the news letters and discussed countless times in these forums. The current limit of 100ly will be increased to 1000ly as part of the 1.1 release. More optimisations will like follow that will further increase this limit and there have been many valuable suggestions on how best to do this.

If it takes 10 mins to calculate 100ly, (and 5 to calculate 80) then i don't think increasing the number to 1000ly is very wise.
(unless one of these optimisations is, `calculate nothing until i select something then only that`)

sorry i didnt see the notes about that on the emails we get sent out. i try to read every one of them.

Loki - Aye fair point , i lack the experience of deep, deep space at the moment.
rectifying that now

dementia - thank you for the effort and sorry about the humdrum. I'll await 1.1 like everyone else. Just trying to help, couldnt find it mentioned in the `common suggestions` thread

 

[Rein Quest]

I've mapped out to 130 so far.

Anyhow I only remember the range limit of 100 going to 1,000. If there is calc speed boosts that will be awesome.

 

[knoppaz]

I wonder why they try to calculate every route anyway. Why not just calculate one route as soon as you set the destination. The actual system calculates hundreds of routes within a sphere of 30ly within a second (and from there it slows down rapidly) so it should be able to calculate just one single route of hundreds or even thousands of ly in the same time..

 

[stevelee]

I wonder why they try to calculate every route anyway. Why not just calculate one route as soon as you set the destination. The actual system calculates hundreds of routes within a sphere of 30ly within a second (and from there it slows down rapidly) so it should be able to calculate just one single route of hundreds or even thousands of ly in the same time..

Suggestion;

You select a system in the galaxy map, the navcom prioritizes the calculation, instead of waiting around for 10 mins it could be done within seconds.

(unless one of these optimisations is, `calculate nothing until i select something then only that`)

yes i agree