![[Diplomacy] Carnegie](https://forums-cdn.zaonce.net/data/avatars/m/123/123809.jpg?1553527149){kind=avatar}
I view the Codex as pointless, in large part because of this type of buggy behaviour. It makes a nonsense of it being introduced in the first place.
The FSS still goes off on a drunken cruise sometimes when looking at distant objects, and planets regularly show up fully scanned in the DSS when I’ve never been anywhere near them (plus we now get the entertainment of seeing nearby planets getting the scan markings at the same time as the object being scanned)
All these things were marked as “fixed” in various patches. My level of confidence in any of them being truly fixed is very low at this point.
As an aside, the new “make it easier for newbies” descriptions and updates threw up something interesting last night: I selected a planet to travel to in the nav panel after first entering the system (It had bio signals come up). Selecting targets now gives you the option to see “more information” about it, eg pad size available, faction, etc. One of the items is “Mapped?” which shows Yes or No, depending on whether you have probed it. Well, in this case, it showed as “Yes” even though I had never been in the system before, let alone visit or probe the planet! Sure enough, when I arrived at it, it was showing fully scanned in the DSS view... I’m not sure what this really tells us, but it seems that the scan status isn’t affected by travel to the object, perhaps. (On the sysmap, it showed correctly as “You have not yet mapped this planet”)
The random FSS behavior on distant objects is a joy to behold.
Today I had it tell me that there were no icy moons near a distant star. Spinning the mouse in circles to rotate the orbital plane 90 degrees (because that's intended behavior
) and pointing at the star fixed the problem. Rotating the orbital plane back to horizontal brought it back again. It's like FDev tested it in 3 systems and called it good.
