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

Speccy

Speccy
I'm trying to set up a custom criteria to alert me for landable planets with carbon dioxide atmospheres, but it's not working. This is the xml I'm using:
Code: 
    <Criteria Comparator="And">
        <Criteria Comparator="Equal" Value="1">
            <Operation Operator="None">
                <FirstValue Type="EventData">AtmosphereType: CarbonDioxide</FirstValue>
            </Operation>
        </Criteria>
        <Criteria Comparator="Equal" Value="1">
            <Operation Operator="None">
                <FirstValue Type="EventData">Landable</FirstValue>
            </Operation>
        </Criteria>
        <Description>Landable body w/ carbon dioxide atmosphere</Description>
    </Criteria>
What am I doing wrong?
 

Vithigar

Vithigar
Speccy said:
I'm trying to set up a custom criteria to alert me for landable planets with carbon dioxide atmospheres, but it's not working. This is the xml I'm using:
Code: 
    <Criteria Comparator="And">
        <Criteria Comparator="Equal" Value="1">
            <Operation Operator="None">
                <FirstValue Type="EventData">AtmosphereType: CarbonDioxide</FirstValue>
            </Operation>
        </Criteria>
        <Criteria Comparator="Equal" Value="1">
            <Operation Operator="None">
                <FirstValue Type="EventData">Landable</FirstValue>
            </Operation>
        </Criteria>
        <Description>Landable body w/ carbon dioxide atmosphere</Description>
    </Criteria>
What am I doing wrong?
Click to expand...
There should not be a space after the colon for AtmosphereType.

Code: 
AtmosphereType:CarbonDioxide
 

Speccy

Speccy
Thanks. You may want to remove the space in the example in the Custom Criteria file:

Code: 
AtmosphereType returns 1 if the type scanned matches the type provided, otherwise
        returns 0, e.g., "AtmosphereType: CarbonDioxide".
 

Vithigar

Vithigar
New release of Observatory Core is looming folks. Headline features will be some very nice improvements for the basic built-in notifications, and a an actual application installer. Possibly a couple of other items, but that's the bare minimum.
1630176288798.png


There will also be a small update for the original Elite Observatory sometime soon, with a couple of very minor fixes (such as the above sample criteria snafu), but primarily a change to the update check to also offer the latest released version of the Observatory Core installer.
 
Last edited:

idahosurge

idahosurge
Does this search for materials sold to Bartender's like biological samples?

I would like to see how many I sold since looking through all journals since May 19th would take way to long to bother with.
 

Vithigar

Vithigar
idahosurge said:
Does this search for materials sold to Bartender's like biological samples?

I would like to see how many I sold since looking through all journals since May 19th would take way to long to bother with.
Click to expand...
It does not currently, but a plugin could be made for Observatory Core to do so.
 

Vithigar

Vithigar
General polish pass: Installer, Icon, and more!

github.com

Release General polish pass: Installer, Icon, and more! · Xjph/ObservatoryCore

Some major housekeeping and some new features now available for testing! The major headline features of this patch are an actual application installer and application icon, plus a complete cosmetic...
github.com github.com

Some major housekeeping and some new features now available for testing! The major headline features of this patch are an actual application installer and application icon, plus a complete cosmetic overhaul of the built-in basic notifications along with a number of settings to configure their appearance.
The explorer and botanist plugins are now also bundled in the installer package, but may be optionally deselected at install time if you desire.
A "portable" version (0.0.241.2331) is still available in ObservatoryCore.zip.
Several other under-the-hood fixes have also happened since last release. I will attempt to provide a full list below, but may have missed some:

Core​

  • Brand new appearance and settings for built-in basic notifications
  • Several under-hood fixes for notification plugin loading (no user impact currently)
  • Fixes for pre-read causing unnecessary notifications to pop
  • Application icon added
  • Application installer created
  • Donation and github links are now slightly larger

Framework​

  • Handle new data type for fleet carrier distance travelled
  • Corrected several journal entry classes being marked private
  • Added handling for slider and roller numeric setting entry methods for plugins

Explorer​

  • Custom criteria performance improvement during read-all
  • Tidied up notification text
  • Added AtmosphericComposition to available custom criteria variables
  • Added Materials to available custom criteria variable
  • Cleaner handling of empty ring lists for custom criteria
  • Cleaner handling of nested objects for custom criteria

Botanist​

  • No changes

I'll be posting an updated guide for using the new custom criteria soon, so stay tuned for that!
 

Vithigar

Vithigar
Major focuses that I'd like to get feedback on with this release:

The installer should hopefully work for most everybody. .NET 5 is no longer packaged directly into the .exe, making the application size much smaller. The installer should reach out and download the .NET 5 runtime if necessary. Please let me know if this fails to work. (Note: This is not true of the portable version, which is a separate build that does still bundle .NET 5.)

The built-in notifications are in what I consider to be a close to final state now. There is still some wonkiness with their positioning (I may just add manual offset settings to allow users to fine tune this), but do please give feedback about how you feel about them and any changes you'd like to see now.

Finally, how do people feel about the new icon? I quite like it. :D
 

varonica

varonica
Fired it up and set it to do a read all in biologist, it came up with this;

The JSON value could not be converted to Observatory.Framework.Files.ParameterTypes.CrimeType. Path: $.CrimeType | LineNumber: 0 | BytePositionInLine: 105.
File: Pre-read
Line: { "timestamp":"2021-06-23T02:59:35Z", "event":"CommitCrime", "CrimeType":"onFoot_failureToSubmitToPolice", "Faction":"The Outcasts", "Victim":"Maxwell Tucker", "Fine":500 }

The JSON value could not be converted to Observatory.Framework.Files.ParameterTypes.CrimeType. Path: $.CrimeType | LineNumber: 0 | BytePositionInLine: 128.
File: Pre-read
Line: { "timestamp":"2021-06-23T02:59:35Z", "event":"CrimeVictim", "Offender":"Varonica", "CrimeType":"onFoot_failureToSubmitToPolice", "Fine":500 }

The JSON value could not be converted to Observatory.Framework.Files.ParameterTypes.CrimeType. Path: $.CrimeType | LineNumber: 0 | BytePositionInLine: 105.
File: Pre-read
Line: { "timestamp":"2021-07-04T14:03:29Z", "event":"CommitCrime", "CrimeType":"onFoot_failureToSubmitToPolice", "Faction":"The Outcasts", "Victim":"Karlee Callahan", "Fine":500 }

The JSON value could not be converted to Observatory.Framework.Files.ParameterTypes.CrimeType. Path: $.CrimeType | LineNumber: 0 | BytePositionInLine: 128.
File: Pre-read
Line: { "timestamp":"2021-07-04T14:03:29Z", "event":"CrimeVictim", "Offender":"Varonica", "CrimeType":"onFoot_failureToSubmitToPolice", "Fine":500 }
Click to expand...

Going to test it in actual play rather than just a read all test later!

Ah it looks like read all when in bio doesn't just look for bio stuff then, it also does explorer stuff, so that may be related to that as well, anyway I'll leave it to you, it did seem to come up with a lot and didn't just crash so that's good!
 

Vithigar

Vithigar
varonica said:
Fired it up and set it to do a read all in biologist, it came up with this;



Going to test it in actual play rather than just a read all test later!

Ah it looks like read all when in bio doesn't just look for bio stuff then, it also does explorer stuff, so that may be related to that as well, anyway I'll leave it to you, it did seem to come up with a lot and didn't just crash so that's good!
Click to expand...
Read all is a complete journal parse of every event (Core doesn't "know" what plugins need which events), so if there's anything in your history that can't parse it'll trip on it and fail. Frontier failed to list all the possible crime types in their documentation, so I've had to add the new ones piecemeal as I've encountered them. Will take care of onFoot_failureToSubmitToPolice now and it will be handled in the next release.

A failure to correctly read crime types should (hopefully!) not be an issue while exploring!
 

varonica

varonica
Vithigar said:
A failure to correctly read crime types should (hopefully!) not be an issue while exploring!
Click to expand...

Yeah that was while I was still testing Odyssey stuff in the bubble, not doing that at the moment so as you say not going to be an issue. Poor documentation, that's new /s
 

Vithigar

Vithigar
Big news!

I've been somewhat dissatisfied with how the new custom criteria format has been working and decided to throw it out completely and start over!

CodingSeb's Expression Evaluator is a very neat tool and very simple to implement, but has many edge cases that trip it up, and doesn't handle Observatory's Scan data type as well as I'd like, so I finally made the decision to switch to something else. That something else will be...

Lua!

While adding a Lua script engine to the Explorer plugin brings along a bit more in the way of dependencies as compared to Expression Evaluator, which is a single self-contained class, it has an enormous advantage in terms of maturity and robustness that make the very slightly increased dependency load more than worth it.

A quick peek at two simple criteria using the new Lua based custom criteria format:
1630349307315.png


Why Lua in particular? Mostly its combination of extreme maturity (28 years old!) and lightweight implementation. Adding a complete Lua compiler to Observatory Explorer is a mere 600KB or so of extra libraries.

So brush up on your Lua (or go find a friend who has experience writing Roblox games or WoW addons)!
 
Last edited:

Vithigar

Vithigar
Another peek at the Lua based custom criteria:
1630611103071.png

1630611118035.png


Both single-line simple evaluations like in my previous post, and more complex scripts like this one, will be options for how to write criteria.

I still have a couple of kinks I need to work out, but should be good for a release this weekend.
 
Last edited:

varonica

varonica
Vithigar said:
Another peek at the Lua based custom criteria:
View attachment 260658
View attachment 260659

Both single-line simple evaluations like in my previous post, and more complex scripts like this one, will be options for how to write criteria.

I still have a couple of kinks I need to work out, but should be good for a release this weekend.
Click to expand...

Nice, just to update, I have been using the current release since it came and have encountered no other issues apart from that first one when scanning all journals, so all good so far!
 
You must log in or register to reply here.
Back
Top Bottom