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

Well, I guess the first question is are you actually pledged to my patreon? I had to remove free access to Herald a while back when usage costs suddenly spiked and I was on the hook for Azure bills in excess of $300/mo. I don't see any members matching your forum name, but you could easily be under a different name there.

If you have your own azure account or openai voice service available you can change the herald settings to use that without needing to pledge.

As for bioinsights, I think that looks correct? It should look better once it populates with data after scanning things or reading all journals.
Cheers. And no, I'm not pledged :D which is something I need to find out how to do!

Sorry - showing my ignorance here. Best ignore my bleating for now while I grow some more brain cells.
 
Last edited:
v1.3.0 - On Top Of Things


Some tidying, some minor features, and some catch-up!

Most notably for users this release adds per-windows "Always On Top" functionality, accessible in the top-left system menu (click the icon in the corner).

Also new is a built-in way for plugins to notify that they have updates available.

For those of you pledged to my Patreon or with your own Azure/OpenAI TTS services this update also coincides with an update to Observatory Herald which uses the new plugin update check and improved plugin messaging features to generally improve its user experience.

For plugin authors this version includes the long-awaited refactor of inter-plugin messaging, with thanks to @fredjk-gh.
  • Add "Always On Top"
  • Add plugin update check
  • Add new core method for plugins to easily display message boxes
  • Add GUIDs to plugin interface for identification
  • Handle new journal events and properties for Vanguards
  • Improvements to inter-plugin messaging
  • Improvements to plugin error handling
 
"Has been first footfalled" isn't in the journal, so that one's not possible, unfortunately.

I'm not particularly inclined to add a default criteria for "WasMapped" for a couple of reasons. First, it's essentially meaningless for any explorer deep in the black. Previous exploration drops off sharply once you get any appreciable distance from well traveled areas and it would trigger constantly. Second, it's very straightforward to set up as a custom criteria.
Headsup that "WasFootfalled" has evidently been quietly added to the journals with the Type-11 patch (heard from Jessidhia), thanks again for everything
 
So I’ve noticed in 1.3 it’s possible to pin the main window so it stays on top. Am I missing something or is this not possible to do with popped out panels?
 
So I’ve noticed in 1.3 it’s possible to pin the main window so it stays on top. Am I missing something or is this not possible to do with popped out panels?
Should work just fine.
1762021685902.png

Make sure you're using the native popout functionality (right click tab, popout plugin) rather than anything bespoke to a particular plugin though. Some plugins had their own popout functionality before it was built in to Observatory natively.
 
Should work just fine.
View attachment 442940
Make sure you're using the native popout functionality (right click tab, popout plugin) rather than anything bespoke to a particular plugin though. Some plugins had their own popout functionality before it was built in to Observatory natively.
AHA! I think that was the key piece of secret sauce - right click on the tab and click Popout, rather than the Popout button inside the plugin's window itself. Now I can see an Always On Top menu option. Cheers!
 
v1.4.0 - Plug It In

This update comes with some significant changes under the hood for plugin developers, most notably a new plugin bundling format inside .eop files (Elite Observatory Plugin) which allows developers to package .NET build outout as-is into plugin bundles.

These new plugins can also be updated in-place without needing to close Observatory first, though a restart is still necessary in order to load the new version.

Users should not notice any difference in normal usage, and existing plugins will continute to work as before.
  • Add WasFootfalled and WasLogged to Scan and ScanOrganic events respectively
  • Fix issue where ancillary files would incorrectly be included in retroactive pre-read as if current
  • Fix datatype issues with squadron contribution values
  • Complete rework of plugin loading to avoid unpacking .eop bundles and holding files open
  • Improved plugin update check to provide direct link to update and allow plugin self-update
  • Explorer "Eccentric Orbit" built-in check now indicates whether planet is landable
 
v1.4.0 doesn't start at all on my pc after installation (Win11, .net8 runtime installed).
v1.3 runs without problems and I went back to that version.
 
Last edited:
v1.4.0 doesn't start at all on my pc after installation (Win11, .net8 runtime installed).
v1.3 runs without problems and I went back to that version.

Yeah just checked, doesn't even try to start on my system either, haven't had a chance to test any further yet, maybe disabling some of the plugins might help, will test later.
 
Just uninstalled, deleted the old folders on the PC to get rid of any plugins, installed just the latest base version no plugins, works fine so it must be a plugins issue somewhere.
 
Ok, next step, re-downloaded all the old plugins I was using, they all installed and now it's working, so don't know what exactly caused the issue, but recommend if it doesn't work, uninstall, delete old folder and all plugins, re-install latest version, grab your plugins fresh and install and test them one by one, shutting down between each install to make sure it works properly.

Hang on, there's one I missed testing, statscanner, that one stops it working!

Yeah that's the one, deleted it from the plugins folder and it's working again now, all of MattG's are fine, it's the statscanner that didn't work for me.
 
Last edited:
v1.4.2 - Primarily Portable Tidying

This bugfix release focuses on some undesired behaviour in the portable version with regard to plugin loading and data storage. This should prevent plugin data folders from erroneously being displayed as invalid plugins.
In addition the bundled version of Explorer finally has the new codex entry criteria implemented. This setting previously did nothing.
  • Reorganise data folders for portable version.
  • Add automatic migration of existing portable data to new folder structure.
  • Disable processing of plugin subfolders as plugins for all non-debug builds.
  • Implement codex entry criteria in bundled Explorer plugin.
  • Fix issue where internal plugin messaging would lose the original message ID. @fredjk-gh
  • General tidying and improvements to plugin UI handling. @fredjk-gh
 
v1.4.3 - Data Migration Cleanup

Very little that users will notice in this release, primarily bugfixes around how plugin data folders are handled and migrated.
  • Revert to bare GUID for data folder naming to avoid issues with plugin name changes or overlaps.
  • Improved robustness and error handling of data migration.
  • Fix issue where data folders were not created for newly installed plugins. @fredjk-gh
  • Fix issue with decompressing .eop plugin manifests containing multibyte characters. @matt-g-dev
  • Implement more missing journal serializers. @fredjk-gh
 
Hang on, there's one I missed testing, statscanner, that one stops it working!

Yeah that's the one, deleted it from the plugins folder and it's working again now, all of MattG's are fine, it's the statscanner that didn't work for me.
Sorry for the trouble -- there was also an updated StatScanner posted that day that also fixed the issue with StatScanner. I should have also mentioned that.

That said, I've got a full round of plugin updates for everyone to try out. This is a beta release of all plugins as there has been a lot of changes since the last release and I'd love to get some feedback on them: https://github.com/fredjk-gh/ObservatoryPlugins/releases/tag/v1.4.0.26035-beta

These all require Observatory Core 1.4.3. Please read the release notes for more details. Enjoy!
 
Hi, very sorry if this has been answered already but I just starting using this tool and I'm having a minor issue with the exobiology window that provides distances from your most recent scan(s) where it is staying in place after finishing a sample instead of updating itself and going away, and the issue persists even if I close to menu. It's easily fixed by just closing Observatory and restarting it but I'm wondering if there's some setting that's causing it to happen that I could tweak or a work around someone is aware of. This tool is great this is just a minor thing.
 
Hi, very sorry if this has been answered already but I just starting using this tool and I'm having a minor issue with the exobiology window that provides distances from your most recent scan(s) where it is staying in place after finishing a sample instead of updating itself and going away, and the issue persists even if I close to menu. It's easily fixed by just closing Observatory and restarting it but I'm wondering if there's some setting that's causing it to happen that I could tweak or a work around someone is aware of. This tool is great this is just a minor thing.
Someone recently asked about this exact issue on Discord and it seemed to be an issue with persistent notifications and the Stellar Overlay plugin.

Just in case that wasn't you, a couple of workarounds until Matt releases an updated version are removing stellar overlay and using native notifications, or just disabling the "sticky" notification open in Botanist.

If you're not using Stellar Overlay but still seeing this behaviour then please let me know, as I'll need to dig in some more.
 
Back
Top Bottom