Notice Scan data bug fixed

[GG7]

Hopefully it isn't terribly complex issue to fix.

Considering the number of systems out there, I would be willing bet that this is probably the most complex system in the game. I definitely do not envy the dev team trying to parse out what is going south in all of this data. Pleased that they appear to have resolved it, but at the same time, I wouldn't be at all surprised if issues remain.

I'm holding off any serious exploration until enough time has passed that we are completely sure that all of these issues have indeed been addressed.

 

[bitstorm]

Ahhh it's not fixed?

I've just spent the last 4 hours exploring given this thread says it's fixed.

We've been told it's "fixed" like 3 or 4 times now? =(

 

[GJ51]

Why does this thread have 'fixed' written in red when it's not?

Because FD are just like politicians.

No credibility

Nothing to see here, it's all better, just move along, go about your business...

Through the whole process, some guy in the back room finds something and goes, "Ah, there it is, I see the problem." Zac and the band rush to report it's all good now, until they find out the script they ran didn't fix the problem and they are back to square one.

Such an embarrassment. They really need to hire a qualified/competent db admin.

The excuses are all worn way too thin.

 

[James Son]

Hmm, this looks strange. I was visiting Sagittarius A* on 4th October (it's confirmed here https://forums.frontier.co.uk/showthread.php?t=159651&page=31&p=2890297&viewfull=1#post2890297) but when I go back to Sagittarius A*, the galaxy map tells me there is no data available.
May I assume this is not how it should be?
Should I return to rescan? File a bug ticket? I am only 2k LY away, so it is still possible.

FD should fix it but don't bet on it. Some things may be un-fixable. If you're so near, turn back and rescan it, just in case. If you haven't been to Great Annihilator, i suggest you visit that too (it's less than 3KLys away from Sag A*). It's not as big as Sag A* but it's a landmark, it would be nice to have it in your logs.

Unfortunately, I did not keep a travel log. Maybe this is a good time to start a log.

Yup, i've done that because of this bug. I'm using Captains Log. I'm not sure it's the best program out there but it will do for now...

 

[AnnuverScotinExile]

Why does this thread have 'fixed' written in red when it's not?

PR, at a guess. I have reported the thread to the mods, asking them to change the title to reflect reality, noy what FDs PR department would like the truth to be. If nothing happens in the next half hour or so, I suggest you all report it to the mods.

- - - Updated - - -

Hmm, this looks strange. I was visiting Sagittarius A* on 4th October (it's confirmed here https://forums.frontier.co.uk/showthread.php?t=159651&page=31&p=2890297&viewfull=1#post2890297) but when I go back to Sagittarius A*, the galaxy map tells me there is no data available.
May I assume this is not how it should be?
Should I return to rescan? File a bug ticket? I am only 2k LY away, so it is still possible.

Unfortunately, I did not keep a travel log. Maybe this is a good time to start a log.

If you are that close, then go and rescan. That scan is worth over 300K

 

[EUS]

Hmm, this looks strange. I was visiting Sagittarius A* on 4th October (it's confirmed here https://forums.frontier.co.uk/showthread.php?t=159651&page=31&p=2890297&viewfull=1#post2890297) but when I go back to Sagittarius A*, the galaxy map tells me there is no data available.
May I assume this is not how it should be?
Should I return to rescan? File a bug ticket? I am only 2k LY away, so it is still possible.

Unfortunately, I did not keep a travel log. Maybe this is a good time to start a log.

If you've had verbose logging on since your exploration started, you may want to pick up and install captain's log (check the exploration tools sticky in the exploring forum), and it will read your netlog, and create a database of all your travels.

As mentioned go back and re-scan all you can, I wuoldn't rely on FD to fix missing exploration data.

 

[Nutter]

If you are that close, then go and rescan. That scan is worth over 300K

If it works of course!

 

[CMDR Nirnroot]

Just logged in first time since Sunday. The system I scanned before logging off is showing all planets scanned on the system map and all planets unexplored on the navigation map. Have submitted a report.

Given this and all the recent posts I have just read on this thread I think I will give ED a miss until it is confirmed that all is well not only by FD, but also by players as well.

 

[serge]

Yup, i've done that because of this bug. I'm using Captains Log. I'm not sure it's the best program out there but it will do for now...

That means for me: back to the windows version. Or is there anything similar to Captains Log on the mac? (at least, I haven't seen anything mentioned in the mac forums, I did not look too hard though.)
And thanks for the hint to the Great Annihilator, I will definitely go there too.

 

[Greeboski]

by far the majority of my data is still missing from when i launched till the relese of cqc , so i put in the advised report to support.

anyone got a clue when this issue will be fixed ?

 

[AnnuverScotinExile]

by far the majority of my data is still missing from when i launched till the relese of cqc , so i put in the advised report to support.

anyone got a clue when this issue will be fixed ?

I think the obvious answer to that is 'NO'. I include FD in 'anyone'.

 

[LOSBOT]

If they wrote a log to the client then fixing old data would be simples!

I wonder why no one has suggested that before.

It does log to the client, to some extent. If verbose logging is turned on, then there's a log showing what systems you were in and when you went there.
That's how programs like "Captain's Log" works. It reads that data and parses the log files as you play. The files are so small, I wish they'd turn that on by default instead of disabling it with every updates, forcing some of us to turn it back on.

 

[Astronut57]

I've still not moved from my current system since this bug showed up and I'm not moving until the data gets restored or declared unrecoverable in which case I'll backtrack and rescan.
.
In the meantime I've just submitted a ticket with details of at least some the systems I seem to have lost. I haven't been keeping detailed records other than scribbled notes for waypoints but I do make system map screenshots of previously undiscovered ELW's, neutron stars, black holes, etc.
.
Once this gets resolved one way or the other I'll be running Captain's Log to keep records.

 

[Greeboski]

Just found another interesting feature. Please see if it affects you too when entering systems in the GalMap.

When searching for 'Flya Eohn XS-W b20-0' the navigator homes in on 'Flya Eohn XS-W b20-1' instead. I tried it out with several other zero endings and all searches homed in on the next higher digit, so mostly '1'.

New feature?

I think that's quite a well known bug and it seems to be systems ending in a hyphen and a single digit.
eg. -1 will go to -10, -11, -12, -13, -14 etc. and then -1 if you keep clicking the search key.
If you're looking for a system ending in -0 keep clicking the search key and it'll eventually cycle to it.

Had the same problem with -a and -b single - char ending systems

this is a well known bug caused by systems with 2 spaces in the names , which could have a couple of billion combinations ( blah sector xx-x xx-x gives 36^6 = 2,176,782,336 combos) but i hope there arnt that many of one name arcitype

 

[Promius]

Think I'm just gonna self destruct and go back home and go back to Bounty Hunting.

 

[Jack Crow]

Has anyone seen any data restored or available to sell that wasn't there before today? I have not. Just curious if anyone has had positive results.

 

[pum1127]

I have just docked after a trip to Sag A, I scanned about 300 neutron stars between the 3rd and the 5th of October, so was a bit concerned as since the server upgrade and 1.4 patch none of those systems show as scanned on my Galaxy map.

Having docked I went into the exploration data selling screen and cross referencing with Captains log, the systems I scanned between the 3rd & 5th of October are there, with the correct selling values for neutron stars and black holes. I have to say I am quite relieved

I have not sold any data yet, so cannot confirm whether the 1st discoverer bonus is working, I am waiting to see if Frontier sort out the galaxy map tomorrow.

Hope this puts some peoples minds at rest.

 

[iain666]

Has anyone seen any data restored or available to sell that wasn't there before today? I have not. Just curious if anyone has had positive results.

I can now see some systems visited since the 1.4 roll out shown as such in the galmap (that I couldn't previously, I've not found any that I can't see at all). System data is incomplete though (system names appended to open ticket...).

Everything from the weekend before remains missing.

 

[ByteMe]

I have just docked after a trip to Sag A, I scanned about 300 neutron stars between the 3rd and the 5th of October, so was a bit concerned as since the server upgrade and 1.4 patch none of those systems show as scanned on my Galaxy map.

Having docked I went into the exploration data selling screen and cross referencing with Captains log, the systems I scanned between the 3rd & 5th of October are there, with the correct selling values for neutron stars and black holes. I have to say I am quite relieved

I have not sold any data yet, so cannot confirm whether the 1st discoverer bonus is working, I am waiting to see if Frontier sort out the galaxy map tomorrow.

Hope this puts some peoples minds at rest.

Thanks for the info, will be back from Sag A soon so good to hear this from you. Hopefully they will have the rest sorted out soon!

 

[Commander William Diffin]

Just found another interesting feature. Please see if it affects you too when entering systems in the GalMap.

When searching for 'Flya Eohn XS-W b20-0' the navigator homes in on 'Flya Eohn XS-W b20-1' instead. I tried it out with several other zero endings and all searches homed in on the next higher digit, so mostly '1'.

New feature?

I find that the navigator ignores the last digit of system names you type into the navigation panel and homes in on the same system name but ending -1. Click the star name on the navigator panel again and the Galaxy Map homes in on another system with the same name but ending in a different number again. Keep clicking and it'll go through all the systems with the same name but a different numerical suffix until eventually it'll home in on the actual system you typed in the first place. This feature was present before the 1.4 bomb and I always assumed it had something to do with the limitations of the Galactic procedural generator.