So after a lot of time with the FSS (which I generally like, by the by) I wanted to make a suggestion on its feedback to the commander - particularly the 'signal count' displayed next to the Body Count.
To me, signal count should indicate non-body signals - i.e. emissions, geological, alien, biological signals. So in the bubble, this will be a pretty stinking high number because there are, of course, a huge number of signals! But in the black, where the FSS sees most of its work, signals by this definition would be much more informative.
So, to be succinct, here are my suggestions:
1) "Signal Count" is defined as the summation of all Non-Body Signals (No Clusters, No Bodies, No Stars). A body with signals (be it 5 bio or 55 geo) counts only as ONE signal. This is because at distance, and without surface scan, the FSS cannot discern the count of signals from such a specific point, only that they exist.
EX: System has 11 Bodies (2 Stars, 3 Clusters, 4 Landable Planets, 2 Non-Landable)
-FSS Reads: "Body Count: 2 / 11" (I haven't found the clusters yet at this stage, so just the stars are showing after initial 'honk')
-"Signal Count: 5"
So right off I know at least one signal isn't on a planet, because only four planets are landable - could be an emission, or a guardian beacon or whatever - but by paying attention to my initial system map and FSS readout, I already have an idea of potential signals. It might be that ALL FIVE are in space, too - using the FSS will be necessary to solve that question.
2) When conducting level 2 scans of bodies, Signals are only displayed by type - not quantity.
EX: I zoom into one of those landable planets. Instead of taking forever to count up the "55 Geological" signs, it simply immediately reads "Geological Activity Detected". Other examples would look like so:
-"Biological Signs Detected"
-"Alien Emissions Detected"
-"Human Signals Detected"
If a planet has multiple types, it says so. Counts are not given for the same reason as mentioned in the first suggestion: the FSS can't count at such distance, and without a surface scan (level 3) you shouldn't be able to locate them anyways...so how can you count them? As already exists in the FSS information screen of a zoom-in, you have clues in the planet's data to determine if these signals are worth looking into.
These two suggestions only change how the FSS displays data and ought to reduce the scan time (loading time for server to figure out how many signals there are) when just conducting level 2 scans, but also clarify what may be present in a system. A quick recap:
Level 1 Scan (Honk) tells me if signals are in the system and how many - 1 point per planet, 1 point per space-borne signal (as normal)
Level 2 Scan (FSS Zoom) tells me what type of signals, if any, are on a body. Zooming into space-borne signals tells me what they are (as normal)
Level 3 Scan (Surface Scan) tells me the actual locations of the signal (as displayed in navigation) and their quantity (also found in navigation). Signal quantity never enters the FSS or the analysis mode of the cockpit HUD - it is only shown in navigation when they aren't filtered out.
To me, signal count should indicate non-body signals - i.e. emissions, geological, alien, biological signals. So in the bubble, this will be a pretty stinking high number because there are, of course, a huge number of signals! But in the black, where the FSS sees most of its work, signals by this definition would be much more informative.
So, to be succinct, here are my suggestions:
1) "Signal Count" is defined as the summation of all Non-Body Signals (No Clusters, No Bodies, No Stars). A body with signals (be it 5 bio or 55 geo) counts only as ONE signal. This is because at distance, and without surface scan, the FSS cannot discern the count of signals from such a specific point, only that they exist.
EX: System has 11 Bodies (2 Stars, 3 Clusters, 4 Landable Planets, 2 Non-Landable)
-FSS Reads: "Body Count: 2 / 11" (I haven't found the clusters yet at this stage, so just the stars are showing after initial 'honk')
-"Signal Count: 5"
So right off I know at least one signal isn't on a planet, because only four planets are landable - could be an emission, or a guardian beacon or whatever - but by paying attention to my initial system map and FSS readout, I already have an idea of potential signals. It might be that ALL FIVE are in space, too - using the FSS will be necessary to solve that question.
2) When conducting level 2 scans of bodies, Signals are only displayed by type - not quantity.
EX: I zoom into one of those landable planets. Instead of taking forever to count up the "55 Geological" signs, it simply immediately reads "Geological Activity Detected". Other examples would look like so:
-"Biological Signs Detected"
-"Alien Emissions Detected"
-"Human Signals Detected"
If a planet has multiple types, it says so. Counts are not given for the same reason as mentioned in the first suggestion: the FSS can't count at such distance, and without a surface scan (level 3) you shouldn't be able to locate them anyways...so how can you count them? As already exists in the FSS information screen of a zoom-in, you have clues in the planet's data to determine if these signals are worth looking into.
These two suggestions only change how the FSS displays data and ought to reduce the scan time (loading time for server to figure out how many signals there are) when just conducting level 2 scans, but also clarify what may be present in a system. A quick recap:
Level 1 Scan (Honk) tells me if signals are in the system and how many - 1 point per planet, 1 point per space-borne signal (as normal)
Level 2 Scan (FSS Zoom) tells me what type of signals, if any, are on a body. Zooming into space-borne signals tells me what they are (as normal)
Level 3 Scan (Surface Scan) tells me the actual locations of the signal (as displayed in navigation) and their quantity (also found in navigation). Signal quantity never enters the FSS or the analysis mode of the cockpit HUD - it is only shown in navigation when they aren't filtered out.
Last edited:
