I have noticed that myself, switching between SRV and ship does appear to cause this issue, I mainly hunt long range stuff only by ship and that always works, if I do short range stuff and stay in SRV or on foot that always works, but if I can't find stuff and switch to ship, doesn't always work.
MattG's Observatory plugins
- Thread starter MattG
- Start date
I have noticed that myself, switching between SRV and ship does appear to cause this issue, I mainly hunt long range stuff only by ship and that always works, if I do short range stuff and stay in SRV or on foot that always works, but if I can't find stuff and switch to ship, doesn't always work.
I dunno. It happens to me in the ship, or the SRV, at what seem to be random times. The pop up is displayed by Observatory Core, though, I'm sure. Perhaps it sometimes ignores the call from BioInsights. I'm not sure how the underlying code works.
For what it's worth, the failure I had this morning was the only time it didn't work for me today. The rest of my scans it did work.
For what it's worth, the failure I had this morning was the only time it didn't work for me today. The rest of my scans it did work.
A couple of updates.
BioInsights
Oh, and there's also a mysterious 'Link Discord' button. Unless you've been specifically invited to beta test certain features, this button won't do anything for you
.
CodexCompanion
Colliders
As always, you can grab them here
BioInsights
- Massive improvements in Recepta false-positives. Testing shows a reduction of around 96% of all Recepta predictions.
- Fixes for a small handful of Bacterium that were not being correctly predicted. Also made the current criteria a bit stricter for all Bacterium species to hopefully improve predictions
- When DSSing a planet (mapping before landing), any predicted biologicals that are not present will be marked as such
- When in a system where a marked biological is detected on multiple bodies, the first scan of the biological will removed the marks on the other bodies.
- The legend in settings is finally no longer a huge button
- Various small tweaks and fixes
- Note that BioInsights requires the latest Core release. Using it with the older release is liable to crash. Also, you should do a one-off Read All after upgrading BioInsights to ensure the background data is consistent for this release.
Oh, and there's also a mysterious 'Link Discord' button. Unless you've been specifically invited to beta test certain features, this button won't do anything for you
.CodexCompanion
- Updated to reflect current rules used by BioInsights
- Ensured background data stored in same place as BI data.
- Added limited logging
- Hopefully fixed the "lock up and flashing buttons" seen by @Ultra Fluffy
Colliders
- I think the last issue in Colliders is finally resolved, and I've witnessed it successfully predict even fast moving and fleeting collisions down to the minute. (Now to work on the Orrery model...).
- You can now sort on next collision time or by name
- As the math has changed slightly, you'll need to do a one off Read All to get your existing colliders list back
As always, you can grab them here
Last edited:
Yeah that's strange, I will test it myself to see if I can trigger it, but it seems to be related to scanning in SRV then going back to ship and using that to search for next sign. If I stay in one or the other to scan I have never had it happen. I will test and see if I can get it to reliably trigger, but not right not, I am heading back to FC for emergency repairs
Yeh, it's quite a pain to try and debug a problem you can't reproduce, and are sure isn't possible
I'm hoping it is just some mis-reported / missing position data causing it, and that these tweaks will fix it.
If not, I'll have to look into adding more logging specifically in the distance notifier.
There is - check in Settings and hit "Show Legend".
Also, if anyone downloaded before this post you should re-grab BiopInsights. In attempting to fix distance notifications, I broke distance notifications...
Ah, cool, I missed seeing it there. Thank you
Haha. It should be correct. Colliders will check up to 20 years into the future so that one will only have been detected in the last 3 months.
Something to pencil in the diary
I also don't get the notification, when I reach the distance.
And my Message Window won't go away after the setted milliseconds. (This might not be caused by the plugin...)
But it will count the sample from 1 of 3 to 2 of 3 and the message window disappears, when the 3rds sample is collected.
And my Message Window won't go away after the setted milliseconds. (This might not be caused by the plugin...)
But it will count the sample from 1 of 3 to 2 of 3 and the message window disappears, when the 3rds sample is collected.
Last edited:
Is that definitely BioInsights? That sounds like it might be Botanist instead?
Thanks so much for Elite Observatory, while exploring it has its fixed place on my screen.
Only problem is the SignalMonitor (v 228.1052). I was visiting systems with NSPs but there was no notification or entry in the list. Never. Of course, ticks in the core are set.
Am I the only one experiencing this?
Only problem is the SignalMonitor (v 228.1052). I was visiting systems with NSPs but there was no notification or entry in the list. Never. Of course, ticks in the core are set.
Am I the only one experiencing this?
@MattG , Just for your information:
I scanned a plant using the SRV and it said that it was a "Not predicted" Cactoida Vermis Green. However when I scan it using the hand scanner it said that it was a predicted Cactoida Pullulanta Green. Not a bug in BioSights, it is in Elite Dangerous itself. Just did not want you wasting your time adjusting your prediction tables!!
I scanned a plant using the SRV and it said that it was a "Not predicted" Cactoida Vermis Green. However when I scan it using the hand scanner it said that it was a predicted Cactoida Pullulanta Green. Not a bug in BioSights, it is in Elite Dangerous itself. Just did not want you wasting your time adjusting your prediction tables!!
Done !!
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) ?Just ran a read all on Observatory and it returned far fewer signals than I know are there, only shows a single NSP, a single Listening Post and a single Unregisterd Coms Beacon. The NSP it shows is from 25th January 2019, whereas the latest entry for NSP's in EDDiscovery is from 18th September 2022, so something definitely odd here. Last time I did a read all it showed quite a large list of signals, EDDiscover shows a large number of NSP's in the journal.
This is my EDDiscovery list for the last few, none of which showed up when I did the read all.
So something odd here, they should show up in signals on a read all, they all did last time.
Curious all 3 that show are all from 2019, it's as if Observatory isn't reading the later journals, which may be the issue here with not showing the signals when it's running, something changed recently?
Last edited: