I'm docked at Morgan's Rock now in the NGC 6188 nebula, last stop on my way to the cats paw nebula. I'm about 4,000ly & a couple of hundred jumps out now and my ship has nearly paid for it's 42mCr rebuy in exploration data & I've cashed in a total of 225,000Cr in Codex vouchers.
In terms of credit farming the new FSS is certainly a time saver. It has probably helped that in order to stave off frustration in my 30ly ship I'm route plotting with a filter that excludes M & K class systems and brown dwarves.
With the old process there was a sense of achievement to completely scanning a system, something I rarely did unless the system was small. Every time I hear 'System Scan complete' now I'm relieved I can get back to my cockpit to throttle up & look at the sysmap. I can then pick some airless world or two with volcanic activity, travel to it uneventfully, park up & lob 2-6 probes in a box formation in 3 seconds then wait for the POIs to populate the nav panel. Choose the closest one & drop down to scan it.
The composition scanner is incredibly difficult to use from the ship while pointing it at the ground. It has zero gimbaling effect and the ship wanders around and every time it goes off target I have to start the scan again (unlike a KWS for example, where the scan slowly regresses). I've spent a few minutes trying to scan in an area where my admittedly massive ship can't easily park, on the later ones I parked & took the SRV out to scan stuff only to realise how that's even more frustrating to scan with (again no gimbal and the turret doesn't tell you what you scanned), hence the reason for trying to use the ship.
In the FSS why do I have a percentage complete & not just a body count? I don't want to know I'm 88% done, I want to know I only have to find one more blue blob. I'm really starting to hate finding a signal obscured by the main star. I back out of the FSS & use the few planets I have already scanned & can see on my scanner (radar) to guess where the system plane is & move up or down a bit to let me FSS the blue blob. I could scan a body through another body before, why did this need to change? How did the FSS honk find it while it was obscured?
There's a few bugs that are relatively minor (like the composition scanner in the SRV) but mostly the issues I have are with the design. Put the ADS back in as a purchasable module just as it was before, and let it populate the sysmap & nav panel just as it did before. The FSS scanner Screen will still be useful to DSS at a distance for those that want to explore the system that way, and the dedicated explorer can FSS all the things & save themselves a module slot, some power & mass.