It used to be that planets showed up on the system map after the discovery scan, but now I'm having to FSS them to get them to appear. I don't recall this being the case in the past. Is this a change, a bug, or something else?
System Map Not Showing Planets
- Thread starter avarusbrightfyre
- Start date
-
- Tags
- osyssey;system map
This was an update to exploration back in Horizons Beyond, it's working as intended.
Just to clarify, this is probably your first previously unvisited system. In the current system if you jump into a system that has been visited and the planets scanned using the FSS by another CMDR the planets will show up as soon as you jump in, but only the ones that were actually scanned using the FSS by the previous CMDR/CMDR's in the system. If you jump into a system that has never been visited previously by anyone the initial honk will show all stars and asteroid belts, including those stars in orbit around other stars, but none of the planets or moons except those within 50ls of your entry point.
Before the introduction of the FSS the honk would show all the planets regardless if anyone had visited the system previously so yes this has changed.
So in a new system the honk will show stars and asteroid belts and the number of bodies, but you won't see the bodies until you use the FSS.
Ah, I see. That makes sense then. I've noticed some systems show planets and other do not, so that clarifies the issue. Much appreciated!
oh what fun, attempting a fss in a thargoid controlled spire site system, with the only planet NOT showing is the one with the spire site... BAD DESIGN period.
Nice necro.
I find it a good idea to send in a scouting ship with reasonable jump range, cold running (low emissions), zippy fast, low rebuy cost ship to scout out all the Thargoid systems I might be interested in. FSS scan each system and then return to sell the cartographic data. This lets me know what systems are best for picking. Then I send out the appropriate AX ship for whatever activity I'm gunna do.
Using a scout ship to figure things out is a pretty basic strategy.
I find it a good idea to send in a scouting ship with reasonable jump range, cold running (low emissions), zippy fast, low rebuy cost ship to scout out all the Thargoid systems I might be interested in. FSS scan each system and then return to sell the cartographic data. This lets me know what systems are best for picking. Then I send out the appropriate AX ship for whatever activity I'm gunna do.
Using a scout ship to figure things out is a pretty basic strategy.
Though in this case it would be entirely unnecessary if it wasn't for the exploration data bug, which has been tripping people up probably since Beyond 3.3.
The Thargoid spire systems are all part of the "already discovered" set, so as with any system that someone else has sold the data for, when you jump into the system for the first time you get the positions (though not identities) of all the bodies without needing to use the FSS. Then you go to the planet with the spire, and die, because Thargoid spire. At this point if you've not done any actual scanning you have picked up proximity scans of the primary star and the planet with the spire (and maybe some others), which you lose on death. In theory, that shouldn't matter beyond the loss of a few hundred credits...
... but the game then incorrectly sets the status of the star and the spire planet in your personal exploration data to "entirely undiscovered" rather than "not personally discovered", so when you return to the system you proximity-scan the primary star again and find that ... but the spire planet is a long way away, so just appears missing and can't easily be rediscovered.
It's a bug which is, unfortunately, almost certainly never going to be successfully reported via the bug tracker despite having caught out at the very least hundreds of players over the years.
1) Every person experiencing it finds it happens in a different system so they can't find each other's reports easily. Also, if you post about it on the forum everyone else says "works for me" so you're not going to pick up extra confirmations that way either.
2) The actual cause of the bug is usually so distant from the experience of the symptoms - people might be revisiting systems months after their first visit - that even if it did somehow get enough player confirmations to get a Confirmed report that "Blah 6a" was missing from the system map, anyone at Frontier would do what most forum replies do: go to the system, find that it wasn't, and close the bug as unreproducible.
Ya, so whether it is system with a Titan, Spire, Station Under Evac, etc. If its a cmdr's first time in the system it is worth scanning them first, saving the data, and then proceeding with the activity. Generally Thargoid activities are done by a cmdr repeatedly, so saving the data once before hand and then choosing the best system (where the location isn't 300,000 Ls away) saves time. And obviously in a cold ship designed to escape interdictions quickly and easily.
I like the scout ship idea and understand why low rebuy is included in its description I do think that keeping the rebuy down should not be at the expense of the speed and coolth of the ship.
Ya, I just use my general purpose Krait AX farming ship to scout systems. Its zippy, runs cool, and only 5.5M rebuy. A specialized DBX with low emisions power plant might do well, having a better jump range.