Definitely not a problemSince the Telegram plugin is open-source and MIT licensed I'd like to include it as an option in the installer, if that's not a problem.![]()
After using them for about a week, I love your plugins, in particular the BioInsights and the BoxelsStats.
Regarding the latter I have a little request for you to consider.
Yesterday I arrived in a new boxel. The first ~50 systems I fully FSS-scanned to build up a proper statistic of the boxel. After that, as part of the ELW hunt (unsuccessful in this case), I went Chiggy mode as I call it, that is just checking the FSS for ELWs, and if there are none just continue to the next system. If uncertain I might FSS-scan some Rice balls or AWs, but I usually don't fully FSS the system.
The little problem that I have with the BoxelStats is that such incompletely FSSed systems water down the body-specific stats - after the first 50 systems the rates were about twice as good as they are listed now.View attachment 270645
So the request would be that for these ratios only fully FSSed systems should be counted.
Yeah, it will still be impacted, like by star-only systems,or when I fully FSS a ELW systems, but not as drastic.
There is anI'm not 100% sure how possible this will be, but leave it with me and I'll see what I can do.
FSSAllBodiesFound
event. Should be fairly straightforward to hold on committing results to your total until that is seen.namespace Observatory.Framework.Files.Journal
{
public class FSSAllBodiesFound : JournalBase
{
public string SystemName { get; init; }
public ulong SystemAddress { get; init; }
public int Count { get; init; }
}
}
I’d need to make it an option, meaning it would only affect presentation, and that’ll mean recording a chunk of extra data. It’s doable, but conscious how much memory the stored data starts to use.There is anFSSAllBodiesFound
event. Should be fairly straightforward to hold on committing results to your total until that is seen.
C#:namespace Observatory.Framework.Files.Journal { public class FSSAllBodiesFound : JournalBase { public string SystemName { get; init; } public ulong SystemAddress { get; init; } public int Count { get; init; } } }
{ "timestamp":"2021-10-18T20:10:10Z", "event":"FSSDiscoveryScan", "Progress":0.274203, "BodyCount":22, "NonBodyCount":3, "SystemName":"Blia Chria LL-X b1-1", "SystemAddress":2529065007121 }
In the wake of update 8 bio-insights seems to have stopped working. It was working fine before the update, no other change and after the update it's no longer working. Strange, just going in to test again.
Not had time to get on and check anything yet, and possibly not for a couple of days yet - I will keep my eyes open for any oddness though, in all the plugins. I have a few small tweaks to make to the codex rules in BioInsights at some point too.Working now, really strange, I passed through a couple of systems this morning with bio and bio-insights said nothing, now after restarting everything it's working again, some sort of anomaly in the systems I passed through earlier maybe?
Not had time to get on and check anything yet, and possibly not for a couple of days yet - I will keep my eyes open for any oddness though, in all the plugins. I have a few small tweaks to make to the codex rules in BioInsights at some point too.
That is… very odd. But it does give me some clues to look at. Might be a few days before I can investigate properly though.Ok, I have worked out the problem with BioInsights, it's peculiar, bizarre even, didn't believe it myself at first.
The clue came after update 8. Fire up the game, upgrade it, start the game it make sure it's running ok, start my tools up, go exploring. BioInsights reports nothing for bodies it should be reporting on, strange but maybe something to do with the update, so I report here.
Shut everything down and start playing again later, this time do my normal start up, start my tools to get them loaded, start the game, BioInsights works fine, report here that it's not the update, and then it hits me, is it what I'm doing that's causing the problem?
So I test, start EDDiscovery, start the game, then start Observatory, BioInsights doesn't report bio for candidate planets, check a few systems and still nothing. Shut game and tools down, start everything from scratch, EDDiscovery, then Observatory, then the game. First candidate system I jump into BioInsights reports immediately.
So it seems if I start Observatory after I start the game BioInsights doesn't work, if I start Observatory before I start the game BioInsights does work, most peculiar! Just to note the order of startup doesn't seem to affect any other plugins, just BioInsights.
That is… very odd. But it does give me some clues to look at. Might be a few days before I can investigate properly though.
Great plugins. I particularly like BioInsights. I find it really accurate.
A couple of issues:
- In BioInsight there is an option "Only show current system". It does not appear to work. I'm getting Bio data staying in table until I scan a planet/noon that has enough interest to cause the notification box to appear. That could be several systems away.
- Could we have an option to start BioInsight monitoring on start up.
- Could we have some indication as to the number of bio scans have been done with the handheld gizmo. I believe that there is enough info in the journal files.
When you find biologicals you need to do 3 scans with the hand gadget. If you doing that over a couple of sessions it is easy to forget:
- It’s not clearing down the table when jumping to a new system until the first “interesting” scan. It’s on my todo list, just not had a chance to fix it yet.
- This is actually something that ObsCore needs to add - it’s definitely on Vithigar’s list though so hopefully soon
- Could you elaborate a bit? You mean total hand scans ever, or something else? Where would this information be shown?
When you find biologicals you need to do 3 scans with the hand gadget. If you doing that over a couple of sessions it is easy to forget:
I hadn't spotted that, but that tells you how many scans you have done and not what species.