Release EDDiscovery 19.X is out - ED Canonn Plugin is available, Python support, Latest data updates, new colonsation panel and engineering ship views

This is now on general release, after 180 odd commanders tried it for a couple of weeks:

Nice!

On the "Spansh Stations" tab, it would be really nifty if also showed if a settlement was in conflict and at what threat level i.e. low, medium, high for on-foot CZ's.
 
Download the Spansh dataset (use the settings panel to do this, click on reload system database) to get a better 3dmap. See
Source: https://youtu.be/ki8ECcmEkn4
video. The Spansh data has more stars and allows EDD to colour your star correctly:

1704559253748.png
 
You put the portable version of EDDiscovery into %programfiles%, even though it's on you D: drive I suspect that you told Windows to use that drive for this folder. If that's true then that's the problem. %programfiles% is a write protected folder, thus no program is able to write something into it. Put it somewhere else (e.g. D:\EDDiscovery\ ) and see if that fixes it.

Also delete the uploaded log file, it contains your name.
 
I see a lot of repeated tries to get data from EDSM. So please double check your API key. And try deactivating "Sync from EDSM" in your commanders settings.
(There are *.hlog files that contain more stuff about the web queries, but they contain sensible information, so if you can send them in a DM or on Discord that would be helpful.)
Also the content of options.txt and optionsportable.txt or any command line options you're using might be helpful.
 
Last edited:
You should still be able to activate "Sync to EDSM" as it was the "from EDSM" part that looped.
Also please send me your *.hlog files so I can try to figure out what's going on.
(Most likely it's a wrong API key, did you check that?)
 
Last edited:
Thanks.
This looks like you ran into EDSM API limit. We'll need to code something to prevent the eternal loop, the limit is rolling, so each hour after a query the query is forgotten and the limit increased by 1. If you want to get all your things you can run it until it loops, close it, wait one hour and start again until it no longer loops.
Might also be that there are no more things to catch and the empty response is throwing it off, but I don't think so.
But why don't you use your old DB that already has these things (I guess)?
 
Last edited:
We tracked the issue down. EDSM changed one of its API behaviour, so it behaves in the way it does at your machine.
It's one of the APIs queried by having "Sync from EDSM" activated, so you can still send data to EDSM by activating "Sync to EDSM".

If EDSM doesn't revert the change the query (it's the one that gets your past jumps) will be eliminated from future versions as adapting to the current API would lead to constantly running into the API limit and thus causing even more problems.
 
Loving the Spansh panel generally but suffering info overload and underload at the same time...
  • What do the numbers in the "Market" (and Outfitting and Shipyard) column mean?
  • Is there any way to add info about whether a planet is landable or not? (I don't have Odyssey so maybe if I did there's no such distinction?)
 
Everything in the station panel is landable, otherwise there won't be a station listed on the planet.
Not quite true, not quite false.
He especially asked for Horizons landables, those currently can't be spotted because Spansh doesn't have a "has atmosphere" flag in his results.
 
Last edited:
The numbers are the numbers of days old the information is - the older it is, the less reliable it is.
OK thanks. I'll watch the video too, I didn't think of doing that, my bad.
Everything in the station panel is landable, otherwise there won't be a station listed on the planet.
I am using Horizons 4.0.
There's a bunch of systems labelled Odyssey only. OK, I can't use those, and if Spansh doesn't have the data I realise you can't show it from Spansh!

I think there are more complications here though...

Odyssey-only systems look like this for a Horizons user. They still appear in the POI lists in-game but the red flash tells you it's Odyssey only.

1705403328813.png

1705403996533.png


What's interesting at Kumbaya A 4 is:

A4 is not landable for me, so I can't use either of these.
  • Kingsbury's Progress appears in the Spansh grid
  • Berezuk does NOT appear in the Spansh grid

Meanwhile over at A1 (NOT landable),
  • Heceta Landing is an outpost, so obviously I can use it, and I have docked at it.
  • It shows up in the Spansh grid BUT it does not have the parent body A1 marked, that "body" cell is just blank.

And at A2, it's decided to show me this list
1705404748595.png

Note the parent A2 is missing for two of those.
There are EIGHT planetside settlements, not four, so I should have nine (Zamyatin is orbital) in this list.

Maybe focus on A4 and A1 because A2 seems to be missing the same stations on the Spansh website so I can go talk to Spansh about that.

Note I am confident the data flow is working in general because now I know that figure is "days old" I can see all the stations I landed/docked yesterday are indeed showing as under a day old. So both the logic on my EDDiscovery installation and the roundtrip of me uploading to EDMC and that making it into Spansh are working.

I have mapped all of A4, A2, and A1 using DSS so the data should be complete.

Side note - Spansh does have atmosphere data - as a number - I think there might be a thin atmosphere/thick atmosphere rule you could use for Horizons?

Note our EDDN system and Spansh only stores information for the live Odyssey game or Horizons in the Odyssey world, not the legacy 3.8 game.
Yes, I am using live Horizons 4.0 on PC; which shares the live Odyssey world. I am submitting data via EDMC (and Discovery obviously :) )
 
Regarding A2, I just tried landing at Levada Prospecting Platform because I noticed that was one of the "missing" settlements.

It did not add itself to the list when I docked.

It DID add itself to the list, almost immediately, when I opened the market screen. (That wasn't a coincidence, I was watching the cooldown clock on EDMC and that still had 15 seconds to go.)
 
Side note - Spansh does have atmosphere data - as a number - I think there might be a thin atmosphere/thick atmosphere rule you could use for Horizons?

Those numbers aren't reliable, there are some bodies that have the requisite atmospheric pressure for landing but aren't landable so if Spansh was to use that it would report some non-landable planets as landable.
 
OK thanks. I'll watch the video too, I didn't think of doing that, my bad.

I am using Horizons 4.0.
There's a bunch of systems labelled Odyssey only. OK, I can't use those, and if Spansh doesn't have the data I realise you can't show it from Spansh!

I think there are more complications here though...

Odyssey-only systems look like this for a Horizons user. They still appear in the POI lists in-game but the red flash tells you it's Odyssey only.

View attachment 381116
View attachment 381117

What's interesting at Kumbaya A 4 is:

A4 is not landable for me, so I can't use either of these.
  • Kingsbury's Progress appears in the Spansh grid
  • Berezuk does NOT appear in the Spansh grid

Meanwhile over at A1 (NOT landable),
  • Heceta Landing is an outpost, so obviously I can use it, and I have docked at it.
  • It shows up in the Spansh grid BUT it does not have the parent body A1 marked, that "body" cell is just blank.

And at A2, it's decided to show me this list
View attachment 381118
Note the parent A2 is missing for two of those.
There are EIGHT planetside settlements, not four, so I should have nine (Zamyatin is orbital) in this list.

Maybe focus on A4 and A1 because A2 seems to be missing the same stations on the Spansh website so I can go talk to Spansh about that.

Note I am confident the data flow is working in general because now I know that figure is "days old" I can see all the stations I landed/docked yesterday are indeed showing as under a day old. So both the logic on my EDDiscovery installation and the roundtrip of me uploading to EDMC and that making it into Spansh are working.

I have mapped all of A4, A2, and A1 using DSS so the data should be complete.

Side note - Spansh does have atmosphere data - as a number - I think there might be a thin atmosphere/thick atmosphere rule you could use for Horizons?


Yes, I am using live Horizons 4.0 on PC; which shares the live Odyssey world. I am submitting data via EDMC (and Discovery obviously :) )
It's totally possible that there are many stations missing in public DBs. If no one that submits data to EDDN ever landed there, there's no way to know they exist.
You did the correct thing and landed there while submitting data, so the station is now on Spansh: https://spansh.co.uk/station/3917399808
Of course other parts of Spansh DB don't update live, so it might take a while until this station is available to the station search.

On a sidenote: A few hours ago Spansh added a "has atmosphere" field to his station search, so in a future update it might be that we lable atmospheric bodies as "Odyssey only", but as this requires some changes in the code its nothing you'll see soon.
 
Firstly thanks for the fast responses from everybody.

It's totally possible that there are many stations missing in public DBs. If no one that submits data to EDDN ever landed there, there's no way to know they exist.
Don't they get listed in FSS and DSS events? Inara knows of many more at Kumbaya for instance - I think it has everything that I can see in-game. I can't believe there are that many pilots who submit to Inara but not to EDDN one way or another; and I also can't believe every one of 35 settlements in that system has been docked at.

I can now see there's one on Spansh - Ryabokin Biological - that's not showing up on the Spansh screen anyway (and I haven't docked there.)
On a sidenote: A few hours ago Spansh added a "has atmosphere" field to his station search, so in a future update it might be that we lable atmospheric bodies as "Odyssey only", but as this requires some changes in the code its nothing you'll see soon.
Cool!
 
Back
Top Bottom