Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!

Minor bugfix release

This is a minor bugfix release, no new functionality has been added.
  • Fix some star types being identified as "unknown" in custom criteria descriptions.
  • Skip processing of journal lines which are not valid json instead of throwing error and halting processing
  • Added some leeway in the initial check for window being on-screen at startup. Being outside of desktop dimensions by small amounts (10px) will no longer reset and forget last position
 
The very first view of the rewrite! I reached a major internal milestone yesterday that I had been struggling with for some time and can finally settle into the work of getting it to do things.
1620735254922.png

Installed plugins currently populate tabs down the left side, with "Core" being the main application settings and plugin management. Currently there is only one functioning criteria, the UI is unthemed and not final, and I haven't even gotten around to setting the application icon yet, but I can finally start showing visible results.

My "to do" list is still pretty long, but things should progress relatively quickly from here! Hopefully I can have a test release with at least the Explorer plugin ready around the time of Odyssey's launch.
 
Last edited:
Minor release to remove the "?!" from the description of the "landable w/ atmosphere" check when it populates to the list, it's not quite as exciting as it would've been before. Also for those of you submitting codex data to the IGAU, this has been updated to include information from the ScanOrganic events generated by the handheld genetic sampler.

 
Fixed a tiny bug in monitoring for ScanOrganic events. Release updated. If you updated between the previous message and this one you should grab it again if you're interested in sending to IGAU, otherwise can disregard.
 
Last edited:
I guess I need to write a custom criteria to let me know when I scan a planet with Bio signs?
I would have thought that would be a built in option. I know it shows in the corner when you scan a planet but I'm usually scanning quickly and don't always notice.
Thanks for this useful tool.

Update: Actually, I don't see Bio Signs in the list of criteria. Is it possible?

I've been using EDD for years and I have some customizations in the action pack to notify me of landable planets by reading out the gravity, volcanism, etc.. but this is much better.
Now I have three different programs monitoring my logs 😮
 
Last edited:
I guess I need to write a custom criteria to let me know when I scan a planet with Bio signs?
I would have thought that would be a built in option. I know it shows in the corner when you scan a planet but I'm usually scanning quickly and don't always notice.
Thanks for this useful tool.

Update: Actually, I don't see Bio Signs in the list of criteria. Is it possible?

I've been using EDD for years and I have some customizations in the action pack to notify me of landable planets by reading out the gravity, volcanism, etc.. but this is much better.
Now I have three different programs monitoring my logs 😮
Bio signals are not written to the log until a DSS surface probe is done. Unfortunately it's impossible to determine their presence from the FSS log data.
 
Bio signals are not written to the log until a DSS surface probe is done. Unfortunately it's impossible to determine their presence from the FSS log data.
It seems neither geo nor bio is mentioned in DSS scans any longer (might change as Frontier is still working on the journal).

This one had 4 biological signals:
JSON:
{"timestamp":"2021-05-27T12:56:55Z","event":"Scan","ScanType":"Detailed","BodyName":"Spoorao GQ-P c5-22 C 1","BodyID":6,"Parents":[{"Star":4},{"Null":0}],"StarSystem":"Spoorao GQ-P c5-22","SystemAddress":6099558248754,"DistanceFromArrivalLS":365036.588307,"TidalLock":false,"TerraformState":"","PlanetClass":"Rocky ice body","Atmosphere":"thin argon atmosphere","AtmosphereType":"Argon","AtmosphereComposition":[{"Name":"Argon","Percent":99.914627},{"Name":"Nitrogen","Percent":0.085375}],"Volcanism":"","MassEM":0.056808,"Radius":2987134.5,"SurfaceGravity":2.537518,"SurfaceTemperature":76.287811,"SurfacePressure":1963.631104,"Landable":true,"Materials":[{"Name":"sulphur","Percent":20.571697},{"Name":"carbon","Percent":17.298668},{"Name":"iron","Percent":16.902061},{"Name":"nickel","Percent":12.784012},{"Name":"phosphorus","Percent":11.074903},{"Name":"chromium","Percent":7.601419},{"Name":"manganese","Percent":6.980379},{"Name":"vanadium","Percent":4.150558},{"Name":"molybdenum","Percent":1.103695},{"Name":"tungsten","Percent":0.928093},{"Name":"technetium","Percent":0.604519}],"Composition":{"Ice":0.499567,"Rock":0.336925,"Metal":0.163508},"SemiMajorAxis":133447408676.147,"Eccentricity":0.000423,"OrbitalInclination":-0.001619,"Periapsis":349.112852,"OrbitalPeriod":52760173.678398,"RotationPeriod":112197.572074,"AxialTilt":-0.352668,"WasDiscovered":false,"WasMapped":false}
 
It seems neither geo nor bio is mentioned in DSS scans any longer (might change as Frontier is still working on the journal).

This one had 4 biological signals:
JSON:
{"timestamp":"2021-05-27T12:56:55Z","event":"Scan","ScanType":"Detailed","BodyName":"Spoorao GQ-P c5-22 C 1","BodyID":6,"Parents":[{"Star":4},{"Null":0}],"StarSystem":"Spoorao GQ-P c5-22","SystemAddress":6099558248754,"DistanceFromArrivalLS":365036.588307,"TidalLock":false,"TerraformState":"","PlanetClass":"Rocky ice body","Atmosphere":"thin argon atmosphere","AtmosphereType":"Argon","AtmosphereComposition":[{"Name":"Argon","Percent":99.914627},{"Name":"Nitrogen","Percent":0.085375}],"Volcanism":"","MassEM":0.056808,"Radius":2987134.5,"SurfaceGravity":2.537518,"SurfaceTemperature":76.287811,"SurfacePressure":1963.631104,"Landable":true,"Materials":[{"Name":"sulphur","Percent":20.571697},{"Name":"carbon","Percent":17.298668},{"Name":"iron","Percent":16.902061},{"Name":"nickel","Percent":12.784012},{"Name":"phosphorus","Percent":11.074903},{"Name":"chromium","Percent":7.601419},{"Name":"manganese","Percent":6.980379},{"Name":"vanadium","Percent":4.150558},{"Name":"molybdenum","Percent":1.103695},{"Name":"tungsten","Percent":0.928093},{"Name":"technetium","Percent":0.604519}],"Composition":{"Ice":0.499567,"Rock":0.336925,"Metal":0.163508},"SemiMajorAxis":133447408676.147,"Eccentricity":0.000423,"OrbitalInclination":-0.001619,"Periapsis":349.112852,"OrbitalPeriod":52760173.678398,"RotationPeriod":112197.572074,"AxialTilt":-0.352668,"WasDiscovered":false,"WasMapped":false}
They are in the DSS scan, what you posted is the FSS scan event.

This event is written when you complete probing with the DSS:
JSON:
{ "timestamp":"2021-05-22T16:02:12Z", "event":"SAASignalsFound", "BodyName":"Synuefe BL-O d6-1 A 10 d", "SystemAddress":44954356027, "BodyID":60, "Signals":[ { "Type":"$SAA_SignalType_Biological;", "Type_Localised":"Biological", "Count":10 } ] }
 
You're right - and you're not right.

If I probe a body there are SAA events written, but there's also that detailed scan event written - I just didn't scroll up far enough to see those SAA events, so I didn't post an FSS event, it just happens to be the exactly same event triggered by a different action.

JSON:
{ "timestamp":"2021-05-27T18:21:18Z", "event":"SAAScanComplete", "BodyName":"Spoorao KG-Y d111 3 b", "SystemAddress":3820482467979, "BodyID":53, "ProbesUsed":3, "EfficiencyTarget":4 }
{ "timestamp":"2021-05-27T18:21:18Z", "event":"SAASignalsFound", "BodyName":"Spoorao KG-Y d111 3 b", "SystemAddress":3820482467979, "BodyID":53, "Signals":[ { "Type":"$SAA_SignalType_Biological;", "Type_Localised":"Biological", "Count":4 } ] }
{ "timestamp":"2021-05-27T18:21:18Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Spoorao KG-Y d111 3 b", "BodyID":53, "Parents":[ {"Planet":49}, {"Null":48}, {"Star":0} ], "StarSystem":"Spoorao KG-Y d111", "SystemAddress":3820482467979, "DistanceFromArrivalLS":2314.339088, "TidalLock":true, "TerraformState":"", "PlanetClass":"Rocky body", "Atmosphere":"thin ammonia atmosphere", "AtmosphereType":"Ammonia", "AtmosphereComposition":[ { "Name":"Ammonia", "Percent":100.000000 } ], "Volcanism":"", "MassEM":0.004309, "Radius":1139968.500000, "SurfaceGravity":1.321667, "SurfaceTemperature":154.239288, "SurfacePressure":113.054367, "Landable":true, "Materials":[ { "Name":"iron", "Percent":18.393913 }, { "Name":"sulphur", "Percent":17.955454 }, { "Name":"carbon", "Percent":15.098676 }, { "Name":"nickel", "Percent":13.912386 }, { "Name":"phosphorus", "Percent":9.666431 }, { "Name":"chromium", "Percent":8.272353 }, { "Name":"manganese", "Percent":7.596498 }, { "Name":"germanium", "Percent":5.282849 }, { "Name":"cadmium", "Percent":1.428371 }, { "Name":"niobium", "Percent":1.257126 }, { "Name":"ruthenium", "Percent":1.135942 } ], "Composition":{ "Ice":0.000000, "Rock":0.910055, "Metal":0.089945 }, "SemiMajorAxis":1097428202.629089, "Eccentricity":0.000122, "OrbitalInclination":0.156737, "Periapsis":181.975449, "OrbitalPeriod":961187.839508, "RotationPeriod":961231.334377, "AxialTilt":0.235316, "WasDiscovered":false, "WasMapped":false }
 
It's time, folks!

First testing release of Elite Observatory Core!

Rewritten from scratch using .NET 5.0 and AvaloniaUI.

Grab it here: https://github.com/Xjph/ObservatoryCore/releases/tag/0.0.15722

Note: This release does not have an installer, simply extract and run.

IMPORTANT

Observatory Core and it's associated plugins are currently in an alpha state and are neither feature-complete nor using a finalised UI. Over the coming weeks I will outline in detail what functionality is missing but still planned, and begin work on getting it to feature parity with the original Elite Observatory.

Omissions to current functionality include:

  • Voice notification
  • Checks based on surface materials (yes, there are checkboxes for them in the Explorer settings, they do not do anything)
  • Having an application icon
  • Integration with Frontier's Companion API
  • Integration with Telegram
  • Data submission to IGAU
  • More that I'm just not thinking of right now

How To Use​

Observatory Core differs from the original Elite Observatory in that it is a fully generic reader for the Elite Dangerous journal files, passing those events along to plugins to do the actual work.

Observatory will attempt to locate your Elite Dangerous journal location in its default location, though other locations can be specified from the settings in the "Core" application tab. Due to the variety of possible system configurations this automatic detection does not function under Linux, so all Linux users will need to browse for the correct location.

The "Read All" button will read all journal files in the specified folder, handing their contents over to all loaded worker plugins. "Start Monitor" will begin watching files in the journal folder for changes, and pass new journal lines as they are created, as well as all changes to the status.json file, over to the worker plugins.

In addition to updating the content of their respective UI tabs, some workers can also send notifications, which will be distributed to all notifier plugins, as well as be passed to Observatory Core's native notification popup.

For specifics on what each plugin does, please refer to their respective repositories:
For information on how to create a plugin, refer to the repository for ObservatoryFramework.
 
Last edited:
Looks nice at first, but the moment I click 'Start monitor' it crashes without any error message.
Turns out "Observatory will attempt to locate your Elite Dangerous journal location in its default location" doesn't work and the time I set a directory it didn't crash any longer.
 
Looks nice at first, but the moment I click 'Start monitor' it crashes without any error message.
Turns out "Observatory will attempt to locate your Elite Dangerous journal location in its default location" doesn't work and the time I set a directory it didn't crash any longer.
I've seen a few reports of that, will hopefully have a fix early next week!

I'll be the first to admit it's a little rough at the moment, and would still recommend the original Elite Observatory for regular day to day use. Thanks to everyone willing to test!
 
Awesome! I'll try it in-game tomorrow, but it's reading my journals just fine ATM.

I don't understand how to make custom criteria work. I tried copying the text of your example into a file in the default location with the default name and nothing is happening.
 
Back
Top Bottom