Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!
- Thread starter Vithigar
- Start date
Version 1.2.3 has been released for patrons.
A general release will follow soon, but this one is getting a more limited initial release mostly due to my own time constraints this past week and inability to give it as thorough a shakedown as I would've liked.
A general release will follow soon, but this one is getting a more limited initial release mostly due to my own time constraints this past week and inability to give it as thorough a shakedown as I would've liked.
Version 1.2.4 is now available!
Three, count them, three bugfix releases since 1.2.0!
Some small issues were identified with 1.2.3, so we're up to four!
Simple audio chimes are now available for notifications as well, for those who wanted some kind of audio alert, but didn't care to have them spoken.
This update also includes a refactor of the plugin settings window. It should now be somewhat more compact and behave better on differently sized displays.
Download Elite Observatory Core
Tool for reading/monitoring Elite Dangerous journals for interesting objects.
observatory.xjph.net
Some small issues were identified with 1.2.3, so we're up to four!
Simple audio chimes are now available for notifications as well, for those who wanted some kind of audio alert, but didn't care to have them spoken.
This update also includes a refactor of the plugin settings window. It should now be somewhat more compact and behave better on differently sized displays.
- Added "Chime" option for audio notifications
- Major refactor of plugin settings window
- Fix an issue where numeric plugin settings could cause an error if they specified a minimum value above 0 (fredjk)
- Added DirectoryInfo as a valid datatype for plugin settings
- Corrected behaviour for internally focusing a plugin while popped out (fredjk)
- Restore missing "Plugin Folder" button
- Corrected handling of application audio to not mess with windows mixer
- Update behaviour when installing plugin from double-click of .eop file to automatically restart Observatory
- Expanded framework notifier interface to include necessary information for persisted notifications
- (1.2.4) Fix an issue in Botanist where re-played journals without accompanying Status file data could cause errors
- (1.2.4) Relax "on screen" requirement when restoring plugin popout locations to be in line with those of the main window
Can't wait to give it a test flight when I get back home. Thank you so much for your work!
rootsrat
Volunteer Moderator
I have this issue which started happening after I upgraded to 1.2.4
Happens after I launch the application, and then as soon as I click on it (for example to move the window, or do whatever in the app), it just goes Not Responding forever. Anyone came across this by chance?
The error message:
EDIT
Nvm, removing Herald plugin fixed the issue
Happens after I launch the application, and then as soon as I click on it (for example to move the window, or do whatever in the app), it just goes Not Responding forever. Anyone came across this by chance?
The error message:
EDIT
Nvm, removing Herald plugin fixed the issue
Glad you got it sorted. It shouldn't have caused the app to freeze like that, however.I have this issue which started happening after I upgraded to 1.2.4
View attachment 412309
Happens after I launch the application, and then as soon as I click on it (for example to move the window, or do whatever in the app), it just goes Not Responding forever. Anyone came across this by chance?
The error message:
EDIT
Nvm, removing Herald plugin fixed the issue
rootsrat
Volunteer Moderator
Unfortunately it's happened again during a live stream. I loaded up all my data, then clicked on Boxel Stats tab, and my PC froze again. Had to do a hard reset.Glad you got it sorted. It shouldn't have caused the app to freeze like that, however.
Note I've been using pre 1.2.2 versions with no issues.
I'll post error log tomorrow.
Boxelstats is almost certainly going to be a source of problems. I expect you have a very large log full of errors from it.
BoxelStats should be working (more-or-less) fine. I'm running the old version alongside it's replacement and haven't had any issues with it (besides GUI not being initially populated where it gets automatically disabled on startup).
Very interested if there are logs showing otherwise - though hopefully the rewrite will be finished soon making it moot anyway.
rootsrat
Volunteer Moderator
Correct. I asked Matt in his thread and he's confirmed his mods should be working OK.
The problem (and please don't take it as entitlement, I am simply reporting an issue
) is that pre 1.2.2 it was working OK with the same journals, so the data didn't change, but the app (or the plugin) now has issues reading them for some reason. Or maybe not reading, as that process went OK, but processing the data.
What what I've seen, it's complaining about JSON values for committing crime entries from the journal.
I hope this can be fixed in the future, Observatory is a must have for me for exploration
o7
Ah, some missing crime types were recently brought to my attention elsewhere and should be sorted out very soon.Correct. I asked Matt in his thread and he's confirmed his mods should be working OK.
The problem (and please don't take it as entitlement, I am simply reporting an issue
Or maybe not reading, as that process went OK, but processing the data.
What what I've seen, it's complaining about JSON values for committing crime entries from the journal.
I hope this can be fixed in the future, Observatory is a must have for me for exploration
o7
That said the error shouldn't cause a complete freeze like this. Something else is likely going on. Unfortunately killing it while frozen also skips writing out crash log for that particular problem. You say pre-1.2.2 works fine, so 1.2.1 doesn't freeze like this? Very little changed between those versions.
rootsrat
Volunteer Moderator
Yeah, the complete lock up of my PC was very weird and I was very surprised to see it.
I'll try to find some time this weekend to do some more troubleshooting to help resolve this.
Is 1.2.2 when the UI change happened? I generally meant the "old" Core, before the UI change, as that's when I used it with no issues last time. Apologies if I confused the vsrsions
Ah, 1.2.0 was the UI change.
Would you mind zipping up your entire plugins folder and sending it to me to test? I'd like to try an identical setup to see if I can replicate.
Plugins which display everything after a read-all do tend to be sluggish while they have the entirety of their content loaded.
That said, my approach to dealing with BoxelStats being disabled by default is to also turn off auto-start of the monitor. That way I can enable the plugin(s) and then hit start monitor and get the proper preloading/initialization.
That said, my approach to dealing with BoxelStats being disabled by default is to also turn off auto-start of the monitor. That way I can enable the plugin(s) and then hit start monitor and get the proper preloading/initialization.
Hello,
I wanted to report that since the latest version, I’ve been experiencing several bugs with the plugins. Many of them no longer work as expected, and I’m not the only one facing these issues—my friends have also reported similar problems.
It seems that the plugins are either not loading correctly or failing to function altogether. This has made it difficult to use some of the features we rely on.
Could you please look into these issues or provide guidance on how to resolve them?
I wanted to report that since the latest version, I’ve been experiencing several bugs with the plugins. Many of them no longer work as expected, and I’m not the only one facing these issues—my friends have also reported similar problems.
It seems that the plugins are either not loading correctly or failing to function altogether. This has made it difficult to use some of the features we rely on.
Could you please look into these issues or provide guidance on how to resolve them?
If you’re talking about my plugins, I’d suggest reading this post. Otherwise, you’re going to need to give more details
As Matt said, definitely need more info here.
What plugins? What version of Observatory were you using previously? What issues exactly are you having? Does the plugin list show these plugins as outdated or as just having errors?
For the general case of outdated plugins: Observatory 1.2 had some changes which broke compatibility with plugins and any from prior to that will need to be updated. Most are good to go now but you will need to get the updated versions.
Matt's are here: https://edjp.colacube.net/observatory
Coddiwompler/fjk's are here: https://github.com/fredjk-gh/ObservatoryPlugins/wiki
Duvel's GeoPredictor is here: https://github.com/mcmuttons/GeoPredictor/releases
If the problem is something else then we can't help without those extra details.
Hey all - been quite a while since I used this so things needed updating.
I'm still getting Update Required on my old "Galactic Exploration Catalog" and "Observatory Telegram Notifier" plugins.
I found "Telegram" here (https://edjp.colacube.net/observatory) but downloading and running the eop hasn't fixed the update required issue.
I can't seem to find the Galactic Exploration Catalog plugin.
Any thoughts/help?
I'm still getting Update Required on my old "Galactic Exploration Catalog" and "Observatory Telegram Notifier" plugins.
I found "Telegram" here (https://edjp.colacube.net/observatory) but downloading and running the eop hasn't fixed the update required issue.
I can't seem to find the Galactic Exploration Catalog plugin.
Any thoughts/help?
The "Update Required" is Observatory saying the plugins are old and may have problems - rather than it telling you they have updates available. It will mean they also get disabled each time you start Observatory. It's because they were written before certain breaking changes happened in Observatory which can stop some plugins working.
I didn't get round to updating Telegram yet, wasn't sure anyone even still used it. I'll hopefully get to it soon, but it should continue to work OK in the meantime (don't forget to re-enable it each time though).
The GEC one won't work at the moment. I am planning to incorporate this into a different plugin (that'll also replace Signal Monitor and Codex Entries plugins), but I've not finished it yet.
OK cool, thanks! To be honest I don’t even remember what Telegram is or why I have it.