You have been lucky.
Patch Notes Update Update 3.3.01
- Status
You have been lucky.
I did read it, yes. Then I replied & you quoted that reply.
There is a lot to like about the new discovery process, but the pre-3.3 process should not have been removed & needs to be reinstated alongside the new one so that overall we see an improvement for all. I was expecting this to be done in the first patch to minimise disruption.
There is no need to hobble the pre-3.3 process, and any body not scanned would remain hidden from any player that chooses not to fit one of the three disco scanner modules. They would also free up a valuable module slot and save some power & mass.
Ok, so the post says;
So, going back to my example of BD-12 1172, why have the first discovered AND the first mapped names been removed?
BD-12 1172 isn't a populated system and is definitely not within the bubble.
Also, I disagree with this change. It shouldn't have been 'populated' systems, only named systems like Sol, Sirius, etc.
Take a look at the PS4 bug report forum, there's a sticky with 23 pages. For the last week people have experienced bluescreens from ED, some so severe the whole console shut off and had to do a system scan afterwards, sometimes resulting in a corrupt local save. Many people were even unable to log into ED again without an instant crash.
Last edited:
I think that when FDev said 'populated' they didn't mean people living in that system but that the data on that system was pre-populated. My home base is one of these tagless systems & I had both discovered by and mapped by tags on most of it after 3.3. From today the main star reverted to untagged & only the mapped tags remain on the other bodies.
Last edited:
Ozric
Volunteer Moderator
There were 2 bugs. One was putting discovered tags on planets that have never been able to be discovered (like Sol). The other was overwriting the visual display for the First Discovered tags that were already there. I believe it occurred when you mapped a planet that had been discovered pre 3.3, it was then showing as having been mapped and discovered by you when you sold the mapping data.
Your example, seems to be a different thing but probably a consequence of the "fix". If you had already sold that data since 3.3 and had you name on the planet, then I would create a bug report for it. There may already be one created so add to it if there is.
Different people like different thingsI used the ADS for thousands of hours, over 30,000 systems & it worked for me. The ADS does things the new process does not, and having used the new system in beta & since launch I can confirm that there is no downside to having the pre-3.3 discovery process remain. They should not have been removed & doing so creates an issue which will only get worse the longer their absence continues.
The ADS & other modules should not have been removed & need to be put back into the game. Those players that prefer to go without an ADS (or BDS/IDS) gain a valuable module slot, and save some power & mass. This easily offsets the minor advantage the ADS has in specific, rare circumstances.
Of course the ADS worked for you, it would magically locate everything almost instantly no matter how far away it was. It worked for me as well for a lesser period of time and fewer systems, but I am delighted with all the extra stuff I can find using the new system even though it does mean I have to learn and setup new controls.
The trouble is the systems are incompatible, not due to any technical reason but because people are often lazy and would tend to stick with the familiar easy system than the new and strange system that they have to think about.
Don’t really understand the “want” to go back to the old system.
Right now, the “honk” seems to work like the ADS and then you scan using the FSS in scan mode.
I suppose if you just did the “honk” and all the stellar bodies showed up as explored, it is a bit weird. But right now I have this problem where even after honking and targeting the Sun of a system it shows “unexplored” in the bottom left target UI.
I am ok with the new system.
Dovrebbe essere stato risolto (non ho provato personalmente ma ho visto dei video con i molluschi e le altre forme di vita nelle Lagrange clouds).
I was hoping for a fix for the message list's filter option: if you accidentally hit it (and this happens quite often because it is the first to be selected upon opening that UI), you seemingly cannot close the filter list without either closing the social UI altogether or choosing Clear all filters. Both the Escape key on the keyboard and the circle/B button on the DualShock 4 controller do not appear to work.
Anyone getting that behaviour or is that some local issue with my copy?
Anyone getting that behaviour or is that some local issue with my copy?
I think people would use the FSS to DSS if they are interested (ie they would still have to learn to use it and see it's advantages), or they would be able to travel to the body as before if they prefer not to use the FSS Scanner Screen at all. Those that see the benefit may then choose not to equip an ADS & so the community can choose to transition to their preferred technique.
This discussion has been had btw, and there is at least one active thread on this very topic in DD.
The old system revealed everything as unexplored & did not tag the bodies unless direct action was taken by the player. These unexplored bodies are not visible on the sysmap to any other player, you may have noticed this already in 3.3 as you make your way out of the bubble & venture into partially explored systems.
Yes, the new process has a lot going for it. If you chose not to fit an ADS it's availability to other players would not affect your enjoyment of the new features at all.
Last edited:
OK, I admit to being slightly naive to this. I play regularly and had not had occasion to log any bugs, or trawl through the bug forum to see if the others were getting the same issues. As others have pointed out here, I've been lucky in that respect.
However, consider the whole concept of console hardware. They are built the same, to the same specifications so that if a game works on one it works on all, something that cannot be said for PC. So FDEV develop and test the game on a number of consoles by different people and clear out bugs that show up internally. Then it goes out into public use, on consoles that are also the same hardware specs as the ones on which they have tested. Then new bug reports start coming in. However, if those bug reports do not show, in detail, exactly how that console has been used, how many times it's been powered off mid-process, etc., what other games are also installed on it, how the OS has been configured by that user, then FDEV have almost zero information to go on to try to recreate the problem in the lab. If they can't recreate it, then how will they ever know if they've fixed it? They can't just put in a fix that "might work" and release that in hope, how would that look in the patch notes? All they can do is accumulate more information regarding it with the hope that somewhere along the line the one snippet of info comes in that sheds light on the root cause. In the meantime it just has to sit there in the "reported" queue, but if only a small number of people ever suffer this and not enough information comes in to diagnose it, then it will never get fixed, no matter how many times those few people fume on the forums.
I understand why discovered and mapped tags were removed from pre-populated planets such as Earth, etc and also fixing first discovered/mapped tags that were overwritten.
I mapped three or four previously unmapped planets in BD-12 1172 and sold the data only a couple of days ago. So it does seem like a bug.
I've now posted a bug report about it so I'll wait and see what happens.
Cheers
I think the idea of finding Opals in space is very odd given that opals are derived from organic (plant) material.
- Status