Where's the FSS?

Johnny Cyclops

Johnny Cyclops
So, I've got an automatically installed Discovery Scanner, and that seems to still work as before, although have to toggle into Analysis Mode.

I've got a Detailed Surface Scanner, as before, but now needs this fiddly 'firing splats at planets' procedure, rather than the previous 'scan body' activity.

I've been given a seemingly new unweighted module 'Composition Scanner' that doesn't appear in the Outfitting, but is in Fire Groups Tab. And no indication what it's actually for (ignoring for now, but presume it will have some hidden use).

I keep reading about something called an FSS which I think might be a fourth scanner. How do I install it? Do I need to buy and fit, or is it like the Discovery and Composition, free? And what function does it perform that Discovery Scanners don't or won't?


I've an inkling that changes to missions and finding USS might now require this "FSS", but I'm not sure, and as often with FD/ED players are lefting guesing as to how the game actually functions. I'd forgotten this 'feature' of FD's approach, given I got over most of my learning 'bumps' years ago, but new release spring new surprises!
 
Last edited:

CMDR Zadian Lichtfrost

C
Johnny Cyclops said:
So, I've got an automatically installed Discovery Scanner, and that seems to still work as before, although have to toggle into Analysis Mode.

I've got a Detailed Surface Scanner, as before, but now needs this fiddly 'firing splats at planets' procedure, rather than the previous 'scan body' activity.

I've been given a seemingly new unweighted module 'Composition Scanner' that doesn't appear in the Outfitting, but is in Fire Groups Tab. And no indication what it's actually for (ignoring for now, but presume it will have some hidden use).

I keep reading about something called an FSS which I think might be a fourth scanner. How do I install it? Do I need to buy and fit, or is it like the Discovery and Composition, free? And what function does it perform that Discovery Scanners don't or won't?


I've an inkling that changes to missions and finding USS might now require this "FSS", but I'm not sure, and as often with FD/ED players are lefting guesing as to how the game actually functions. I'd forgotten this 'feature' of FD's approach, given I got over most of my learning 'bumps' years ago, but new release spring new surprises!
Click to expand...


The FSS was the replacement for the discovery scanners. FDev removed the module for the discovery scanners and made it a no-module-integrated part of the ship.
The D-Scanner is the FSS.
Go to Analysis Mode and press the button assigned to D-Scaner - the FSS screen will activate. Then press D-Scanner button again to honk. Then use the bindings you have assigned to move around in the FSS view and "click" on the blue blobs to scan them.
You don't have to buy it, it's already part of your ship and you might have noticed that you got the money for all the ADS you might have had back.

The composition scanner is apparently needed to identify things for the Codex - I have no clue about that.

USSs can still be found by being in discovery range of them - just like before. In the bubble you can go to the NavBeacon and scan that to get the location and type of all current USS in the system (or use the FSS - it's probably faster than going to the NavBeacon).

There is a YouTube video from FDev explaining the new exploration system. Might be worth to check out.

https://www.youtube.com/watch?v=hXXe7422OYE
 
Last edited:

Johnny Cyclops

Johnny Cyclops
Ok, I might need to do some more work here. I did some key bindings for the Detailed Surface Scanner (to launch the 'splats').

With the Discovery Scanner, I can get to it via the Analysis Mode already (and bound a key to toggle Analysis/Combat modes). The Discovery Scanner remains on my secondary fire button as it's in the Fire Groups tab and I've always assigned it that way, so I just press and hold that until the scan completes. Post 3.3 I keep getting the same data back "there are [xx] bodies in the system disc" (or some such). I'm not seeing anything else beyond that on the Analysis mode. I suppose I'll need to start calling in the FSS not the Discovery Scanner (but odd that FD left it call the latter in the Fire Groups tab).

I'll also add I'm only doing BGS work in local systems I've already explored and know like the back of my hand, so it's possible the Discovery Scanner will spring into life (or the FSS bits will) in unknown or uncharted systems.
 

CMDR Zadian Lichtfrost

C
Johnny Cyclops said:
…
I'll also add I'm only doing BGS work in local systems I've already explored and know like the back of my hand, so it's possible the Discovery Scanner will spring into life (or the FSS bits will) in unknown or uncharted systems.
Click to expand...

I think it's a single press (no hold) - I can't get the honk without getting into the FSS mode. And it should work in all systems, discovered or not, as it can be used to identify USSs.

Will have to recheck my keybindings later today.
 

Ashnak

Ashnak
The FSS and D-Scanner are the same module (arguably) and, post-3.3, integrated in your ship.

As you already noticed - using it as D-scanner, bound to a fire button in Analysis mode, will honk the system and tell you how many bodies there may be. It will also automatically analyze all bodies you are passing by close enough, giving the information (and reputation, and payout) the former DSS did. That's (for me) usually the central star, any close by asteroid belts, some of the secondary stars and, if I approach a gas giant, their inner moons.

If you want to use the FSS, you'll need to add two more bindings (or use one of the default bindings) - enter FSS mode and exit FSS. You now can even map them to the same button. And, if you actually want to do anything while in FSS mode, you'll also need to map a few more buttons (I re-purposed the turret controls) to sweep and zoom the FSS. This will then permit you to perform a scan of all bodies in the system (unless they're hiding behind a star) from your current position, yielding the information that formerly was available through the DSS without having to fly up to every moonlet.

The DSS is also extremely useful to any explorer (beyond the money). After the FSS scan, some objects may warrant a closer inspection - e.g. those planets that exhibit surface features. Fly up to them and pester them with DSS probes. When you've mapped the surface, those surface features will resolve into POIs you can target from orbit (like tourist beacons) and land next to. This is where the Composition Scanner comes into play. You can map it to the same button/firegroup as the Data Link Scanner and it'll activate automatically when you point it at something interesting - like an Ice Fumarole. Keep the fumarole in the scanner reticle and trigger the scan. You'll then be credited with a codex entry, including a small bonus payment.
 

Johnny Cyclops

Johnny Cyclops
CMDR Zadian Lichtfrost said:
I think it's a single press (no hold) - I can't get the honk without getting into the FSS mode. And it should work in all systems, discovered or not, as it can be used to identify USSs.

Will have to recheck my keybindings later today.
Click to expand...

With the Discovery Scanner still mapped to a Fire Group button it will still perform the pre-3.3 press, hold, scan/honk process, but you do still need to be in Analysis Mode for the DS to fire using the fire button.

I've now mapped to FSS commands and in Analysis Mode able to toggle in/out of the FSS. I'm not sure what all the bindings/mappings do (but no change there from around half of all bindings generally, and I've not met any limitations in that approach in four years!). I practiced the FSS in a known/mapped system, and will persevere (as with most things in ED). I suspect it's a different feel/function in unmapped systems.

I'm a wee bit concerned about the 'sitting duck' issue of being at zero velocity in SC (other than the near-static 30km/s), in Analaysis Mode and unable to look for either NPC ships getting in position to interdict, or worse a CMDR/pirate. When properly exploring it's in an unarmed stripped-down lightweight Asp-X, so a total sitting duck shielded but not much armour and no SCBs or chaff. When doing other local missions etc., it's likely the Python or Conda which both have enough shields/armour to withstand an NPC's initial attack, but not I fear a hardened PVP CMDR.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom