MattG's Observatory plugins

I've uploaded a speculative fix for Evaluator. If it does the trick I'll apply similar logic to BioInsights.

Downloaded and installed, just logging off now so I won't be able to test for a few hours but I will let you know what happens when I do!
 
Ok, now it didn't work this last time, and there was a previously undiscovered and unmapped terraformable world in the system so evaluator should certainly have shown that, however this may be a case that's different from regular events. What I did was schedule a FC jump, log off and logged back on after the FC arrived in the system, in that case it doesn't show anything. This may be different to scheduling an FC jump and staying logged on and on board the FC as it jumps. I will test that next!
 
Ok, now it didn't work this last time, and there was a previously undiscovered and unmapped terraformable world in the system so evaluator should certainly have shown that, however this may be a case that's different from regular events. What I did was schedule a FC jump, log off and logged back on after the FC arrived in the system, in that case it doesn't show anything. This may be different to scheduling an FC jump and staying logged on and on board the FC as it jumps. I will test that next!

Ah, I know what's going on there, I will deploy another fix (once I finish muttering about FCs...)

Thanks for the report.

Edit: And done, new version is available for download
 
Last edited:
Ah, I know what's going on there, I will deploy another fix (once I finish muttering about FCs...)

Thanks for the report.

Edit: And done, new version is available for download

Whatever you did worked fine after my last logged off carrier jump (y)
 
Just a quick note to say I've updated BioInsights so it should correctly handle attended and unattended Carrier Jumps. I've also made a handful of small tweaks to the underlying Codex requirements for determining with bios might be present based on new data.
 
Just a quick note to say I've updated BioInsights so it should correctly handle attended and unattended Carrier Jumps. I've also made a handful of small tweaks to the underlying Codex requirements for determining with bios might be present based on new data.

Updated, will let you know if there are any issues!
 
Having tested the new version, it appears BioInsights isn't showing anything at all for any planets in any systems. The frist few being wd/ns where I am I thought it might just be that the systems didn't fit any of the codex info, so I hit a few more normal systems and still get nothing!
 
Having tested the new version, it appears BioInsights isn't showing anything at all for any planets in any systems. The frist few being wd/ns where I am I thought it might just be that the systems didn't fit any of the codex info, so I hit a few more normal systems and still get nothing!

Ok that's interesting. I just jumped into a different area with my FC, system names start with a different area name and all of a sudden it started working! The current system names start with Ingozz, previous system names were in the Ingowry area, is it possible that it may be affected? I may have to backtrack and test this one, it seems strange.
 
Doesn't seem to be anything to do with system names, that's seems to be working, but I was high up in the plane and hitting mainly WD and N's, maybe the data for bio in those systems hasn't been fully populated in the codex yet if that's where you are taking your predictions from!
 
Well that's annoying, I haven't been able to reproduce the issue, I will keep an eye on it and see of it crops up again any time.
 
Well that's annoying, I haven't been able to reproduce the issue, I will keep an eye on it and see of it crops up again any time.
I’ve noticed some oddities this weekend and will be prodding a bit more. At least a small handful of cases where bios were present but not predicted. The changes I made to Codex criteria were minimal so not 100% sure what’s going on just yet.
 
I’ve noticed some oddities this weekend and will be prodding a bit more. At least a small handful of cases where bios were present but not predicted. The changes I made to Codex criteria were minimal so not 100% sure what’s going on just yet.

It may be something to do with star type. Just jumped into a K class giant and despite 4 planets having 1 bio each nothing showed up in BioInsights. I've scanned several and they are just bacteria of course as expected.

I dropped onto a couple of planets to scan the bio and after scanning BioInsights shows up like this;

Wtd8v9K.png


It still works fine for regular stars in the area, so it may just be unsual star types, but why I have no idea.
 
OK, I've updated BioInsights to fix a few bugs and improve Codex rules further. It'll also write a log file for any errors that occur, and it has the option to send some simple data back when it encounters a Bio that was not predicted - this is toggleable in settings.

I've also added a new plugin called BoxelStats that myself and a couple others in IGAU have been using for a little while. It's for explorers performing surveys, and will give a breakdown things like observed Helium range, ELW count/ratio, total body count etc.
OJkGRSm.png

(Ah, what a fun boxel that was with 5 ELWs in just under 1000 systems - and each with over 23 bodies to scan on average... )
 
I've also added a new plugin called BoxelStats that myself and a couple others in IGAU have been using for a little while. It's for explorers performing surveys, and will give a breakdown things like observed Helium range, ELW count/ratio, total body count etc.
Wow, this makes me think I might want to install latest Observatory after all. (y)
Haven't done so yet, as old one and OpenOffice Calc have so far been enough for my needs.
 
OK, I've updated BioInsights to fix a few bugs and improve Codex rules further. It'll also write a log file for any errors that occur, and it has the option to send some simple data back when it encounters a Bio that was not predicted - this is toggleable in settings.

I've also added a new plugin called BoxelStats that myself and a couple others in IGAU have been using for a little while. It's for explorers performing surveys, and will give a breakdown things like observed Helium range, ELW count/ratio, total body count etc.
OJkGRSm.png

(Ah, what a fun boxel that was with 5 ELWs in just under 1000 systems - and each with over 23 bodies to scan on average... )

Ooh nice!
 
This is fantastic! I have been waiting for something like this! I will definitely download and install tonight and report back!

The only issue: I play in VR. Does it read the results, or do I need to remove my goggles to have a look on the monitor (I do it sometimes anyway, to look at other tools)

Looking forward to testing this! (y)
 
This is fantastic! I have been waiting for something like this! I will definitely download and install tonight and report back!

The only issue: I play in VR. Does it read the results, or do I need to remove my goggles to have a look on the monitor (I do it sometimes anyway, to look at other tools)

Looking forward to testing this! (y)

Not sure which of the plugins you were looking at specifically - but currently none of these report any notifications, just results in their own windows. That's not to say they couldn't be added (Observatory Core supports voice notifications just fine) - but I'd need to know what would be useful without it talking for minutes at a time.

I've also pondered how it might work with one of the VR Overlays... but this looks like a non-trivial problem.
 
Great tool, really happy.

Once comment: can the value reporting be wrong? I have visited a system with Water World, that has already been discovered, but not mapped. Your plugin reported maximum value of 567k, while EDDiscovery reported over 1.379M... have a look...


Untitled.jpg
 
I'm in now way an expert on DLLs, but

Code:
.method private hidebysig static int32  GetPlanetValue(float64 k,
                                                       float64 mass,
                                                       bool isFirstDiscoverer,
                                                       bool isMapped,
                                                       bool isFirstMapped,
                                                       bool withEfficiencyBonus,
                                                       bool isOdyssey,
                                                       bool isFleetCarrierSale) cil managed

bools isFirstMapped but everywhere else in the DLL this is named isFirstMapper.
 
Great tool, really happy.

Once comment: can the value reporting be wrong? I have visited a system with Water World, that has already been discovered, but not mapped. Your plugin reported maximum value of 567k, while EDDiscovery reported over 1.379M... have a look...


View attachment 265861

That looks like the payout for mapping without First Discovery, I see that value in your screenshot for "mapping value". One of the two is incorrect of course, looking around at other sources it appears that maybe MattG is correct and EDdiscovery is giving an erroneous value, non-terraformable water worlds without first discovery but with DSS should pay around 500k according to the chart linked by this reddit post;

Source: https://www.reddit.com/r/EliteDangerous/comments/avsszo/updated_visual_guide_to_scan_values_in_33/


Need someone to test this I suppose to see what values they actually get but I believe MattG's plugin gives the expected value for mapping and FSS without FD, adding the values from the chart, 415,613 for mapping and 99,717 for FSS without first discovery gives us 515,330 (that's an average of data of course so won't be exactly the same) so that seems to be correct according to the chart.

Best we can say at the moment is, one of these is wrong until someone goes out and tests it.
 
Back
Top Bottom