You need the latest release linked a few posts back or on the main page. Or here.
Note that themes in new release of Observatory won't work yet. It's on my to-do list, but it's non-trivial.
MattG's Observatory plugins
- Thread starter MattG
- Start date
Note that themes in new release of Observatory won't work yet. It's on my to-do list, but it's non-trivial.
I did download the latest one - that's what changed it to monochrome.
Have you got an "idiot's guide" to installing? I think I need to start again.
I downloaded this on Sunday
Uninstalled and reinstalled just now, it looks like this, is this right?
Looking hopeful...
Last edited:
In case others have similar issues:
It looks like you downloaded the new Observatory on Sunday, not BioInsights.This release of Observatory has many improvements, but one downside of it is the "basic" UI no longer supports the coloured iconography I was using. I have since rewritten the UI for BioInsights, but it requires you to also download the latest BioInsights - which you've now done. Don't forget a Read All to repopulate background details.
I've mentioned this before, but if you were using my AutoUpdater plugin it specifically won't update to the latest release of BioInsights. This is because it just blindly downloads the latest release without checking the version of Observatory being used, and if it downloaded BioInsights while you were on the old version of Observatory it would cause problems. Instead, new releases of my plugins are able to check for updates themselves - and will only download versions compatible with the version of Observatory you're using.
Thanks, it looks good now.
(System names removed to protect the unclaimed.)
Hi MattG, is there still a download link for the old version of BioInsights?
A Cmdr friend of mine likes the old Observatory version more, but unfortunately had installed the new BioInsights, which of course doesn't work properly with that version.
Edit: nvm I've fixed it now.... was having trouble with the Observatory herald voice overriding things...
Last edited:
Has there been any earlier work on the hinted Codex 'proximity to nebulae' requirement anywhere? In this forum or elsewhere? So far it seems that it is not a simple spherical volume, at least not as the Pueliae location is concerned.
At present I can note that Z coordinates for systems with Electricae Radialem 'near' to the Pueliae nebula seem likely to extend outside the current search limits of 120 ly 'radius', and that there is some minor slop for Y coordinates (within 105 ly). X coordinates seem to stay within the presumed 100 ly limit. This is from an almost completed exhaustive search of a 240x240x240 ly volume fairly close to the nebula.
Not by me, I keep putting it off.
I'm running out of reasons to not start tackling Bark Mounds though, and I'll be able to use that data to look closer at Electricae too. Just need to find the motivation to start!
Do all Electricae need Nebula, because there is a site in the bubble with electricae.
Codex says so for Electricae Radialem. For Electricae Pluma (which I have not encountered myself so far), Codex suggests 'planets orbiting bright white stars'.
Fandom Wiki has 'Parent star of type A, with a luminosity class of V or more, Neutron star or White dwarf. To be confirmed: type O, B, black hole.' but I see no date for that.
Canonn Bioforge only seems to have 'icy planet' as requirement (ignoring likely colour requirements), but seems to indicate that they have been observed with several other star types, including brown dwarfs. (I wonder if they may be conflating DSS reports and sample/comp. scans.)
It was Electricae Pluma orbiting the secondary star, a white dwarf, in the system HIP 44463, so it seems to fit that criteria.
Looking at the galaxy map, the Pueliae AA-A h0 nebula is right near a region border. Did you check if that messes things up perhaps? Electricae Radialem should be present in both regions though, but I wonder if perhaps some spawn calculation goes awry and the game decides not to spawn those in "problematic" systems.
As for the Codex nebula requirement: for the pre-Odyssey stuff, there has been plenty of work. Bark Mounds have been mentioned here before, especially as having been problematic. When it comes to Notable Stellar Phenomena that require nebulae, in the cases of large life (molluscs, pods and trees) it's the usual 100 ly from a nebula center, and for most Anomalies, it's 10 ly... except for the E02 and E03 Anomalies in Izanami, which go out to 100 ly instead. Even for large life, there are some that go beyond 100 ly, but those aren't listed as requiring nebulae in the Codex. (Their spawn zone was set manually though.) Of course, the Codex has numerous errors when it comes to the NSP requirements listed there.
For the Electricae Radialem: I don't know of any exhaustive effort. When Odyssey was new, I checked IIRC around 5-7 nebulae, the Electricae spawned within the usual 100 ly of those, so I just assumed that's universal and went on to do more interesting stuff. Looking at the data that has been gathered since (see the map here, that assumption was probably wrong. Which is somewhat unfortunate, because it'd be more convenient to just go with the same distance everywhere than to have to do two separate sets.
For the Electricae Radialem: I don't know of any exhaustive effort. When Odyssey was new, I checked IIRC around 5-7 nebulae, the Electricae spawned within the usual 100 ly of those, so I just assumed that's universal and went on to do more interesting stuff. Looking at the data that has been gathered since (see the map here, that assumption was probably wrong. Which is somewhat unfortunate, because it'd be more convenient to just go with the same distance everywhere than to have to do two separate sets.
The volume I'm inventorying right now is [ 17920, 280, 13750 ] --> { 18160, 520, 13990 } (where { } indicates 'up to but not including') . That is, I don't care about regions in deciding what systems I visit, only if the system has a StarPos that is within the search box or not. I don't see what kind of test would indicate that the presence of a region would mess anything up. (The only quick test I can make is for consistency: all my current CodexEntry logs for Electricae Radialem in this box have 'Hawking's Gap' as region.)
(Added: perhaps a 3D plot to see if there are odd gaps?)
I have not noted any problems with 100 ly until I stumbled on one specimen that BioInsight didn't predict. (See https://forums.frontier.co.uk/threads/mattgs-observatory-plugins.589466/post-10293369 . Your own recommendation was to do a proper survey. OK ... ) The prediction failure suggested either a bad estimate of nebula center or a bad volume radius or a bad volume model (non-spherical), or some combination. Don't know if I'll be able to say what, but at least there will be database entries for everything I've looked at ... right now the count seems to be 41 systems with one or more Electricae Radialem in my logs, but there will be additional checks to try to settle the Z extent.
Last edited:
I'm aboslutely loving ED Obs and cant find any reason not to run it all the time. But i would love to use different voices that the 3 listed (Microsoft David, Hazel, Zira). I have many more loaded on the machine within windows but would be even better if we could use AI voices such as ElevenLabs. Is this on the cards or already possible?
Not planning to expand the native voice notifications. Unsure why it doesn't detect all installed voices and not likely to spend much time looking into it.
That said, as Ski'Thor said, the Herald plugin should provide much higher quality voices.
Last edited:
As Vithigar said, there should be many more different voices to choose from.
That's how it looks for me. The scroll bar gives you an idea of how many more there are to choose from.