MattG's Observatory plugins

[lsitongia]

I installed Observatory Core and that works. After I drag and drop the Insight dll into the Observatory plugin directory, Observatory no longer works. The blue busy ring spins for a bit then stop. No window opens. After I drag the dll out of the plugin directory, Observatory works again. Where do I look for a log file?

Thanks for your work and time!

Edit: never mind! I colleague told me to drop the deps into the plugin/deps, too. That got it going! Thanks a bunch! Great work. I appreciate your time and labor.

 

[Codger]

Ran into a small glitch in Bioinsights. I found a planet with 3 biologicals, but only 1 showed up in the Bioinsights window (a bacteria). I did get the correct 'distance traveled' popup though, even for the ones that weren't in the window.

The missing items are Fumerola Nitris - White, and Fonticula Campestris - Amethyst. The planet in question is PLIO EURL BE-M B5 1-0 7C.

This is the only planet I scanned today. Note that the planet name is also wrong (and truncated) in the Bioinsights window. Or maybe it's displaying a different planet, and not the one I scanned.

Thanks again

 

[MattG]

Ran into a small glitch in Bioinsights. I found a planet with 3 biologicals, but only 1 showed up in the Bioinsights window (a bacteria). I did get the correct 'distance traveled' popup though, even for the ones that weren't in the window.

The missing items are Fumerola Nitris - White, and Fonticula Campestris - Amethyst. The planet in question is PLIO EURL BE-M B5 1-0 7C.

This is the only planet I scanned today. Note that the planet name is also wrong (and truncated) in the Bioinsights window. Or maybe it's displaying a different planet, and not the one I scanned.

Thanks again

View attachment 298899

I can't see anything obviosuly wrong in the criteria compared to the body details on EDSM.

Have you possibly visited this system before? Can you PM me the journal in question?

 

[Wissam24]

Ran into a small glitch in Bioinsights. I found a planet with 3 biologicals, but only 1 showed up in the Bioinsights window (a bacteria). I did get the correct 'distance traveled' popup though, even for the ones that weren't in the window.

The missing items are Fumerola Nitris - White, and Fonticula Campestris - Amethyst. The planet in question is PLIO EURL BE-M B5 1-0 7C.

This is the only planet I scanned today. Note that the planet name is also wrong (and truncated) in the Bioinsights window. Or maybe it's displaying a different planet, and not the one I scanned.

Thanks again

Out of interest, the Fumerola, did they appear in the DSS surface maps when you scanned the planet, and did the DSS also show the fumeroles geological signal? I ask just because to date I've never found bio and geo on the same planet, but based off your screenshot may pay more attention to planets that only show min value bacteria.

 

[MattG]

Out of interest, the Fumerola, did they appear in the DSS surface maps when you scanned the planet, and did the DSS also show the fumeroles geological signal? I ask just because to date I've never found bio and geo on the same planet, but based off your screenshot may pay more attention to planets that only show min value bacteria.

FWIW, I think the posted example was a glitch and not normal behaviour. Sure, BI isn't perfect - but I've checked the bodies on EDSM and they absolutely should have flagged the 2 missing species. For whatever reason, BI was unaware of the main star in the system - and that is a requirement of the 2 missing Biologicals. There are a few scenarios where this could have happened, but the Journal entries in question would've provided more detail.

WRT your question, yes, Fumerola show in the DSS as well as any volcanism. They're not too common though.

Edit: BioInsights will show you the number of biologicals expected, and you can see how many it actually predicts - if the number of unique Genus predicted isn't at least the number expected, it certainly worth checking the body a bit more (though remember BI will not predict Horizons biologicals).

 

[Wissam24]

Cheers.

 

[Codger]

the Journal entries in question would've provided more detail.

Sorry I got distracted by life. Here's the journal attached to this post.

And yes, the Fumerola did appear in the DSS scan.

Note that the system was discovered already when I arrived, so I didn't FSS everything, I just popped over to the planet that had biologicals and geologicals on it.

Thanks !

 

[Wissam24]

This planet was listed as having Aleoida, when in fact it didn't but it DID have frutexa (metallicum, grey) which isn't listed on the plugin (until after I scanned it). It did have all the others on the list. Would you like any more info about the system or planet?

 

[MattG]

View attachment 302284

This planet was listed as having Aleoida, when in fact it didn't but it DID have frutexa (metallicum, grey) which isn't listed on the plugin (until after I scanned it). It did have all the others on the list. Would you like any more info about the system or planet?

Can you confirm the BI version? I did a soft (so, unannounced) release a couple of weeks back that might fix this. If you use latest, either the Scan event would be useful - unless you already upload to EDSM and I can check it there.

 

[Wissam24]

BI is 0.22.95.1627. How do I get that for you?

 

[MattG]

BI is 0.22.95.1627. How do I get that for you?

You’d need to check the Journal in question in notepad or similar and find the Scan event for the body. Don’t worry for now, hopefully BI submitted a report to me anyway (can’t check at moment).

 

[Wissam24]

No worries, just let me know if you need it!

 

[MattG]

Are you aware that BI seems to stop working at all if you don't update? It would be nice if the earlier version would still work for a while, at least for the BIO signals it still knows. The distance to the next version is very convenient, you know? Or does this function come from the Botanist Plugin?

Distance notification is from BioInsights. Older versions should keep working, nothing in the newer should change that. That said, if you updated Observatory then there are instances where older BioInsights would appear to stop working. Other than that I can't think of a good reason it would just stop. (But always grab latest anyway because it'll be more accurate (usually)).

Lots more features planned too!

 

[GraphicEqualizer]

I have noticed herald sometimes now stops fully telling me about some bodies... does not seem to be a common reproducible type... e.g. sometimes it will just say "body 3c" but then not finish it's thought. When I look at the Explorer tab it will indicate that was an oblate gas giant or whatever - but other times it will also say that fully. Still trying to figure out if there is a pattern. I tested the old voice announce mode and confirmed that one still reads it out in full.

 

[MattG]

I have noticed herald sometimes now stops fully telling me about some bodies... does not seem to be a common reproducible type... e.g. sometimes it will just say "body 3c" but then not finish it's thought. When I look at the Explorer tab it will indicate that was an oblate gas giant or whatever - but other times it will also say that fully. Still trying to figure out if there is a pattern. I tested the old voice announce mode and confirmed that one still reads it out in full.

Probably one for the Observatory thread, Herald isn’t one of mine - but a couple of things, first check your Documents folder for an Observatory error report. Also, if you’re using custom criteria make sure you don’t have any & symbols in the output. I think there is a small bug at moment that can cause issues with ampersands - try a plus or something instead.

 

[MattG]

I've added a new plugin - Colliders. Full disclosure: this plugin sends data about potential colliders to me. I plan to eventually have some sort of calendar or something to direct people to the nearest event but for now it's just collecting data. The data sent is the Scan events of the 2 colliding bodies (so no more than you send to EDSM). For now, there's no way to turn it off (the point of the plugin is to collect this data...).

What are colliders? Well, this thread is a good starting point. The vast majority of colliding bodies only do so once every few decades, or centuries, or even tens of milleniums. Very occassionally, they're more frequent. This plugin will alert you of potential collisions, and if there is enough Scan data it will check if there is a collision predicted in the next 20 years. It also gives you the minimum period between collisions.

You can download it here

I also hope to have a new version of BioInsights and Codex Companion out this week, with many improvements.

 

[varonica]

Got, tested it against my historical data, got 3 matches that need to be rescanned if anyone is in the area!

 

[Eahlstan]

https://www.edsm.net/en/system/id/41294461/name/Hypiae+Phyloi+BL-V+d3-49
https://www.edsm.net/en/system/id/51754689/name/Gru+Hypue+AA-A+b58-5
https://www.edsm.net/en/system/id/21086705/name/Phroi+Blou+RY-R+e4-265
https://www.edsm.net/en/system/id/56887543/name/Phroi+Blou+AA-A+f157

If someone is near.

 

[MattG]

OK, new BioInsights and Codex Companion available here.

There are a number of behind the scenes changes. First and foremost, the DB location has moved. Previously, it was in %localappdata%\ObservatoryCore, it will now be in %appdata%\ObservatoryCore\ObservatoryBioInsights. This is partly because there are now more files in the background, but also to keep it more in line with where plugin data should be stored in Core. When you first try to use new BI or CC, they will try and migrate any existing data to the new location and rename the old files. The log file will also be in the new location, should you need to access it. If you really care about the data, you should probably back it up - but the majority can be easily recreated in the event something goes wrong.

BioInsights should now look more like this:

Any body meeting the minimum value requirement (or having Stratum Tectonicas if you have that option enabled) will show the moneybag in the Mark column. Marked species will show with a blue diamond both in the Mark column and by the specific variant so you can see at a glance which is the marked one(s). There is a new Type column that will show a pickaxe or a star - this signifies whether the variant colour is determined by Surface Material or Star. The possible variants will show the reason for the variant - either the Star type or the surface material. These changes have allowed the output to be more streamlined so it doesn't take quite so much screen space. If you really hate the emojis you can disable them in Settings and have text output instead


In Codex Companion, normal marks are also shown with a blue diamond. There is a new type of mark called a Persistent Mark that is shown with a blue square (note that if you want to change a mark to a persistent one in the interface, you need to Clear it first then re-mark it persistently). You no longer need to push Refresh (though the button is still there if you need to force a refresh for any reason), nor Unmark. If you see scan a new Bio in Odyssey and BioInsights is running, it will tell Companion automatically so it can be marked as Seen. Additionally, if the species was marked it will automatically remove the mark - unless it's a Persistent Mark in which case it will persist. Bulk Actions have also been vastly improved - the new button for them will bring up a dialogue so you can quickly add or remove marks from the current or all regions.

There have also been a number of improvements to the Codex requirements for a handful of species.

Let me know if there's any problems.

 

[Straha Yeagar]

OK, new BioInsights and Codex Companion available here.

There are a number of behind the scenes changes. First and foremost, the DB location has moved. Previously, it was in %localappdata%\ObservatoryCore, it will now be in %appdata%\ObservatoryCore\ObservatoryBioInsights. This is partly because there are now more files in the background, but also to keep it more in line with where plugin data should be stored in Core. When you first try to use new BI or CC, they will try and migrate any existing data to the new location and rename the old files. The log file will also be in the new location, should you need to access it. If you really care about the data, you should probably back it up - but the majority can be easily recreated in the event something goes wrong.

BioInsights should now look more like this:

Any body meeting the minimum value requirement (or having Stratum Tectonicas if you have that option enabled) will show the moneybag in the Mark column. Marked species will show with a blue diamond both in the Mark column and by the specific variant so you can see at a glance which is the marked one(s). There is a new Type column that will show a pickaxe or a star - this signifies whether the variant colour is determined by Surface Material or Star. The possible variants will show the reason for the variant - either the Star type or the surface material. These changes have allowed the output to be more streamlined so it doesn't take quite so much screen space. If you really hate the emojis you can disable them in Settings and have text output instead


In Codex Companion, normal marks are also shown with a blue diamond. There is a new type of mark called a Persistent Mark that is shown with a blue square (note that if you want to change a mark to a persistent one in the interface, you need to Clear it first then re-mark it persistently). You no longer need to push Refresh (though the button is still there if you need to force a refresh for any reason), nor Unmark. If you see scan a new Bio in Odyssey and BioInsights is running, it will tell Companion automatically so it can be marked as Seen. Additionally, if the species was marked it will automatically remove the mark - unless it's a Persistent Mark in which case it will persist. Bulk Actions have also been vastly improved - the new button for them will bring up a dialogue so you can quickly add or remove marks from the current or all regions.

There have also been a number of improvements to the Codex requirements for a handful of species.

Let me know if there's any problems.

Quick note on this...I had to update my ObservatoryCore to the latest version v0.2.22094.2356 in order for it to launch. Previous versions of Core would not launch with the new BioInsights.