Recently I've also noticed bodies "g" being read as "ge" not "gram", which is cool. 
No idea when it was fixed but I thank for this fix anyway.
No idea when it was fixed but I thank for this fix anyway.
Last edited:
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
Specifics of speech generation like that are mostly in the hands of Microsoft. Direct your thanks to whoever is working on Azure Cognitive Services text to speech service.Recently I've noticed bodies "g" being read as "ge" not "gram", which is cool.
Use an up to date version of that plugin which is compatible with the version of Observatory you are using.
Export Options
github.com
This release adds a feature that several people have asked for, courtesy of @fredjk-gh. The export format can now be changed between the defaulted fixed width output and a tab separated file for ease of use with automated processing tools and spreadsheet programs. Find the option to change this in the new "Export Options" pane of the core tab.
Of interest to plugin developers, there is a new AddGridItems method which can add multiple rows to a plugin UI grid in only a single call, which should improve performance for large changes to the grid.
In addition there are a number of bug fixes for edge case error conditions, and some minor tweaks for behaviour of linux builds courtesy of @cerus, who has also provided an unofficial linux build of Observatory, which you can find here: https://github.com/cerus/observatorycore-linux
Release Export Options · Xjph/ObservatoryCore
This release adds a feature that several people have asked for, courtesy of @fredjk-gh. The export format can now be changed between the defaulted fixed width output and a tab separated file for ea...
github.com
This release adds a feature that several people have asked for, courtesy of @fredjk-gh. The export format can now be changed between the defaulted fixed width output and a tab separated file for ease of use with automated processing tools and spreadsheet programs. Find the option to change this in the new "Export Options" pane of the core tab.
Of interest to plugin developers, there is a new AddGridItems method which can add multiple rows to a plugin UI grid in only a single call, which should improve performance for large changes to the grid.
In addition there are a number of bug fixes for edge case error conditions, and some minor tweaks for behaviour of linux builds courtesy of @cerus, who has also provided an unofficial linux build of Observatory, which you can find here: https://github.com/cerus/observatorycore-linux
Shouldn't the base value shown above have one more zero in it?
Love the tool!
Hello!
Has anyone else noticed that bio scan message popups now - only sometimes - remain on-screen until that bio has been fully scanned? It seems to be like this since the last release.
It's more than likely something I'm doing wrong...
EDIT - no, actually, it's happening all the time now. I have the duration set to 3kms.
Has anyone else noticed that bio scan message popups now - only sometimes - remain on-screen until that bio has been fully scanned? It seems to be like this since the last release.
It's more than likely something I'm doing wrong...
EDIT - no, actually, it's happening all the time now. I have the duration set to 3kms.
Last edited:
No, that appears to be the correct value, only Stratum Tectonicas and Cucumsis have a values over 10m, all the rest of the Stratum are mostly well under the 10m mark in base value.
Some big-ish news today, with regard to the UI overhaul that I've been talking about doing for many months (a year?!) now.
The short version: I'm kicking AvaloniaUI to the curb and completely re-writing the UI using WinForms.
The long version: I originally chose AvaloniaUI as my UI framework because it was a more modern framework which was compatible with both Windows and Linux, and when originally sitting down to write Observatory Core I had planned to also support a Linux release alongside the Windows one. Well no Linux build I ever did was in what I would consider a "releasable" state, and on top of that my use of AvaloniaUI has not really been a great time.
A considerable source of delay in Observatory updates happening since Core released is that I just don't like working with Avalonia, and procrastinated whenever I needed to do so. But I just sucked it up and slowly trickled out updates anyway.
Last week while thinking about Observatory in the shower I had a moment of realisation about just how much this was actually slowing things down and made the decision to just get rid of it. Converting the existing codebase from AvaloniaUI to WinForms is a fair bit of work, but in the week since I made that call I'd estimate it's about 75% done.
What does this mean for users?
For most of you, very little. You might notice some small cosmetic differences, but by and large ObservatoryCore using WinForms will be the same UI with the same things in the same places. I do actually expect that the application will be smaller and start more quickly.
For Linux users who were perhaps holding onto the hope of an official Linux release, this is unfortunately the final nail in the coffin for that particular goal. Sorry I never made it work.
For developers who were working on plugins, everything "under the hood" is essentially unchanged, and I expect the current ObservatoryFramework library to remain compatible across this particular migration. Also, the long-teased feature of a UI type other than "basic" should happen soon. If you've been wanting to make plugins with more involved UIs, stay tuned.
One small caveat for plugins is that with this update I will finally be checking code signing, and unsigned plugins will popup up a one-time, dismissable warning. Loading arbitrary dlls is a potential attack vector for running arbitrary malicious code, and while I'm not completely locking the door on that possibility I'd at least prefer Observatory not remain completely silent while it happens. If you want to get the plugins you're creating signed, ask me about it on Discord.
What does this mean going forward?
More frequent updates and the addressing of many long-standing UI issues very soon (lack of column ordering and sorting chiefest among them). It does unfortunately make theming more difficult, but I swear I'll get a dark mode/light mode switch in there at some point.
Why Winforms? Why not something "modern" like WinUI or even WPF?
Using AvaloniaUI has taught me to hate working with XAML and I will now go to great lengths to avoid it. I do not want a level of abstraction between my UI and my code.
When will it release?
I'm hoping to have a test version available to users on the Observatory Discord within the next few days, and a proper release soon after that depending on how that goes.
The short version: I'm kicking AvaloniaUI to the curb and completely re-writing the UI using WinForms.
The long version: I originally chose AvaloniaUI as my UI framework because it was a more modern framework which was compatible with both Windows and Linux, and when originally sitting down to write Observatory Core I had planned to also support a Linux release alongside the Windows one. Well no Linux build I ever did was in what I would consider a "releasable" state, and on top of that my use of AvaloniaUI has not really been a great time.
A considerable source of delay in Observatory updates happening since Core released is that I just don't like working with Avalonia, and procrastinated whenever I needed to do so. But I just sucked it up and slowly trickled out updates anyway.
Last week while thinking about Observatory in the shower I had a moment of realisation about just how much this was actually slowing things down and made the decision to just get rid of it. Converting the existing codebase from AvaloniaUI to WinForms is a fair bit of work, but in the week since I made that call I'd estimate it's about 75% done.
What does this mean for users?
For most of you, very little. You might notice some small cosmetic differences, but by and large ObservatoryCore using WinForms will be the same UI with the same things in the same places. I do actually expect that the application will be smaller and start more quickly.
For Linux users who were perhaps holding onto the hope of an official Linux release, this is unfortunately the final nail in the coffin for that particular goal. Sorry I never made it work.
For developers who were working on plugins, everything "under the hood" is essentially unchanged, and I expect the current ObservatoryFramework library to remain compatible across this particular migration. Also, the long-teased feature of a UI type other than "basic" should happen soon. If you've been wanting to make plugins with more involved UIs, stay tuned.
One small caveat for plugins is that with this update I will finally be checking code signing, and unsigned plugins will popup up a one-time, dismissable warning. Loading arbitrary dlls is a potential attack vector for running arbitrary malicious code, and while I'm not completely locking the door on that possibility I'd at least prefer Observatory not remain completely silent while it happens. If you want to get the plugins you're creating signed, ask me about it on Discord.
What does this mean going forward?
More frequent updates and the addressing of many long-standing UI issues very soon (lack of column ordering and sorting chiefest among them). It does unfortunately make theming more difficult, but I swear I'll get a dark mode/light mode switch in there at some point.
Why Winforms? Why not something "modern" like WinUI or even WPF?
Using AvaloniaUI has taught me to hate working with XAML and I will now go to great lengths to avoid it. I do not want a level of abstraction between my UI and my code.
When will it release?
I'm hoping to have a test version available to users on the Observatory Discord within the next few days, and a proper release soon after that depending on how that goes.
Found a bug today (pretty rare, I guess): when a shepherd moon orbits a barycentre with another moon, the message for built-in "Shepherd moon" criteria says things about barycentres and hyphens instead of standard body names.
Screenshot please, and if possible the journal containing those events.Found a bug today (pretty rare, I guess): when a shepherd moon orbits a barycentre with another moon, the message for built-in "Shepherd moon" criteria says things about barycentres and hyphens instead of standard body names.
There were many tries to get barycenters right, so if it's still wrong Vithigar surely needs proof and data.
Known broken for a long time. Actually one of the first things I fixed in the UI rewrite mentioned a few posts above.
Count me in to looking forward to it, then
Cheers!
Looks like a possible candidate for life, given magnetic fields may be present:
www.independent.co.uk
Looking at the data, the planet was discovered in 2017, but Elite Dangerous doesn't have it, only an ice world that's too light in mass
exoplanets.nasa.gov
‘Coherent’ radio signal detected from alien planet
New findings suggest planet could have magnetic fields, and therefore is more likely to be habitable
www.independent.co.uk
Exoplanet-catalog – Exoplanet Exploration: Planets Beyond our Solar System
exoplanets.nasa.gov
Hi ! thank you very much for this great software, very usefull. I begin to play with lua criteria file and I am looking for a scan criteria about first footfall. Is there any one ? I use Scan.WasMapped for this purpose and I don't find any lua criteria for the footfall.
Heads up, there is currently an issue in the voice list that the Herald plugin retrieves from Microsoft Cognitive Services which has incorrectly doubled up a voice name (Ryan is named Jenny now). Herald expects the names to be unique and this causes an error which stops Herald from loading.
I've submitted a support request to MS to bring their attention to it. If they don't respond reasonably quickly I'll have to release an update for the plugin to work around this.
I've submitted a support request to MS to bring their attention to it. If they don't respond reasonably quickly I'll have to release an update for the plugin to work around this.