Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!

MattG

MattG
GraphicEqualizer said:
Question/Suggestion... could a rule or core functionality of Bio Insights alert me to the likelihood of a body having a genus/species that I have not yet recorded in Codex Companion... similar to how there are the alerts for chances of high value ones... I really like the little endorphine hit from the 'new codex entry' fanfare regardless of intinsic value
Click to expand...
If I'm understanding you correctly - yes, it already does this.

In CC, Select "Any Region" then hit "Bulk Action" and select "Mark Unseen Variants in current region", then hit Go. This will mark anything you've not seen anywhere. When BI thinks it might be possible on a given body it will send a notificaiton and the possible bio will have a blue diamond (or other mark ikf you use different symbol set). I'd strongly suggest ticking "supress notifications for unlikely marked vartiants" in BI settings or you'll be getting false positives all the time. When you do scan a marked bio, it will automatically get unmarked - unless you choose "persistent mark" then it will... persist.

You can also do the same for all regions (there's a bulk action to do it) but I personally only want to collect 1 of everything, I don't care where.
 

GraphicEqualizer

GraphicEqualizer
MattG said:
If I'm understanding you correctly - yes, it already does this.

In CC, Select "Any Region" then hit "Bulk Action" and select "Mark Unseen Variants in current region", then hit Go. This will mark anything you've not seen anywhere. When BI thinks it might be possible on a given body it will send a notificaiton and the possible bio will have a blue diamond (or other mark ikf you use different symbol set). I'd strongly suggest ticking "supress notifications for unlikely marked vartiants" in BI settings or you'll be getting false positives all the time. When you do scan a marked bio, it will automatically get unmarked - unless you choose "persistent mark" then it will... persist.

You can also do the same for all regions (there's a bulk action to do it) but I personally only want to collect 1 of everything, I don't care where.
Click to expand...
SQUEEEEE!!!!

I can't believe it was there the whole time and I missed it, especially seeing as I'm a bit of a tinkering nerd myself... this is my shame face 🤡 (what a clown!) Confirmed it is already urging me to go check out places I might not have not bothered with.

I wonder if others might have not have put two and two together and realised this feature was there, and if there could be some way to bring awareness of it to the forefront somehow in the UI... maybe a first launch prompt like a "Do you want to be alerted of...?" -- I do recall seeing the option to mark unseen things in the CC display, but I must have just assumed that was only going to mark those things in the CC tabs, not also alert me to them. I'm a dumdum. lol

I continue to sing the praises of this whole framework at every opportunity... it's really fantastic work.
 
Last edited:

Galactic Fork

Galactic Fork
Is there a way to get numbers in custom criteria to display with commas like in the included criteria? For example for close ring proximity, it says "DIstance from ring: 14,368km." But in the custom criteria I made for moons close to rings but with high orbital Inclination, it says "Distance from ring: 14368km."

This is what I have:
Code: 
::Criteria::
if scan.Landable and parents and parents[0].Scan and parents[0].Scan.Rings then
    if scan.SemiMajorAxis - parents[0].Scan.Rings[0].OuterRad > 0 and scan.SemiMajorAxis - parents[0].Scan.Rings[0].OuterRad < 15000000 then
             if scan.OrbitalInclination > 2 or scan.OrbitalInclination < -2 then
            RingDistance = (scan.SemiMajorAxis - parents[0].Scan.Rings[0].OuterRad)/1000
            return true,
                'Close Ring Proximity with Inclined Orbit',
                string.format('Distance from ring: %.0fkm, Inclination:  %.3f°', RingDistance, scan.OrbitalInclination, scan.SemiMajorAxis)
        end
    end
end
::End::
 

Eahlstan

E
If nothing fundamental has changed LUA doesn't allow the required printf thing to be passed through to the underlying program. So you'd have to make your own function to do that. The bad thing with this is, that this only runs in the local language setting it's coded for (so no replacement of . and , when switching your settings from English to German).
Here are example codes for such functions.
 

Galactic Fork

Galactic Fork
Eahlstan said:
If nothing fundamental has changed LUA doesn't allow the required printf thing to be passed through to the underlying program. So you'd have to make your own function to do that. The bad thing with this is, that this only runs in the local language setting it's coded for (so no replacement of . and , when switching your settings from English to German).
Here are example codes for such functions.
Click to expand...
Thanks, I found one and am beginning testing!

Edit: Worked! Looks better along side premade criteria. Thanks again!
 
Last edited:

Galactic Fork

Galactic Fork
OK, sorry to post again, but I think I found a bug. The Close ring proximity missed a moon today. it was only 10000km away.
1664850182842.png


Also, how do you specify the outermost ring when comparing the ring outer radius to the semi major axis of the moon? In the same system, there was another moon (BC 2 a) that was 28,880km from its parent's ring, and I adjusted my custom criteria to extend the allowed distance and my criteria was reading the distance from the inner ring to the moon which is 115020km. The first moon I mentioned (BC 1 a) above didn't come up at all as a result of my edited criteria. Event the 2nd (BC 1 b) and 3rd (BC 1 c) moons don't appear event though I made the limit 20000000000meters and BC 2 b and BC 2 c do appear. . The only thing different about that gas giant was that I scanned the moons before I scanned the Gas Giant.

Feel free to ask any additional information.
 

Eahlstan

E
This triggers when the radius of the body multiplied by 10 is smaller than the difference between the inner or outer radius of the ring minus the semi major axis.
Your body might just have been too small to trigger it at that distance.
 

Galactic Fork

Galactic Fork
Eahlstan said:
This triggers when the radius of the body multiplied by 10 is smaller than the difference between the inner or outer radius of the ring minus the semi major axis.
Your body might just have been too small to trigger it at that distance.
Click to expand...
Are you sure it's not the other way around? the semi major axis minus the outer radius (or inner). The other way would be a negative number. And wouldn't it be when 10 times the radius is larger than the distance? Other wise most bodies would trip it.

Either way either BC 1 A or BC 1 B should have come up.

BC 1 A - Radius is 1144.6km (Radius*10 is 11446). Semi Major Axis is 238,744.6km and the outer ring's outer radius is 228,450km. difference of 10294 vs 11446. (radius larger than difference).
BC 2 A - Radius is 950.9km (Radius *10 is 9509). Semi Major Axis is 252,900.1km and the outer ring's outer radius is 224,020km . Difference of 22880.1 vs 9509 (Radius smaller than difference).
 

Eahlstan

E
There's a function in there that turns negative numbers into positives.
It would be possible to check if you paste the scan events here.
 

MattG

MattG
Galactic Fork said:
The first moon I mentioned (BC 1 a) above didn't come up at all as a result of my edited criteria. Event the 2nd (BC 1 b) and 3rd (BC 1 c) moons don't appear event though I made the limit 20000000000meters and BC 2 b and BC 2 c do appear. . The only thing different about that gas giant was that I scanned the moons before I scanned the Gas Giant.
Click to expand...

I think the last sentence is the key to your problems. The custom criteria fires at the moment you generate the Scan event. If you scan a moon first, while it does know who the parent(s) of the moon are, it doesn't have any details of the parent until you've scanned it; it doesn't know if the moon is close to the parent ring (or whatever you're checking) and so doesn't fire a notification.

You can write a custom criteria to account for this but it's a little bit more involved - you'll need to iterate through each body in the system object, check if it has a parent that is the scanned body, and then fire your logic acordingly.

(Or get in the habit of scanning the gas giant before it's moons when using FSS :))
 

Galactic Fork

Galactic Fork
Can
MattG said:
I think the last sentence is the key to your problems. The custom criteria fires at the moment you generate the Scan event. If you scan a moon first, while it does know who the parent(s) of the moon are, it doesn't have any details of the parent until you've scanned it; it doesn't know if the moon is close to the parent ring (or whatever you're checking) and so doesn't fire a notification.

You can write a custom criteria to account for this but it's a little bit more involved - you'll need to iterate through each body in the system object, check if it has a parent that is the scanned body, and then fire your logic acordingly.

(Or get in the habit of scanning the gas giant before it's moons when using FSS :))
Click to expand...
Since this includes the built in criteria of "Close ring proximity," can you add a warning for others that some of their selected options won't appear unless they scan the parent first?
 

Vithigar

Vithigar
Minor update, I've repackaged the portable .zip version on the release page. The incorrect versions of the included plugins were bundled. If you're using that version and experience any issues, re-downloading it may resolve them.

The installed version is unaffected.
 
You must log in or register to reply here.
Back
Top Bottom