Release EDDiscovery 18.X is now out! New modules panel upgrade and Engineering

Two things to consider there, for a feature request...
1. Surely it's useful to know there is a settlement you might be able to use, as a prompt to go look in-game and find out why it says "unknown?"
2. Given this is all volunteer data and we find holes in it all the time, appreciate you need some defensive coding so bad data doesn't break EDDiscovery, but on the other hand, if it's survivable data, I think being optimistic about whether the human will want it would be preferable. This is a discovery tool... so if you have partial data, show the partial and mark it partial?
 
This is on halt because of a critical bug, if you enabled "Sync from EDSM" don't download it now.
I'll update this post when a fix is applied.


A fixed version is now live.
 
Last edited:
is it possible that this does not work for legacy commanders (xbox) as of now? i cant seem to get any response from the journal API. neither when i authorize via xbox login nor Frontier Login
 
is it possible that this does not work for legacy commanders (xbox) as of now? i cant seem to get any response from the journal API. neither when i authorize via xbox login nor Frontier Login

Pretty sure it was decided that EDDN and other sites would not be taking data from the Legacy Galaxy CMDR's so no it shouldn't be reading your journals.
 
but eddiscovery should be using CAPI data directly from frontier. otherwise it wont make sense to login to the CAPI at all, so i'm pretty sure EDDN is not involved in the journal. i'm not trying to upload data to eddn
 
Pretty sure it was decided that EDDN and other sites would not be taking data from the Legacy Galaxy CMDR's so no it shouldn't be reading your journals.
EDDN still does accept sendings from legacy players, it's just some of the listeners that decided to not use them anymore.
And this has nothing to do with EDDiscovery, nothing changed here.

CAPI (especially the journal endpoint) is well known for being wonky. There's no solution for that, most of the time letting EDD run for a long time. And as far as users reported (we have no consoles to test it) the required account to log in is the console account (X-Box or PS), so don't log in using the Frontier account.
 
I just tested it, and setting up a console commander, it was querying the legacy CAPI server correctly.

I think this is a frontier server issue.
 
EDDN still does accept sendings from legacy players, it's just some of the listeners that decided to not use them anymore.
And this has nothing to do with EDDiscovery, nothing changed here

Ah ok, I thought they had stopped.

Anyway other news, now that I have turned off updating from EDSM it seems to be working fine, done a few hours and no issues.
 
I have some EDD behaviot I don't understand & would appreciate explained:

I have two (2) cmdrs in my journal. One is a Steam acct with over 1.2 mil entries. The second is an Epic acct with far fewer, maybe only 20k. The old acct seems to work fine but the Scan panel for the new acct is frequently all but blank except for the arrival star. When this is the case the FSS in game is completely resolved as soon as I open it even though I have never visited the system with this acct. I suspect it is because my main cmdr has been here befor.

So my question is, is this normal or is there a way I can see all the system information in the EDD Scan panel for these occurrances?
 
I suspect you're flying in the bubble where a lot of systems are pre-discovered for everyone.
There's no way EDD could cause something in game.
 
I suspect you're flying in the bubble where a lot of systems are pre-discovered for everyone.
There's no way EDD could cause something in game.
Your suspicion would be correct, however previously even bubble system properties would be fully shown in the EDD Scan panel if there was nothing to find with the FSS in game.
 
That sounds like you simply deactivated querying EDSM (or now Spansh) for data about those systems.

Screenshot 2024-02-02 114800.png
 
Back
Top Bottom