That bug should've been fixed a while ago. What version are you running? Can check in the details tab of the exe properties window. Newest version is 0.4.19.315.Here you go:
![]()
That bug should've been fixed a while ago. What version are you running? Can check in the details tab of the exe properties window. Newest version is 0.4.19.315.Here you go:
![]()
Got it, just reproduced myself no problem. Strange that no one else has brought it up.
At my job we deal with this sort of thing surprisingly often. It's like "How did this EVER work? And why hasn't anyone complained about it before? It's been like this for years." LOL![]()
I want to show moons of ringed bodies with high orbital inclinations because they provide rare and unique photographic opportunities; you get to see the rings from such moons.What's an "offset ring orbit" supposed to represent? Looks like you just want to show a moon with a high orbital inclination? What does that have to do with rings? (rings never have high inclination anyway, they should all be in the planet's equatorial plane)
<Criteria Comparator="And">
<Criteria Comparator="Greater" Value="1.0">
<Operation Operator="None">
<FirstValue Type="EventData">MassEM</FirstValue>
</Operation>
</Criteria>
<Criteria Comparator="Greater" Value="1.0">
<Operation Operator="None">
<FirstValue Type="EventData">Age_MY</FirstValue>
</Operation>
</Criteria>
<Description>Greater than 1 EM and 1 MY</Description>
<Detail>
<Item>MassEM</Item>
</Detail>
</Criteria>
It had not even occurred to me that an asteroid belt would ever trigger a close ring proximity check, that's actually kind of incredible.
I'm not surprised that you can't see any asteroid clusters from the planet, but do you perhaps get a good view of the planet from any clusters?
I'm of two minds as to whether or not I should prevent that check from triggering on asteroid belts. It's probably not every going to be visually interesting, but it does seem noteworthy. Thoughts?
In general it seems that the game considers asteroid belts to be rings, the log shows it that way....
StarType":"F", "StellarMass":1.148438, "Radius":762974144.000000, "AbsoluteMagnitude":4.174454, "Age_MY":6502, "SurfaceTemperature":6415.000000, "Luminosity":"V", "RotationPeriod":286091.812500, "AxialTilt":-0.049108, "Rings":[ { "Name":"KOI 100 A Belt", "RingClass":"eRingClass_Metalic", "MassMT":1.3812e+14, "InnerRad":1.4104e+09, "OuterRad":2.527e+09 } ] }
On one hand, having a ring check for stars is helpful, we actually want to find those. On the other hand, actual rings and not asteroid belts are super-rare and really obvious when you jump in. I think this is going to need the app to pass on the actual ring data so we can choose to filter on the name or class.
Trying to figure out a check to see if a body is a star. Can't use PlanetClass for obvious reasons, so trying to filter on a field that only exists if the object is a star. StellarMass is one of those. This would be easy if an 'Exist' operator was present, returning true if the field was there and false if not. But it's not, so various things I tried....
This does not work (and I didn't really expect it to):
<Criteria Comparator="Less" Value="0.0">
<Operation Operator="None">
<FirstValue Type="EventData">StellarMass</FirstValue>
</Operation>
<Description>Not A Star</Description>
</Criteria>
Nor does this:
<Criteria Comparator="Equal" Value="0">
<Operation Operator="None">
<FirstValue Type="EventData">StellarMass</FirstValue>
</Operation>
<Description>Not A Star</Description>
</Criteria>
And this caused an application crash:
<Criteria Comparator="Not">
<Criteria Comparator="Greater" Value="0">
<Operation Operator="None">
<FirstValue Type="EventData">StellarMass</FirstValue>
</Operation>
<Description>Not A Star</Description>
</Criteria>
</Criteria>
as well as this:
<Criteria Comparator="Not">
<Operation Operator="None">
<FirstValue Type="EventData">StellarMass</FirstValue>
</Operation>
<Description>Not A Star</Description>
</Criteria>
<Criteria Comparator="Not">
<Criteria Comparator="Greater" Value="0">
<Operation Operator="None">
<FirstValue Type="EventData">StellarMass</FirstValue>
</Operation>
</Criteria>
<Description>Not a star</Description>
</Criteria>
Attached is a first pass at a custom criteria file for detecting galactic record-setting bodies. It covers all the planets, but no stars (yet). Using the current EDSM data it should detect any bodies that are new records in terms of mass, size, or surface temperature. Some of the bodies do not have detection for lower mass or surface temperature; planets of 0 K somehow exist, and earth masses < 0.00 EM. I might pull more detailed data out for those super-low masses and add them. Also note in some cases I have rounded up by a whole number (1.0) to make sure detection properly occured.
Please feel free to review/suggest.
How about gravity records?Attached is a first pass at a custom criteria file for detecting galactic record-setting bodies. It covers all the planets, but no stars (yet). Using the current EDSM data it should detect any bodies that are new records in terms of mass, size, or surface temperature. Some of the bodies do not have detection for lower mass or surface temperature; planets of 0 K somehow exist, and earth masses < 0.00 EM. I might pull more detailed data out for those super-low masses and add them. Also note in some cases I have rounded up by a whole number (1.0) to make sure detection properly occured.
Please feel free to review/suggest.
The first two fail because no value isn't zero, it's no value (null). In C# all comparisons against null values are false except "not equal".*
This is very nice, thanks for compiling this criteria list. I downloaded and will test. But one bug question in my mind: how it will get updated? Looks like it is a static list on the local PC and will become outdated regularly when new records are discovered.
How about gravity records?