MattG's Observatory plugins

Funny thing. I just found them on an atmo body. The pressure is just 0.01 atmospheres, but still.

Yeah, you do get them on atmospheric bodies, have seen a few myself, as long as the basic requirements are met, and atmosphere was never used as a criteria for the old bio, they can appear on them. The basic requirements for the old bio are much less specific than the new bio, whether this is just an oversight or was meant to happen I don't know, but that's what happens sometimes.
 
Hi,

Can I ask what the orange dot is signifying?

1673441366822.png
 
I've updated CodexCompanion to work with latest BioInsights (which has also got a small update)

Any marks you previously had are gone - but for the most part you shouldn't need them as their functionality should be more-or-less covered by BioInsights. e.g
  • If you were using CC to add a mark to a species you'd not seen anywhere in the galaxy, check the "mark entries I've not seen in any region" box in BI settings
  • If you were using CC to add a mark to a species you'd not seen in a particular region, check the "mark entries I've not seen in current region" box in BI settings
  • If you were using CC to add marks to valuable species, just set a threshold in the "notify bodies with individual biological value over" box in BI settings. Note that this box works slightly differently in that it will only report when there is a biological that is all but certain not just when it's possible. I may add a setting to toggle this behaviour at a later date.
  • If you meticulously added marks to every variant that had not yet been discovered in the galactic codex of a particular region, well, you no longer have to because BI will already notify you of this and give you an orange diamond (for default symbol set, anyway) when a body may contain a galactic new entry.

Those should cover 95% of mark usage. If you want to be notified when a particular biological is possible then you can still add a Mark/Notification and it will function the same as the old Persistent Mark did - it will not be removed when you see the biological. You can also mark a biological as Seen in CC, which will stop BI reporting it unseen.

When you double click a variant in CC, it will show you the requirements as before but will also show you any region you've seen the variant in as well as any region you've added a notification for it.

One thing that is currently missing is the ability to export a CSV of Codex Entries - this will be moving to Codex Entries plugin soon, as it makes more sense there.

CodexCompanion now requires .Net6. If you used the installer version of Observatory Core (rather than the standalone), you'll already have this. Otherwise, you may need to grab it from here - you want the Windows Desktop x64 option.

BioInsights is also updated, to cater for a handful of tweaks necessary to work with CC.
 
Works a treat, thank you, I was hoping for an update. I'm grateful.

Also, I can never remember if you get notifications of unpredicted lifeforms automatically or not:
1673607486131.png
 
Works a treat, thank you, I was hoping for an update. I'm grateful.

Also, I can never remember if you get notifications of unpredicted lifeforms automatically or not:
View attachment 341564
I've actually disabled the reporting at the moment so appreciate any reports like this. Looks like it was just below the expected minimum gravity so I've tweaked that, it'll be fixed in next release.
 
Not a biggie, but I get these when running a "Read All" - I usually just ignore them as they cause no issue but it would be good if I did not need to :)

1673633896058.png


Contents of the error log file dated today are below (and sure to cause a flurry of Raxxla tinfoil hat alarm bells!)


[14/01/23 7:16:02 am]:
Error reading file Journal.190218184603.01.log: Requested value '++++' was not found. - { "timestamp":"2019-02-18T07:15:41Z", "event":"MissionAccepted", "Faction":"Raxxla Research", "Name":"Mission_Smuggle_Boom", "LocalisedName":"Smuggle 56 Units of Imperial Slaves", "Commodity":"$ImperialSlaves_Name;", "Commodity_Localised":"Imperial Slaves", "Count":56, "DestinationSystem":"Mizete", "DestinationStation":"Crowley Terminal", "Expiry":"2019-02-19T22:24:38Z", "Wing":false, "Influence":"++++", "Reputation":"+", "Reward":487032, "MissionID":462508037 }

[14/01/23 7:16:02 am]:
Error reading file Journal.190219183724.01.log: Requested value '++++' was not found. - { "timestamp":"2019-02-19T07:21:31Z", "event":"MissionAccepted", "Faction":"Raxxla Research", "Name":"Mission_Smuggle_Boom", "LocalisedName":"Smuggle 144 Units of Imperial Slaves", "Commodity":"$ImperialSlaves_Name;", "Commodity_Localised":"Imperial Slaves", "Count":144, "DestinationSystem":"Uhlanqui", "DestinationStation":"Zoline City", "Expiry":"2019-02-20T11:42:06Z", "Wing":false, "Influence":"++++", "Reputation":"+", "Reward":2295166, "MissionID":462727562 }

[14/01/23 7:16:03 am]:
Error in Observatory Botanist while handling ScanOrganic: Value cannot be null. (Parameter 'key') - { "timestamp":"2022-07-07T07:51:15Z", "event":"ScanOrganic", "ScanType":"Analyse", "SystemAddress":0, "Body":0 }
 
The first ones are Observatory errors, not MattG related errors. The second one is malformed Frontier data that can safely be ignored (and MattG can protect against it in a patch).
 
Another system I passed through more than a handful of years ago, probably on my first trip to Colonia when it was still just Jaques Crashed Station, I am guessing star type not detected for the missing ones;

1674046887476.png
 
BioInsights went silent for me after the latest Observatory Core update (to v0.2.23019.109). Not crashing but nothing appears in the window and no notifications are played. Does anyone else have this issue?
 
BioInsights went silent for me after the latest Observatory Core update (to v0.2.23019.109). Not crashing but nothing appears in the window and no notifications are played. Does anyone else have this issue?
I just bothered Matt with this for the past hour before realising that it was me being dumb.
The latest update reset everything, so the "Start Monitor when starting" setting was gone, might be the same on your side.
 
Back
Top Bottom