About Jan-2015 I suggested we had a filter in the galaxy map to show which systems we've visited. In 2.2 we are seemingly getting this, which is great. And unsurprisingly (for performance) this is using local storage.
But there is the unfortunate limitation that it will only show systems visited from 2.2 onwards. And I suspect, if you were to re-install ED, you'd probably lose all that data?
I'm wondering if FD could:-
1) Write a bit of clever code to check if a CMDRs visited system data is sync'd up with FDs? And if not, trickle feed an update down to the CMDR.
2) Even more simply, add a dedicated option in the Menu (or Launcher or Website) to download all visited systems (from FDs servers to local).
Option 2 sounds the simplest and would mean we'd have all the systems in our local database as we'd expect/hope. And if we have to re-install ED, this option will mean we get all that data back too. And by all means limit this to once a day/week etc, and cap any bandwidth usage etc. [See EDIT below]
NOTE: An option to filter by "Discovered" as well as "Visited" would be nice. And the proposed download feature could download that data too.
EDIT: Seems FD are already offering an import option to update visited stars, so part of this suggestion is already in place! - The VisitedStars cache (Thanks gazelle)
EDIT: Confirmation: FD's database almost certainly knows which systems you've been to (ever); In your system panel it shows "Systems Visited". This goes up when you go to a system for the first time, and does not when you revisit. Furthermore, it seems in the past FD have offered a list of systems visited.
*IMPORTANT* UPDATE (23-Sep):-
Official Comment (3-Oct)
Michael commented on the possibility of getting a download of Visited Systems from FD. While it's no suprise such a feature will not be in 2.2, at least the comment implies it might be on a list for the future.
But there is the unfortunate limitation that it will only show systems visited from 2.2 onwards. And I suspect, if you were to re-install ED, you'd probably lose all that data?
I'm wondering if FD could:-
1) Write a bit of clever code to check if a CMDRs visited system data is sync'd up with FDs? And if not, trickle feed an update down to the CMDR.
2) Even more simply, add a dedicated option in the Menu (or Launcher or Website) to download all visited systems (from FDs servers to local).
Option 2 sounds the simplest and would mean we'd have all the systems in our local database as we'd expect/hope. And if we have to re-install ED, this option will mean we get all that data back too. And by all means limit this to once a day/week etc, and cap any bandwidth usage etc. [See EDIT below]
NOTE: An option to filter by "Discovered" as well as "Visited" would be nice. And the proposed download feature could download that data too.
EDIT: Seems FD are already offering an import option to update visited stars, so part of this suggestion is already in place! - The VisitedStars cache (Thanks gazelle)
EDIT: Confirmation: FD's database almost certainly knows which systems you've been to (ever); In your system panel it shows "Systems Visited". This goes up when you go to a system for the first time, and does not when you revisit. Furthermore, it seems in the past FD have offered a list of systems visited.
*IMPORTANT* UPDATE (23-Sep):-
So it would seem:-
- There is already an import option suitable for purpose (ie: to populate the local visited database).
- FD have (in the past) produced a list of all visited systems. This could clearly easily be manipulated into the appropriate format for such an import.
- The resultant file is not large. I'd estimated 25 bytes per system, and actual examples (see #45) seem to suggest it's less than that. ie: We're typically talking about tens/hundreds of K for the file size.
- Seemingly FD need only give us a means to re-access/download the visited data (again), and this will work. And they could do that as restrictively as they like. eg: Just one request a week, given how infrequently it would be required.
Official Comment (3-Oct)
Michael commented on the possibility of getting a download of Visited Systems from FD. While it's no suprise such a feature will not be in 2.2, at least the comment implies it might be on a list for the future.
There won't be a mechanism for this as part of the 2.2 release. We appreciate the desire for it, so it will be looked at in the future, but I have no time scale for that at the moment.
Last edited: