MattG's Observatory plugins

To me it looks like SM only shows one of each kind. So most likely it doesn't create a list but overwrites anything found with the latest find (if read all goes from new to old) or just takes the first one and fails on the next ones (if read one goes from old to new).

It never used to on a read all, there was a huge list to scroll through, but yes these may be the earliest events of each type I have recorded so its behaviour has changed fairly recently if that's the case.
 
I've updated SignalMonitor.

When doing a Read All, it would only record the first instance of a NSP / beacon / post and ignore subsequent ones until the Read All completed. Subsequent FSD jumps would've continued to work as expected. I've now corrected this to only record the first instance of an object per system when doing Read All.

This shouldn't have any effect on that the OP was describing though.
 
SM is affected by the "show signals in the wrong system" behaviour caused by the fact that signals are written to the journal before location events (at startup) and before jumps are completed.
I got signals being displayed way out in the black because commander 1 logged out there and commander 2 got signals written when logging in.
 
I've updated SignalMonitor.

When doing a Read All, it would only record the first instance of a NSP / beacon / post and ignore subsequent ones until the Read All completed. Subsequent FSD jumps would've continued to work as expected. I've now corrected this to only record the first instance of an object per system when doing Read All.

This shouldn't have any effect on that the OP was describing though.

Working as previously experienced now, read all now shows the output I expect! Strange issue for the other poster though, I have previously not experienced it, I am sure the last NSP's I came across showed up in SM as expected.
 
I've not had other reports of this. I've not seen an NSP in some time but a Read All against some historic journals is showing some NSPs present in the plugin. Do you have the journal event showing the NSPs (event type FSSSignalDiscovered) ?
Hello Matt,
installed your new version (version 283.1503) , after "ReadAll" still the expected events from the last days (->September) don't show up.

Here is what is in the journal, first match only (does it look like a localization issue?)
Code:
$ grep FSSSignalDiscovered Journal.2022-09-* | grep Bemerk
Journal.2022-09-18T195938.01.log:{ "timestamp":"2022-09-18T18:38:21Z", "event":"FSSSignalDiscovered", "SystemAddress":33787140411779, "SignalName":"$Fixed_Event_Life_Ring;", "SignalName_Localised":"Bemerkenswerte Sternenphänomene" }

The last displayed NSP timestamp from "ReadAll" was from August:
Code:
Journal.2022-08-27T201750.01.log:{ "timestamp":"2022-08-27T18:26:17Z", "event":"FSSSignalDiscovered", "SystemAddress":3238296097059, "SignalName":"$Fixed_Event_Life_Cloud;", "SignalName_Localised":"Bemerkenswerte Sternenphänomene" }

Does Cloud vs Ring make a difference?
 
Now here's an interesting issue;

1665889156669.png


As you can see, 11 signals on body 1b, only 10 species listed, at first I thought obviously a horizons type bio is the 11th because they don't list in bioinsights, but no, the DSS only lists the above 10 species as well, so it must be a 2nd variant of the one species is the 11th signal, so Concha, Clypeus or Stratum has 2 variants, I don't see how that can be predicted though!
 
If I knew where that was, will check. This one?

Biological: 11, Human: 1, @ Col 285 Sector ZQ-M d7-41 1 b; Aleoida, Bacterium, Cactoida, Clypeus, Concha, Fungoida, Osseus, Stratum, Tubus, Frutexa, Tussock

Now that does have 11! Tubus is missing from bio insights!
If you let me know the species and variant of Tubus, I’ll tweak the criteria for next update 👍
 
Tubus Compagibus Grey

Looking at it, I have temperature range as >= 160 and < 195. This body has a surface temperature of 195 on EDSM (though journals are more accurate, they don't round. I'll tweak it for next release - thanks for the data.

Can't you do a "unpredicted XYZ in signals event" thing?

So BI does report on unpredicted (if the option is enabled) - but the majority of what it collects at the moment seem to be where someone re-visits somewhere they've been and then BI is unaware of the stars in the system (because no new scan events) so everything that relies on star type for colour is unpredicted. Makes using the data less useful - easier to just ask for pertinent reports.

Unpredicted reporting behaviour is on my list of things to improve in next release - which has turned into a fair chunk of a rewrite so far, so it may be a while off yet.
 
Hello @MattG,

i'm working on a little tool for my self and our small german community,
where i predict the Bio on a Planet and check against a DB if this Biological Type is scaned in this Sector.
I wanted to ask you, if it's not too intrusive. And I certainly don't want to copy your work. I would just appreciate some helpful info.

What criteria do you use for your prediction algorythm?
I would think Athmosphere, temperature, Gravity.
Do you use pressure and other criteria?

Kind regards
MajorK
 
Hello @MattG,

i'm working on a little tool for my self and our small german community,
where i predict the Bio on a Planet and check against a DB if this Biological Type is scaned in this Sector.
I wanted to ask you, if it's not too intrusive. And I certainly don't want to copy your work. I would just appreciate some helpful info.

What criteria do you use for your prediction algorythm?
I would think Athmosphere, temperature, Gravity.
Do you use pressure and other criteria?

Kind regards
MajorK
If you grab Codex Companion (it's a stand-alone app), you can double click a variant and it'll show you exactly what criteria I'm using (though it does get refined in each release, as my understanding improves).
 
If you grab Codex Companion (it's a stand-alone app), you can double click a variant and it'll show you exactly what criteria I'm using (though it does get refined in each release, as my understanding improves).
Thanks, i will take a look.
 
If you grab Codex Companion (it's a stand-alone app), you can double click a variant and it'll show you exactly what criteria I'm using (though it does get refined in each release, as my understanding improves).
Sorry, but i didn't mean the Color Variant Criteria, but the criteria for predicting which biosignals can occur on the planet, just as the Osseus Discuss must have a water athmosphere.
1666288432482.png
 
In BioInsights Codex Companion the headings in the tables for each genus tab appear in either blue or orange. What is the significance of the different coloured heading?

It'll be something obvious that i just haven't twigged.
 
Back
Top Bottom