ad1df66379
Previously the Sampler overlay notification was sticky (ie. it stuck around until you completed sampling). This change adds an option (by request) to make it not-sticky (so it disappears after the configured timeout, like other notifications). Default will be sticky. It was also observed that for non-English users, all the colony distances were 100m (effectively default) because the Genus_Localised field was being used for lookups, failing and thunking to default. Furthermore, the notification would display a mix of languages. With this update, we use the identifier (ie. the Genus field) and map to English names and this should provide consistent language output and lookup of colony distances. This also adds support for Horizons bios that can be sampled. 2 minor changes to support the ui-overhaul: - Assign grid column widths - Add Sender to NotificationArgs for the sampler status overlay. Supercedes #120
Elite Observatory Core
Tool for reading/monitoring Elite Dangerous journals for interesting objects. Successor to the original Elite Observatory, rewritten from scratch using .NET 6.0.
IMPORTANT
Observatory Core and it's associated plugins are currently in a state of ongoing development and are neither feature-complete nor using a finalised UI.
Omissions to current functionality include:
- Integration with Frontier's Companion API
- Data submission to IGAU
- Non-grid plugin UI options
- Light mode
- And more...
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 wiki pages:
If you're interested in Custom Criteria for Explorer in particular you can find the documentation for writing them in the project wiki.
If you want to chat or collaborate with other users of Observatory you can find us either in the Elite Dangerous forum thread for Observatory, or on the Elite Observatory Discord.
For information on how to create a plugin, refer to this article about ObservatoryFramework.
Prerequisites for use
All you need is .NET 6, which should be installed automatically by the Observatory Core installer.
The portable build has no prerequisites due to bundling the .NET runtime along with the program, though this does make the exe commensurately larger.
Prerequisites for building
C# 9.0, .NET 6.0, and ObservatoryFramework.