Notice Scan data bug fixed

I was planning to head to the core and back before Horizons released but I've decided to cancel that idea. I wanted to do a partly leisurely return trip but waiting for the exploration problems to be fixed and the frequent server issues in the evenings means I doubt I will even reach the core at this rate.

I've just lost some exploration data due to being destroyed by an NPC. Normally I would have sold it by now but I have been holding on to it waiting for the all clear on selling exploration data. Luckily I have a record of where I have been so I can retrace my steps.
 
Last edited:
Just make sure you raise tickets for all these bugs. FD have shown through all of this a habit of assuming just a single issue and announcing it as fixed, even when there is evidence of multiple issues. Overwhelm them with data so they cannot assume that simplistic position.
 
Just make sure you raise tickets for all these bugs. FD have shown through all of this a habit of assuming just a single issue and announcing it as fixed, even when there is evidence of multiple issues. Overwhelm them with data so they cannot assume that simplistic position.

They're already "overwhelmed with data" and apparently lacking the expertise to protect or handle it properly.
 
No just telling it like it is,this is what happened to me...all these people think their data is ok because they said it was fixed and based on my personal experience it is clearly not...
 
Can a Moderator PLEASE fix the title of this thread, "Scan data is bugged - Hold off on exploring" or similar. Very misleading I set up a Conda explorer yesterday as it was suggested the issue was fixed.

Thanks

Nutter
 
Can a Moderator PLEASE fix the title of this thread, "Scan data is bugged - Hold off on exploring" or similar. Very misleading I set up a Conda explorer yesterday as it was suggested the issue was fixed.

Thanks

Nutter

clear your cache, the thread title reads: 'Notice: Scan data bug fixed' for me.


Still awaiting confirmation of the new Bugs since this happened though, missing stars/planets in the navigation panel but they're clearly visible.
 
clear your cache, the thread title reads: 'Notice: Scan data bug fixed' for me.


Still awaiting confirmation of the new Bugs since this happened though, missing stars/planets in the navigation panel but they're clearly visible.

That was a suggested title lol - Had me confused there !
 
aahh yes I see sorry my bad :D

Totally agree, it's certainly not fixed yet but I can only hope a patch sometime this week will help, usually we get them shortly after a main release but we're now one week after and nothing yet.
 
Before 1.4 hit I was complaining there weren't any changes to exploring in 1.4.

Now I wish there weren't any changes to exploring in 1.4.

Got to be careful what I wish for.
 
aahh yes I see sorry my bad :D

Totally agree, it's certainly not fixed yet but I can only hope a patch sometime this week will help, usually we get them shortly after a main release but we're now one week after and nothing yet.

We have had patches over the weekend - all server side presumably.

The point that needs to be stressed, for the umpteenth time, is that whilst they may have found and fixed some bugs, there are clearly still issues. At best, anyone exploring now risks losing the exploration data that they gather. There may be no problems for most of us, but I would not bet on it.

So, as Nutter said, we need a thread title that says that the state is still questionable, and not one that implies the problems are over, as the current one does. Frankly, anyone who wants to know the current state, should watch threads like this, and see what real explorers are saying they are experiencing. FD have announced that it is fixed too many times when it is clearly not 100% correct. It could, of course, be connected with the various connection issues that many are reporting, so that in one sense there is not a problem with the exploration scan code. Whilst that may matter for internal finger pointing, all that matters for us is that it cannot be trusted yet.
 
Last edited:
Before 1.4 hit I was complaining there weren't any changes to exploring in 1.4.

Now I wish there weren't any changes to exploring in 1.4.

Got to be careful what I wish for.

I think we may have a self-fulfilling prophecy here. I did not see FD comment about the exploration server update during the beta - though I did not follow that as closely as I might have done because - you guessed it - there was doodlesquat of interest for players whose primary occupation is exploring. What we do not, as far as I am aware, know is whether the beta test environment included a test of the new exploration server or not. If it did not then we are certainly justified to complain at FD. It may actually have been impossible to beta test, because of the nature of the change. If that was the case then FD should have been very focussed on exploration data and comments from the community, and we know they were not because of how long it took to take the issue seriously. If it was beta tested, in the sense that it was included in the beta test, then it does not seem to have been spotted by anyone. That would not surprise me at all. After all, we were expecting the doodlesquat mentioned above. I simply did not bother to beta test changes that held no interest for me. I suspect many explorers felt similarly. So if no one was out there exploring, then there was no one to spot the bug.
 
Hey everyone.
Quick update for you all from the dev team.
The bug with new scans not going through should now be fixed. Exploration data should now be working as intended.
In addition, all of the data after the 1.4 update should now be completed.
If you have any issues with the above then please contact support with as much details as possible.
In addition there were some people mentioning that they were missing data from before the update. This is still being investigated and we will update this thread as we have more information.
Once again, thank you for your patience.
Zac

Hey Zac,
thanks for the efforts. I assume your 'global' workings on this matter are now over and we're on the 'ticket by ticket' level then?

Unfortunately the update did not work for me at all. Neither for data from after the update, nor from before (which you said you're still investigating).
This is really, really frustrating. I have been idling in my ship for the greater part of a week now, switching between the forum, the GalMap and the Captain's Log add-on. If I hadn't had any verbose logging activated I'd be even more screwed I guess...

Still hoping this puzzle can or will be solved by FD in some way, because I can already see what CS will do about it if they are flooded with tickets now.

Thanks anyway!
Andrew
 
Just did about 600Ly, and everything seems to have stuck. Also, everything I have scanned (that I have checked with my EDDiscovery logs, anyway), seem to be all good.

Z...
 
Unfortunately, this! Just thought about starting a trip out again today, got about 400ly out, and this was happening in every system I jumped into. Decided to cancel the trip, go back to base, and wait until it is all properly fixed.
I would agree, the initial post from OP is VERY misleading, exploration is far from fixed. Bugs like the initial star not showing up as selectable on jumping into a system indicate issues still. It appears that no initial scan is taking place upon jumping into systems, then even when I use the discovery scanner it still doesn't show the main star as selectable. I can only select it from the System map, once it is selected there, it STILL doesn't even show in my Nav Panel.
I certainly don't think this should be flagged as "fixed", nor should it have been de-escalated to a "ticket by ticket" priority.

P.S. I have zero interest in doing CQC "Arena" PvP. I play this game for Exploration, BH'ing, Trading, or open combat. It's my own personal opinion, but if I wanted Arena style combat, I wouldn't be playing a sandbox space MMO Sim... Therefore, please fix this sandbox element of gameplay. I'm sure it's a lot more important to a lot more people than CQC.



Still having trouble with bodies being unselectable from the ship or showing up in the side panel. I could select this star from the system map though.

View attachment 67792View attachment 67793
 
UPDATE:

Hey everyone.

Quick update for you all from the dev team.

The bug with new scans not going through should now be fixed. Exploration data should now be working as intended.

In addition, all of the data after the 1.4 update should now be completed.

If you have any issues with the above then please contact support with as much details as possible.

In addition there were some people mentioning that they were missing data from before the update. This is still being investigated and we will update this thread as we have more information.

Once again, thank you for your patience.

Zac

... but you know perfectly well why the data is missing between the backup and 1.4 drop: it was captured on the old server, and has not yet been copied across to the new one successfully. So what are they still investigating? Rather than 'some people' has anyone got that data back? Is it really 'everyone that explored between the backup and the drop of 1.4'?

If there is a next time for this sort of thing, please datestamp the various updates as that makes it easier to see what has changed and when.

My data seems to be as it was. 85 system scans missing between the backup and 1.4 drop. I have had various transaction and matchmaking errors on the little new exploration I have done, but I do not see anything obviously wrong with the data. Even when thrown out, as has happened a few times, on logging back in it has updated scans of the system I was in. So it was looking OK.
 
Last edited:
Back
Top Bottom