Suggestion: Show the LS of a Station/Outpost in the mission brief

It would be extremely handy if the in game mission descriptions could include the distance from the arrival point for the outpost or station you need to go to - is this something that would be do-able?

At present the mission description at the bottom where it shows the destination currently looks like this:


Starport: Cochrane Terminal (Station)

System: Itza (7.14LY)


What i'm proposing is this:


Starport: Cochrane Terminal (Station - 454LS )

System: Itza (7.14LY)



It would be a masssive benefit, there's nothing worse than finding an ideal mission only to discover the station or outpost you need to got to is 89,000 LS from the arrival point.

Cheers
 
The solution is literally two clicks - open Galaxy map, open System map. How easy does it have to be?

For some people, those two clicks actually mean 30-45s of just waiting for a bloody screen to finish loading, then going back to the missions screen (loading again) because opening the map closes everything else.

What's being suggested here is a great QOL addition. The current system is unwieldy, and this would make it quite better, actually.

Now that we can just fart in the face of stupid mission givers who send us last minute to another random station half the bloody time, looking at the map is no longer pointless, but it's still a lot of trouble for no reason just to get to a critically important number.

Also, Newsh, saddle up, such suggestions get a lot of heat from the "500 lightyears, bare foot, in the snow, uphill - both ways!" crowd.

I've always advocated for FD to implement some manner of depth, interesting mechanics, things to do meanwhile to make supercruise more... - sorry - less brutally boring (my main idea here : https://forums.frontier.co.uk/showthread.php/315128-Hazardous-in-system-FSD-jumps)

...But since it dosen't seem to be part of their long term plans, making it as easy as possible to figure out station distance (a parameter that is systematically checked each time) is a must. Such important info shouldn't be hidden behind two load screens, for the very same reason that system distance is displayed - in fact, game-wise, station distance would be much more important to display that system distance - because in most cases, system jumping takes less time than supercruising.
 
Last edited:
Is the distance from the star still reported in the mission description if you don't have the data on the system?

Given that the mission giver clearly knows where the station is due to their contacts, the data should be available, imo. Right now, it is not available at all unless we have the system data and waste time loading the star/system map.
 
The solution is literally two clicks - open Galaxy map, open System map. How easy does it have to be?

As my fellow CMDR stated above - the time taken to open the galaxy map and system map varies from one person to another, and Xbox players also get a delay in opening the maps. So while it might be easy for you, unfortunately its a pain the rear for others
 
The only wrinkle I see is that a mission can send you to a system you haven't visited yet and is not one of the many commonly known. Ergo, you don't have access to the system map and adding that info to the mission is a *little bit*of a cheat.
Simple fix though. If system is known, show distance. If not, don't (and optionally show unvisited system or something on the mission instead so you know it is deliberately not telling you rather than bugged).

I like the idea.

An alternative could be to add an additional filter to missions to exclude stations farther than 1000ls or something. But I like the idea of having it on the mission better.
 
It would be extremely handy if the in game mission descriptions could include the distance from the arrival point for the outpost or station you need to go to - is this something that would be do-able?

At present the mission description at the bottom where it shows the destination currently looks like this:


Starport: Cochrane Terminal (Station)

System: Itza (7.14LY)


What i'm proposing is this:


Starport: Cochrane Terminal (Station - 454LS )

System: Itza (7.14LY)

It would be a masssive benefit, there's nothing worse than finding an ideal mission only to discover the station or outpost you need to got to is 89,000 LS from the arrival point.

Cheers

That would be a great QoL convenience.
It has been asked before.
 
Last edited:
the problem here is, that in most cases, the distance of a station is down to the distance of the body to entry point it is orbiting (and of the star orbiting the main star etc.).

for elliptical orbits (which are not rare) that would mean a server request is necessary, which would slow down the mission board - this is currently done when opening the system map.

so, with the current implementation showing station distances would slow down the mission board, which, i tjink, nobody wants.

workarounds could be to do the server request in the detailed view of a mission (slowing down loading those), or to show minimum/maximum distances of stations ( something like: distance to station >5000 ls), which could be a fixed value.
 
workarounds could be to do the server request in the detailed view of a mission (slowing down loading those), or to show minimum/maximum distances of stations ( something like: distance to station >5000 ls), which could be a fixed value.

Or use your own APIs to query eddb.io which will report the distance instantly.

(Personally I don't mind not knowing how far the station is as only Hutton Orbital is so far it's a problem)
 
the problem here is, that in most cases, the distance of a station is down to the distance of the body to entry point it is orbiting (and of the star orbiting the main star etc.).

for elliptical orbits (which are not rare) that would mean a server request is necessary, which would slow down the mission board - this is currently done when opening the system map.

so, with the current implementation showing station distances would slow down the mission board, which, i tjink, nobody wants.

workarounds could be to do the server request in the detailed view of a mission (slowing down loading those), or to show minimum/maximum distances of stations ( something like: distance to station >5000 ls), which could be a fixed value.

Thats a fair point

i like the idea of a min/max figure, showing that a station is less than or more than a certain Ls would easily suffice - all we need to do is avoid the 'distance to station >200,000 Ls' missions :)
 

Lestat

Banned
I think I rather have Frontier work on the bugs to help with the lag then have it displayed for us..

Here why. A lot of time we don't know how far it is when we view the map. We have to pay for the system info. That part of the game.

Some people they might just have Lag.
 
Experience tells me if it's a near by system and a very high paying mission (not all the time granted if your low rep with the faction issuing the mission ) that it's going to be a trek to the station
 
Back
Top Bottom