Last edited:
Notice Scan data bug fixed
- Thread starter Zac Antonaci
- Start date
Main star not selectable and not in map and initial system scan on jump is also seemingly related to the navigation ring not displaying on the star as you jump into system which makes for tense scooping or aiming away from an invisible ns star until you honk scan
Also sitting in a system that has 2 stars and according to scans and system map but clearly I am.parked next to a third M class start and an orbiting red dwarf can't select then or scan them and not visible in any maps but I can fly up to them.
Confirmed log in log out the persist.
Also sitting in a system that has 2 stars and according to scans and system map but clearly I am.parked next to a third M class start and an orbiting red dwarf can't select then or scan them and not visible in any maps but I can fly up to them.
Confirmed log in log out the persist.
I'm not actually seeing any problems at the moment despite playing with a lousy 3G connection. What I do see however is an at least 3 fold increase of hyperjump times.
Last edited:
Many people are still having issues. The point where there only some individual border cases giving problems has definitely NOT been reached yet.
According to my galaxy map the 500 systems I scanned on October 3, 4, 5 are still missing.
Systems scanned after the update still look buggy with all these 'blackened' / missing astronomical bodies. And I'm pretty sure that I'm also missing scans that I did after the update.
FD, please tell me that you have the backups, logs and know-how to fix the data... I'll be patient for a solution. But I am not willing to just simply accept data corruption/loss at such a large scale.
According to my galaxy map the 500 systems I scanned on October 3, 4, 5 are still missing.
Systems scanned after the update still look buggy with all these 'blackened' / missing astronomical bodies. And I'm pretty sure that I'm also missing scans that I did after the update.
FD, please tell me that you have the backups, logs and know-how to fix the data... I'll be patient for a solution. But I am not willing to just simply accept data corruption/loss at such a large scale.
Last edited:
Any chance the updates in the First Post could have a time/date stamp? I know it shows the last edited time, but when it contains several updates, it can be difficult to keep track if you are not visiting these pages daily.
You refer to 'today' or 'overnight' and 'tomorrow' or 'soon™' but these mean nothing without a reference point.
You refer to 'today' or 'overnight' and 'tomorrow' or 'soon™' but these mean nothing without a reference point.
Last edited:
I can confirm that I see no change with respect to the reported bug, it is still persistent. Systems scanned on & after 3rd Oct are either not accessible from the Galaxy map or System Map shows the central sun (as unexplored) and one black, what appears to be, planet on many different maps (a total of 45 I have made screenshots of). What's the point of further continuing with the exploration, if these are not solved? I am on hold since last Friday...
Like many others before me already made it very clear: we find the losses not acceptable (assuming it is not fixable). As in the past bugs, like the instant billionaires club, and myself victim of 2 previous bugs compensated with a couple of million credits, I would find it morally & principally acceptable to be compensated by ingame credits for the exploration losses because of this bug (loss of playtime = game credit). No point on letting your customers waiting in the middle of virtual nowhere, I don't have 2 accounts, and I am no fan of CQC. It will also solve the ongoing negative publicity on this bug in the gaming community, people will go on their business and FD can focus on more important things.
I have created a ticket, no response so far...
Like many others before me already made it very clear: we find the losses not acceptable (assuming it is not fixable). As in the past bugs, like the instant billionaires club, and myself victim of 2 previous bugs compensated with a couple of million credits, I would find it morally & principally acceptable to be compensated by ingame credits for the exploration losses because of this bug (loss of playtime = game credit). No point on letting your customers waiting in the middle of virtual nowhere, I don't have 2 accounts, and I am no fan of CQC. It will also solve the ongoing negative publicity on this bug in the gaming community, people will go on their business and FD can focus on more important things.
I have created a ticket, no response so far...
Whilst compensation in credits for any permanent losses (if there proves to be any) would obviously be much better than no compensation, mere credits misses the two things that actually matter most to me. After all, if I was that fixated on credits I would not be exploring in the first place. It is the loss of the credits towards Elite status, and the missing 'first found' tags that matter most to me.
Let's just hope that it does not come to that.
I agree, but better something than nothing if our records prove to be lost to the void.
Ditto.
I can also confirm that there are some systems i visited 5 and 9/10 (which i kept track of), in which i can now see the sun only, even though i had certainly performed a d-scan. Others are reported as unexplored even though i can see their system map. I remember in at least one system i had explored the sun and now is shown as unexplored.
It seems that some data have actually been lost due to the bug. I did not keep a full track of what i explored until 2-3 days ago (thank you Captain's Log) so it seems several system's data mau have been lost, perhaps even important ones.
Thanks for the response, Michael. At this point should we be engaging Support and providing netlogs et al? It is not really clear to me from the communications so far if explorers should be proactively engaging Support on a case-by-case basis, or if doing so is simply adding noise to an effort that will resolve this issue for everyone.
I would also like to clarify one detail that remains somewhat ambiguous regarding the issue severity: can you or anyone else at FD authoritatively confirm whether the "missing" data and systems showing as "unexplored" reflect scan data that is truly missing and for which we will not receive credit unless it is fixed... or if this is simply a map display issue that affects which systems appear to us as explored?
This is not a trivial distinction. If our scan data is safe and this is merely a display issue to sort out, then we can continue exploring. But if there is any possibility that the scan data is lost, then we are stuck and cannot do anything until we know for sure... because if the data is lost then we have to backtrack thousands of LYs and re-scan an insane number of systems--an incredibly tedious and un-fun chore that we want to avoid unless it is absolutely necessary.
Last edited:
My records are not lost to the void. They are sitting on my computer. It might start to get nasty when there are players who can provide records showing what is missing, and FD still refuse to correct stuff. Which they may well do - time is money, and it will take time and effort to do the corrections, even if the tools to do so exist. If there are no tools, then it will take time and money to write the tools. I can quite understand why they may want to say 'NO'. As before, let's just hope they sort it all out.
If they wrote a log to the client then fixing old data would be simples!
Last edited:
The data I sold today gives forst discoveries but then I look on the system map and it says validating...it's not fixed this is a complete joke I lost alot of respect for this company...
Zac/michael you say it's ok to sell data but I just sold data and went back to look at the first discoveries I was awarded and it says validating instead of my name...I really hope this will be resolved soon and stop telling people it's fixed when it's not...I can tell you right now it's not gonna go well for frontier if this persists.
I agree its not the credits but the credits for rank... also i only started running captiains log becaus of the bug so i cant prove my 300 odd missing systems except for the excruciating hours it took to get to where i am now and the missing systems between where i am and where i was before patch, pretty much lost 300 scan from the EOK flyuae systems.
- - - Updated - - -
if this happens to me when i go to cash in my 1900 systems i have onboard i will be as 1400 of those are first discoveries...
on a side not i also have now dropped to 92% hull health because of jumping into system where i cannot see navigation lines and go to super cruise away from jump point and hit the neutron star edge because i cant see where the thing is without waiting the 15 seconds to scan.
and then again while scooping and the border line is not visible got a bit close and it dropped me next to a white star and crisped my hull up nicley, this never ever happened in the previous 1800 odd jumps prior to patch.
- - - Updated - - -
if this happens to me when i go to cash in my 1900 systems i have onboard i will be as 1400 of those are first discoveries...
on a side not i also have now dropped to 92% hull health because of jumping into system where i cannot see navigation lines and go to super cruise away from jump point and hit the neutron star edge because i cant see where the thing is without waiting the 15 seconds to scan.
and then again while scooping and the border line is not visible got a bit close and it dropped me next to a white star and crisped my hull up nicley, this never ever happened in the previous 1800 odd jumps prior to patch.
Last edited:
Avago Earo
Banned
Why does this thread have 'fixed' written in red when it's not?
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.
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.