A simple program that scans through netLog files to populate the new visited galaxy map filter

[Vinman]

Greetings commanders,

I recently wrote a simple Python program that scans through existing netLog files to generate and populate an ImportStars.txt file.
Once executed, the resulting ImportStars.txt file can then be used with Elite Dangerous 1.7 and 2.2 to populate the new Galaxy Map Filter.

See the offical Frontier Forum Post to find out more about how the importStars.txt file can be used.

Please Note: That Elite Dangerous 1.7 & 2.2 (The Guardians) will automatically store visited systems.
Rather this program is only useful for commanders who have been fortunate enough to have access to netLog files previous to The Guardians release.

Overview of ED_Build_Visited
ED_Build_Visited was written as a personal project to include my previously visited star systems with the new Galaxy Map mechanic found in Elite Dangerous 1.7 & 2.2.
It has worked for myself and some of my real-life friends. So I thought I would make it available to anyone who might be interested in doing the same.

ED_Build_Visited was written using Python and requires that you have Python 2.7* installed.
A link to Python 2.7.12 can be found here: python-2.7.12.amd64.msi
Note: ED_Build_Visited will not work with Python 3*

Usage

1. Install python 2.7* if not installed and reboot

2. Extract (ED_Build_Visited.zip) to a location of your choice.

3. Find and copy all netLog files to [ ED_build_visited\netLogs\ ]

4. Double Click the build_visited.py icon to run the program.

5. A file called ImportStars.txt should now be in [ ED_build_visited\visited\ ]
Note: The ImportStars.txt is overwritten whenever you run the program.

6. Copy the ImportStars.txt file over to [ C:\Users\<USER NAME>\AppData\Local\Frontier Developments\Elite Dangerous\<NUMBERS>\ ]
Note: You will know if the \<NUMBERS>\ directory is correct since it will contain a file called [ VisitedStarsCache.dat ]

7. Finally, run Elite Dangerous and make sure you login to one of the following modes: Solo, Open or Private Group
Note: After around 15-60 seconds you should see a message appear providing info about how many stars have been imported into the game.

8. You should now be able to see any imported stars in the galaxy map using the new filter.


ED_Build_Visited v1.0 for MS Windows
By CMDR Vinman, 2016

Spoiler

ED_Build_Visited.zip

Signing out,
CMDR Vinman

 

[iain666]

7. Finally, run Elite Dangerous and make sure you login to one of the following modes: Solo, Open or Private Group
Note: After around 15-60 seconds you should see a message appear providing info about how many stars have been imported into the game.

For anyone else who may try this (by whatever route, I used an EDD export to generate the text file) it could take much longer than 15-60 seconds. Like nearly 10 minutes for me to get 20,000 systems imported.

So give it a while if you've got a big history.

 

[Ben Ryder]

Greetings commanders,

I recently wrote a simple Python...

Lost me. I thick as a brick layers sandwich. What does it do?

 

[Mengy]

The EDSM site can also get you your visited stars data, assuming you always fly with EDD and log your data:

The "ImportStars.txt" file is now exportable from EDSM: https://www.edsm.net/settings/export

My log has 12,527 systems in it. I didn't use EDD back for like the first half year, so that sounds right.

 

[Vinman]

For anyone else who may try this (by whatever route, I used an EDD export to generate the text file) it could take much longer than 15-60 seconds. Like nearly 10 minutes for me to get 20,000 systems imported.

So give it a while if you've got a big history.

Hi iain666, thanks for the feedback on point 7.

The amount of systems I imported was a lot less than you. I only imported around 5.5k stars, so I underestimated the time that it might take for larger imports.

When I get a chance I will update the OP to reflect your experience.