VisitedStarsCache - See all EDSM Visited Stars in your GalMap

I'm just glad there's no Journal event for the next targeted system, and no real-time database of systems - some sort of "Star Map", if you will - because then someone might just write something to produce some sort of audible alert if you were about to travel to a system that'd already been visited, and that'd make the whole reasoning behind killing the Visited Stars Cache utterly pointless, and to have served no purpose other than to antagonize explorers. (Modus Operandi).


470emh.jpg
 
The idea was to disable the custom VisitedStarsCache that allowed you to see what was discovered as far as EDSM was concerned. The original intent of the file was just to show you what you had actually visited, and that should still work, with a copy of the file created by the game itself. That is, starting one fresh, or if you have one that you never replaced. However, now the game checks for some of the things that will be different with a downloaded one, and they either delete it, or cut the list short based on how many places you've actually been.

The ImportStars.txt method of repopulating it is supposed to still work. I got an answer to my support ticket about that, and the support dude talked to some of the individual developers who worked on it, and confirmed that it wasn't deliberately disabled. However, myself and several others haven't been able to get anything to import that way, so I think there's an unintentional bug preventing that method from working.

So right now the only legit way to get a working VSC file if you don't have one, is to let the game start a new one, and it'll only have your travel history from that point forward. Or if you're a good enough programmer, you can repopulate it yourself, which is the route I took to get mine back to where it would have been with my travel history had I never lost mine and had been using it continuously.
Orvidius, hello!
Can you help me find an alternative to VSC in the current patch? I realized that you found some way for yourself. Share please! I do not play the game, because I am very attached to the VSC mechanism, which now does not work.

p.s. I'm not a programmer
 
Yeah I'm trying to decide how much I can help people with this, without violating the terms of service. My script is written in perl for linux, so there's already a barrier there, if I were to distribute it. And this just rebuilds based on your journals. It's not a replacement for the custom VSC, since really, that's not practical anymore with the changes they made (which was the intent).
 
It's gonna be a rough row to hoe finishing my E cube without my custom VSC. According to the VSC now, I have almost 160,000 systems (50-60K more visited before logging) and as far as I can tell, it's a true accounting of my travels, however, the game itself is out in left field as far as being correct with the visited/non-visited systems ...It's clearly not reading the VSC correctly..at least for me anyhow. The only thing that ISN'T borked up, are my visited systems since the carrier update.

cubes.JPG
 
...
however, the game itself is out in left field as far as being correct with the visited/non-visited systems ...It's clearly not reading the VSC correctly..at least for me anyhow. The only thing that ISN'T borked up, are my visited systems since the carrier update.

Yep, the VSC file would have either been deleted and started over with that update, or it would have been culled to match the number of systems you've visited (and I have no idea how they're selected, but it's probably that the first X number of entries in the file are kept, and the rest deleted). So yeah, only your activity after the update would have been tracked properly, in either case.
 
I'm just glad there's no Journal event for the next targeted system, and no real-time database of systems - some sort of "Star Map", if you will - because then someone might just write something to produce some sort of audible alert if you were about to travel to a system that'd already been visited, and that'd make the whole reasoning behind killing the Visited Stars Cache utterly pointless, and to have served no purpose other than to antagonize explorers. (Modus Operandi).


470emh.jpg


Funnily enough, I had just exactly that idea (without any knowledge of the history here)..

Source: https://www.reddit.com/r/EliteDangerous/comments/i51v9c/got_sick_of_jumping_into_systems_only_to_find/

No audible alert (yet) but a visual one at least.

Enjoy o7
 
It's mentioned earlier in the thread, but the ImportStars.txt method of adding to systems to the list was also broken when they broke the VSC. Sorry, "fixed". Or "Appeased console players".

Anyway, it would be nice if they fixed this. If you'd like to be able to recreate your personal VSC from your Journal logs using ImportStars.txt, please add to this issue.

It would be really nice to be able to use ImportStars.txt again.
 
It's mentioned earlier in the thread, but the ImportStars.txt method of adding to systems to the list was also broken when they broke the VSC. Sorry, "fixed". Or "Appeased console players".

Anyway, it would be nice if they fixed this. If you'd like to be able to recreate your personal VSC from your Journal logs using ImportStars.txt, please add to this issue.

It would be really nice to be able to use ImportStars.txt again.
Done! I'm really doubting they did it on purpose (have you ever seen ANY change they have made to the game actually work as intended? (Even after several patches) The red icon below unvisited systems on the galmap no longer exists (but the white one still does), and they have added a new icon if there is a carrier present. Either way, a useful tool to separate the wheat from the chaff is lost, and I doubt we will ever see it fixed.
 
Yeah, the response from my support ticket basically said they talked to the devs who originally built it, and to their knowledge it was not intentionally disabled, so definitely a bug.
 
Considering that they do a lot of stealth changes not mentioned in the patch notes, and just as frequently mention things in the patch notes without actually fixing them, it's anyone's guess.

I'd say that if it's in the patch notes for the next major update, there will be a 50% chance of it working. If it's not mentioned, there's maybe a 15% chance that it will mysteriously start working again. ;) :D
 
Back
Top Bottom