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

Twisten Spinn

T
Can someone point me towards some instructions on how to add an api (edsm) to EDDiscovery? I clicked on everything, I don't see where to add. Thanks!
I see the api at edsm and have done the process before for another game, I just don't see where to physically add it to EDDiscovery.
 

DeeJayMMM

D
Twisten Spinn said:
Can someone point me towards some instructions on how to add an api (edsm) to EDDiscovery? I clicked on everything, I don't see where to add. Thanks!
I see the api at edsm and have done the process before for another game, I just don't see where to physically add it to EDDiscovery.
Click to expand...
in the application, click tools then settings and where it says commanders, double click on your commander name and it will pop up a panel to enter the details.
 

microwar

microwar
I have a problem where i go to a system i already scanned, and i only see the main star in EdDiscovery. New systems i scan will show up correctly.
 

varonica

varonica
microwar said:
I have a problem where i go to a system i already scanned, and i only see the main star in EdDiscovery. New systems i scan will show up correctly.
Click to expand...

There's a setting for that, you can either have it tset to not show any data at all until you have scanned, or to show all the data available for the system in EDDiscovery.

It's in the history panel, "show/hide body data from EDSM" with that off it won't load data from EDSM into the systems view panel unless you scan them yourself.
 
Last edited:

Eahlstan

E
microwar said:
I have a problem where i go to a system i already scanned, and i only see the main star in EdDiscovery. New systems i scan will show up correctly.
Click to expand...
If you scanned it an deleted the journals containing those scans (or you scanned it at a time when journals weren't a thing) EDD is unable to know anything about that system from your local data. (You might be able to get data from EDSM as varonica pointed out).
If you scanned them at a time when EDD was able to read the journal (and therefor has the data in its DB) you might have limited the data EDD loads on the settings panel.
 

Alkibiades

Alkibiades
Hello, I have a general questions about 3rd party tools and the logs.

Yesterday I went to a system with guardian ruins. It was the first visit and I used the fss on all bodies in the system.

Code: 
{ "timestamp":"2022-01-20T19:22:26Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Col 173 Sector JS-J d9-76 14 b", "BodyID":60, "Parents":[ {"Star":57}, {"Star":0} ], "StarSystem":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "DistanceFromArrivalLS":2746.919989, "TidalLock":true, "TerraformState":"", "PlanetClass":"Rocky body", "Atmosphere":"", "AtmosphereType":"None", "Volcanism":"", "MassEM":0.009051, "Radius":1455199.750000, "SurfaceGravity":1.703540, "SurfaceTemperature":241.373367, "SurfacePressure":0.000000, "Landable":true, "Materials":[ { "Name":"iron", "Percent":19.721300 }, { "Name":"sulphur", "Percent":19.276188 }, { "Name":"carbon", "Percent":16.209278 }, { "Name":"nickel", "Percent":14.916367 }, { "Name":"phosphorus", "Percent":10.377458 }, { "Name":"manganese", "Percent":8.144696 }, { "Name":"germanium", "Percent":5.677694 }, { "Name":"zirconium", "Percent":2.290050 }, { "Name":"niobium", "Percent":1.347846 }, { "Name":"yttrium", "Percent":1.177930 }, { "Name":"mercury", "Percent":0.861197 } ], "Composition":{ "Ice":0.000000, "Rock":0.910741, "Metal":0.089259 }, "SemiMajorAxis":1690058708.190918, "Eccentricity":0.000182, "OrbitalInclination":-0.002242, "Periapsis":58.561540, "OrbitalPeriod":243388.438225, "RotationPeriod":240617.733313, "AxialTilt":0.311999, "WasDiscovered":true, "WasMapped":true }
{ "timestamp":"2022-01-20T19:22:28Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Col 173 Sector JS-J d9-76 14 a", "BodyID":59, "Parents":[ {"Star":57}, {"Star":0} ], "StarSystem":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "DistanceFromArrivalLS":2747.191932, "TidalLock":true, "TerraformState":"", "PlanetClass":"Rocky body", "Atmosphere":"hot thick water atmosphere", "AtmosphereType":"Water", "AtmosphereComposition":[ { "Name":"Water", "Percent":100.000000 } ], "Volcanism":"minor metallic magma volcanism", "MassEM":0.003743, "Radius":1088461.000000, "SurfaceGravity":1.259264, "SurfaceTemperature":936.819946, "SurfacePressure":5734139.500000, "Landable":false, "Composition":{ "Ice":0.000000, "Rock":0.910741, "Metal":0.089259 }, "SemiMajorAxis":1015545725.822449, "Eccentricity":0.000448, "OrbitalInclination":-0.058482, "Periapsis":329.412790, "OrbitalPeriod":113369.578123, "RotationPeriod":111211.875510, "AxialTilt":0.483670, "WasDiscovered":true, "WasMapped":false }
{ "timestamp":"2022-01-20T19:22:28Z", "event":"FSSAllBodiesFound", "SystemName":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "Count":55 }
{ "timestamp":"2022-01-20T19:22:31Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2022-01-20T19:22:33Z", "event":"Music", "MusicTrack":"SystemMap" }
{ "timestamp":"2022-01-20T19:23:24Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2022-01-20T19:23:48Z", "event":"Music", "MusicTrack":"SystemMap" }
{ "timestamp":"2022-01-20T19:26:36Z", "event":"ApproachSettlement", "Name":"$Ancient:#index=1;", "Name_Localised":"Ancient Ruins (1)", "SystemAddress":2622153001331, "BodyID":60, "BodyName":"Col 173 Sector JS-J d9-76 14 b", "Latitude":37.644558, "Longitude":-166.447784 }
{ "timestamp":"2022-01-20T19:26:36Z", "event":"ApproachSettlement", "Name":"$Ancient:#index=2;", "Name_Localised":"Ancient Ruins (2)", "SystemAddress":2622153001331, "BodyID":60, "BodyName":"Col 173 Sector JS-J d9-76 14 b", "Latitude":50.385384, "Longitude":-105.941895 }
{ "timestamp":"2022-01-20T19:27:36Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2022-01-20T19:27:37Z", "event":"Music", "MusicTrack":"SystemAndSurfaceScanner" }
{ "timestamp":"2022-01-20T19:27:44Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2022-01-20T19:27:45Z", "event":"Music", "MusicTrack":"SystemMap" }
{ "timestamp":"2022-01-20T19:27:48Z", "event":"SAAScanComplete", "BodyName":"Col 173 Sector JS-J d9-76 14 b", "SystemAddress":2622153001331, "BodyID":60, "ProbesUsed":2, "EfficiencyTarget":4 }
{ "timestamp":"2022-01-20T19:27:48Z", "event":"SAASignalsFound", "BodyName":"Col 173 Sector JS-J d9-76 14 b", "SystemAddress":2622153001331, "BodyID":60, "Signals":[ { "Type":"$SAA_SignalType_Guardian;", "Type_Localised":"Guardian", "Count":2 } ] }
{ "timestamp":"2022-01-20T19:27:48Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Col 173 Sector JS-J d9-76 14 b", "BodyID":60, "Parents":[ {"Star":57}, {"Star":0} ], "StarSystem":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "DistanceFromArrivalLS":2746.907756, "TidalLock":true, "TerraformState":"", "PlanetClass":"Rocky body", "Atmosphere":"", "AtmosphereType":"None", "Volcanism":"", "MassEM":0.009051, "Radius":1455199.750000, "SurfaceGravity":1.703540, "SurfaceTemperature":241.373367, "SurfacePressure":0.000000, "Landable":true, "Materials":[ { "Name":"iron", "Percent":19.721300 }, { "Name":"sulphur", "Percent":19.276188 }, { "Name":"carbon", "Percent":16.209278 }, { "Name":"nickel", "Percent":14.916367 }, { "Name":"phosphorus", "Percent":10.377458 }, { "Name":"manganese", "Percent":8.144696 }, { "Name":"germanium", "Percent":5.677694 }, { "Name":"zirconium", "Percent":2.290050 }, { "Name":"niobium", "Percent":1.347846 }, { "Name":"yttrium", "Percent":1.177930 }, { "Name":"mercury", "Percent":0.861197 } ], "Composition":{ "Ice":0.000000, "Rock":0.910741, "Metal":0.089259 }, "SemiMajorAxis":1690058708.190918, "Eccentricity":0.000182, "OrbitalInclination":-0.002242, "Periapsis":58.561540, "OrbitalPeriod":243388.438225, "RotationPeriod":240617.733313, "AxialTilt":0.311999, "WasDiscovered":true, "WasMapped":true }
{ "timestamp":"2022-01-20T19:28:16Z", "event":"Music", "MusicTrack":"Supercruise" }
{ "timestamp":"2022-01-20T19:29:02Z", "event":"ApproachBody", "StarSystem":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "Body":"Col 173 Sector JS-J d9-76 14 b", "BodyID":60 }
{ "timestamp":"2022-01-20T19:29:34Z", "event":"ApproachSettlement", "Name":"$Ancient:#index=2;", "Name_Localised":"Ancient Ruins (2)", "SystemAddress":2622153001331, "BodyID":60, "BodyName":"Col 173 Sector JS-J d9-76 14 b", "Latitude":50.385376, "Longitude":-105.941895 }
{ "timestamp":"2022-01-20T19:29:36Z", "event":"SupercruiseExit", "StarSystem":"Col 173 Sector JS-J d9-76", "SystemAddress":2622153001331, "Body":"Col 173 Sector JS-J d9-76 14 b", "BodyID":60, "BodyType":"Planet" }

My question is does the fss give you info about the existence of things on the planets in the raw log or does the ApproachSettlement event come from selecting the body as target?

I need some god damn visual notification for guardian ruins in a 3rd party tool. My eyes are starting to hurt. Did frontier specifically make it so that its impossible and you must find it yourself in the systemmap / the nav panel?
 

varonica

varonica
Alkibiades said:
I need some god damn visual notification for guardian ruins in a 3rd party tool. My eyes are starting to hurt. Did frontier specifically make it so that its impossible and you must find it yourself in the systemmap / the nav panel?
Click to expand...

That would be Observatory with MattG's signals plugin right?
 

varonica

varonica
Eahlstan said:
No.
FSSing only writes features (geological/biological) to the journal.
To get locations (human/guardian/...) in the journal you have to map the body.
Click to expand...

I'm pretty sure the FSS tells you if there are human or alien signals on or in orbit around a body, I thought everyone knew that! You won't get locations on the body, you will get the info they are there. You get "features" at the top where geo and bio show, and "Locations" further down where human, guardian and thargoid signals show.
 

Alkibiades

Alkibiades
I think so as well after reading the logs. The game gives you the exact locations before you mapped the body.

Ok I'll get that and will test it in a guardian system I havent been to.
 

varonica

varonica
Alkibiades said:
Flew to Vela Dark Region WJ-Q b5-8, unfortunatly the plugin does nothing.
Click to expand...

That's disappointing, mind you then a custom criteria may do the job, I am assuming the info about the location is passed to the journal on FSS, did that work ok, I know the plugin works for NSP's and other stuff but obviously not for human/guardian/thargoid stuff. As long as it's passed to the journal from the FSS as part of the planet data it should be possible to capture it and generate a popup using a custom criteria.

I will look into that.
 

Alkibiades

Alkibiades
And now to something completly different...

Can you pleeeeease colour code the edsm toggle for on or off (I use a popup on the 2nd monitor).

greenllk72.jpg

redgrj58.jpg
 

Eahlstan

E
varonica said:
I'm pretty sure the FSS tells you if there are human or alien signals on or in orbit around a body, I thought everyone knew that! You won't get locations on the body, you will get the info they are there. You get "features" at the top where geo and bio show, and "Locations" further down where human, guardian and thargoid signals show.
Click to expand...
In game: yes.
In the journal: no.
And that's the reason no third party tool can tell you if they are there without mapping the body.
 

varonica

varonica
Eahlstan said:
In game: yes.
In the journal: no.
And that's the reason no third party tool can tell you if they are there without mapping the body.
Click to expand...

Ok, that seems an oversight, everything that shows on the system map using the FSS should be available in the journal in my opinion.
 

Alkibiades

Alkibiades
bug28ajhi.jpg


Hello, Im suddenly getting a strange error. I deactivated sync to edsm a long time ago because edd froze while doing it. Now I wanted to activate it again and this is the result. I have to quit the window with abort. If I deselect sync to edsm the error pops up as well. /I just realised it happens all the time with every tick box.

I did have a beta cmdr which I deleted right before I wanted to do this. This is the only change I did in edd.

But there are more problems. I cant start ed from a cmd anymore, I need to do it manually. Edd informs me that its already running and I confirm that I want to run it a second time. The other instance loads after about one hour - yes.... Then there is this error:
bugxujyp.jpg


I did not change any language settings, its always default english.

Then there is a capi authentication which pops up the browser every time I start the program. Whats that?
CAPI Awaiting Callback
CAPI Require Log in
CAPI Authorized

I dont know what changed but suddenly edd became annoying. Just as market connector who wants to authenticate every single time as well.
Solved by deleting the authentication on the frontier website and doing it again with a different browser. Also quitting the apps with a cmd does not save the user changes after an update. Lesson learned.
 
Last edited:

Alkibiades

Alkibiades
Well I dont quit the apps, I kill them :D

Code: 
taskkill /IM fraps.exe /f /t
taskkill /IM EDDiscovery.exe /f
taskkill /IM EDMarketConnector.exe /f
taskkill /IM EDLaunch.exe /f
 
You must log in or register to reply here.
Back
Top Bottom