MattG's Observatory plugins

Thandco · Dec 14, 2022

In the log file it keeps repeting these errors and the Log starts to get Very BIg
13-Dec-2022 19:29:23.405895 Object reference not set to an instance of an object.
13-Dec-2022 19:29:23.405897 at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
at Observatory.BioInsights.BISystem.AddOrUpdate(Scan scan)
at Observatory.BioInsights.BioInsights.JournalEvent[TJournal](TJournal journal)
13-Dec-2022 19:29:23.407407 Error in [JournalEvent:scan]
13-Dec-2022 19:29:23.407414 { "timestamp":"2022-09-18T18:40:33Z", "event":"Scan", "ScanType":"Detailed", "BodyName":"Hyades Sector DR-V c2-3 3", "BodyID":3, "Parents":[ {"Star":0} ], "StarSystem":"Hyades Sector DR-V c2-3", "SystemAddress":908352033458, "DistanceFromArrivalLS":770.718283, "TidalLock":false, "TerraformState":"", "PlanetClass":"Icy body", "Atmosphere":"thin argon atmosphere", "AtmosphereType":"Argon", "AtmosphereComposition":[ { "Name":"Argon", "Percent":100.000000 } ], "Volcanism":"", "MassEM":0.051585, "Radius":3066834.500000, "SurfaceGravity":2.185991, "SurfaceTemperature":91.216431, "SurfacePressure":309.506683, "Landable":true, "Materials":[ { "Name":"sulphur", "Percent":22.223402 }, { "Name":"carbon", "Percent":18.687582 }, { "Name":"iron", "Percent":15.412699 }, { "Name":"phosphorus", "Percent":11.964109 }, { "Name":"nickel", "Percent":11.657519 }, { "Name":"chromium", "Percent":6.931602 }, { "Name":"manganese", "Percent":6.365287 }, { "Name":"vanadium", "Percent":3.784823 }, { "Name":"niobium", "Percent":1.053376 }, { "Name":"tin", "Percent":0.999014 }, { "Name":"yttrium", "Percent":0.920582 } ], "Composition":{ "Ice":0.683352, "Rock":0.212777, "Metal":0.103871 }, "SemiMajorAxis":231058490276.336670, "Eccentricity":0.001823, "OrbitalInclination":-0.823433, "Periapsis":335.314914, "OrbitalPeriod":84672901.630402, "AscendingNode":-75.707323, "MeanAnomaly":89.492717, "RotationPeriod":141119.730365, "AxialTilt":-0.371548, "WasDiscovered":true, "WasMapped":true }
13-Dec-2022 19:29:23.407416 Object reference not set to an instance of an object.

Thandco · Dec 14, 2022

also minimum distance notification and Detailed notification see to no longer work so it does notr seem to be moniotring the log file like Other adons are

MattG · Dec 14, 2022

Thandco said:
also minimum distance notification and Detailed notification see to no longer work so it does notr seem to be moniotring the log file like Other adons are

I've seen someone else who had this problem. They sent me some of their journals and I verified they did in fact parse correctly in my installation - the problem was something their end. They managed to fix it by reinstalling new version of Observatory Core and then reinstalling BioInsights. If that doesn't fix it, also try removing (or upgrading) any other plugins you may have installed (or try reinstalling ObsCore to a different location). We hypothesized that another plugin may have been causing a problem which was somehow affecting BioInsights.

Kerada · Dec 14, 2022

New version of BioInsights seems to work great for me. I can't believe how quickly you updated this Matt! Much appreciated.

I'll use it and test some more later on today but so far, so good. Thanks again.

Kerada · Dec 14, 2022

~~BioInsights Codex Companion doesn't seem to update when I find a new variety now. It's a minor inconvenience but I thought I'd flag it up~~.
Oops! You mentioned this earlier. Sorry!

MattG · Dec 14, 2022

Kerada said:
BioInsights Codex Companion doesn't seem to update when I find a new variety now. It's a minor inconvenience but I thought I'd flag it up.

Yep, it's not updated yet as I ran out of time - there's a lot of internals that need rewriting. It's on the list, hopefully over xmas break.

Thandco · Dec 14, 2022

Turned out it was a Windows 10 Permission issue.

Thandco · Dec 17, 2022

One Diffence i did notice was that if a Biological is Not present ona Planet after a Scam is is not marrked with a X like before. For example is a planet has the possability for startum but the planataru scans Shows No Stratium is is not marked off untill After you leave the planet.

Kerada · Dec 17, 2022

Thandco said:
One Diffence i did notice was that if a Biological is Not present ona Planet after a Scam is is not marrked with a X like before. For example is a planet has the possability for startum but the planataru scans Shows No Stratium is is not marked off untill After you leave the planet.

Same here. My workaround for the time being is to scroll through the signals in the surface scan to see what's there.

varonica · Dec 17, 2022

Hey hey, see what I just pulled from a single system, just 4 moons!

CMDR Nizekki · Dec 22, 2022

Kerada said:
Same here. My workaround for the time being is to scroll through the signals in the surface scan to see what's there.

Same thing. But if you look carefully the BioInsights screen at the instant the DSS scan finishes, you will see the red Xs briefly appearing before going away.

MattG · Dec 29, 2022

I've put a new beta of BioInsights up here.

It should resolve the problem with DSS not updating, and has a bunch of speculative fixes for various other issues.

I still cannot reproduce the issue with installations in "Program Files" - if anyone is still experiencing this using the latest beta, please let me know if you're using Windows 10 or Windows 11. Please also go into BioInsights settings, enable Verbose Logging, do a Read All and send me the BioInsights.log.

varonica · Dec 29, 2022

MattG said:
I've put a new beta of BioInsights up here.

It should resolve the problem with DSS not updating, and has a bunch of speculative fixes for various other issues.

I still cannot reproduce the issue with installations in "Program Files" - if anyone is still experiencing this using the latest beta, please let me know if you're using Windows 10 or Windows 11. Please also go into BioInsights settings, enable Verbose Logging, do a Read All and send me the BioInsights.log.

Will try this, latest beta fixed the red x problem for me, still don't get proper notification about codex stuff, it sometimes tells me new codex stuff is there and it isn't, and then doesn't tell me it is there when it actually is, so lets see how this one goes.

varonica · Dec 29, 2022

Just testing new beta, this is what I got, also a message that the bodies may contain marked biologicals;

On checking, although I was sure already, all the bio's were already marked as confirmed in the codex.

You said earler this version of BI does some of the tasks that used to be done by Codex Companion, is it supposed to notify us on possible new codex discoveries or is this just a bug?

CMDR Sheehy · Dec 29, 2022

Yes, Windows 11. Yes, in Program Files (it's not going anywhere else for security reasons.)

MattG said:
I've put a new beta of BioInsights up here.

It should resolve the problem with DSS not updating, and has a bunch of speculative fixes for various other issues.

I still cannot reproduce the issue with installations in "Program Files" - if anyone is still experiencing this using the latest beta, please let me know if you're using Windows 10 or Windows 11. Please also go into BioInsights settings, enable Verbose Logging, do a Read All and send me the BioInsights.log.

The following is logged over and over (clean log file):


29-Dec-2022 06:08:32.931140 -----------------------------------------------------------------------------------------------
29-Dec-2022 06:08:32.931291 -> BioInsights v0.22.362.2328, CodexLib v0.22.362.2327, Core v0.2.22347.120
29-Dec-2022 06:08:32.935082 Obtained lock [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BISeen.bin.lck]
29-Dec-2022 06:08:32.938273 BCE ReadFile: 154 in [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BISeen.bin]
29-Dec-2022 06:08:32.938580 Disposing lock [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BISeen.bin.lck]
29-Dec-2022 06:08:33.065914 System database initialised [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BIScans.db] [mode=direct] (3224 cache entries)
29-Dec-2022 06:08:33.435520 [GPNCE] 1.0,25/12/2022 07:30:00,90,57862
29-Dec-2022 06:08:33.437654 [GPNCE] 755 entries
29-Dec-2022 06:08:33.466328 BioInsights Loaded
29-Dec-2022 06:08:35.437922 STATE: (NEW:PreRead),(PREVIOUS:Idle),(FLAG:True)
29-Dec-2022 06:08:35.852902 [enrichBrightestStar]
29-Dec-2022 06:08:35.852914 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.852915 ->    at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
29-Dec-2022 06:08:35.852922 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.853269 [enrichBrightestStar]
29-Dec-2022 06:08:35.853273 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.853274 ->    at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
29-Dec-2022 06:08:35.853275 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.860881 [ProcessMini] Exception <start2a>
29-Dec-2022 06:08:35.860895 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.860896 ->    at Observatory.BioInsights.BioInsights.ProcessScanMini(ScanMini mini)
29-Dec-2022 06:08:35.860897 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.906282 [enrichBrightestStar]
29-Dec-2022 06:08:35.906291 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.906292 ->    at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
29-Dec-2022 06:08:35.906293 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.906649 [enrichBrightestStar]
29-Dec-2022 06:08:35.906652 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.906653 ->    at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
29-Dec-2022 06:08:35.906654 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.907008 [ProcessMini] Exception <start2a>
29-Dec-2022 06:08:35.907012 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:35.907013 ->    at Observatory.BioInsights.BioInsights.ProcessScanMini(ScanMini mini)
29-Dec-2022 06:08:35.907015 -> <in ObservatoryBioInsights>
29-Dec-2022 06:08:35.990893 STATE: (NEW:Idle),(PREVIOUS:PreRead),(FLAG:False)
29-Dec-2022 06:08:35.991266 PreRead finished, PlanetSpecies contains 0 entries
29-Dec-2022 06:08:35.998660 STATE: (NEW:Realtime),(PREVIOUS:Idle),(FLAG:False)
29-Dec-2022 06:08:38.826585 STATE: (NEW:Realtime, Batch),(PREVIOUS:Realtime),(FLAG:True)
29-Dec-2022 06:08:38.827345 Started Read All
29-Dec-2022 06:08:38.830889 [DBH] DeleteAll <True>
29-Dec-2022 06:08:38.919491 [DBH] Closing handler
29-Dec-2022 06:08:38.945211 Deleted database file [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BIScans.db]
29-Dec-2022 06:08:38.948614 System database initialised [C:\Users\antho\AppData\Roaming\ObservatoryCore\ObservatoryBioInsights\BIScans.db] [mode=direct] (0 cache entries)
29-Dec-2022 06:08:39.182235 [enrichBrightestStar]
29-Dec-2022 06:08:39.182240 -> Object reference not set to an instance of an object.
29-Dec-2022 06:08:39.182241 ->    at Observatory.BioInsights.BISystem.enrichBrightestStar(ScanMini mini)
29-Dec-2022 06:08:39.182243 -> <in ObservatoryBioInsights>

Gut · Dec 29, 2022

Where's the Explorer ad on , i can't find it ?

MattG · Dec 29, 2022

varonica said:
Just testing new beta, this is what I got, also a message that the bodies may contain marked biologicals;

View attachment 339648

On checking, although I was sure already, all the bio's were already marked as confirmed in the codex.

You said earler this version of BI does some of the tasks that used to be done by Codex Companion, is it supposed to notify us on possible new codex discoveries or is this just a bug?

Did you do a Read All after installing new beta ?

varonica · Dec 29, 2022

Gut said:
Where's the Explorer ad on , i can't find it ?

Which one do you mean, the explorer is part of the Observatory program itself and not a plug in so you won't find it on MattG's plugins page.

varonica · Dec 29, 2022

MattG said:
Did you do a Read All after installing new beta ?

Good point, will do that and test again lol! I keep forgetting we need to do that.

MattG · Dec 29, 2022

CMDR Sheehy said:
Yes, Windows 11. Yes, in Program Files (it's not going anywhere else for security reasons.)

Fair enough - but this severely limits how I can help. I cannot reproduce the issue with an installation in Program Files running Windows 10, I do not have a PC capable of running Windows 11 (at least as far as Microsoft are concerned) - and even if I did, I wouldn't install it anyway for "security reasons".

If you wish, you can zip up all your journals and DM them to me so I can try to reproduce the problem you're having. Other than that I don't know what to suggest. Try the stand-alone version of Core?