I think we need to start a comprehensive listing of all known plugins - there was another one I tried a while ago which was also good, for something, I cannot remember now dammit cos I fresh reinstalled core LOL
Elite Observatory - Search your journal for potentially interesting objects, or notify you of new ones on the fly while exploring!
- Thread starter Vithigar
- Start date
This is something that's coming along with other documentation improvements in general. Will hopefully reveal that alongside the release once this overhaul is ready.
You are a legend!
Pre-release refresh!
Core
Core
- HUGE refactor from side-menu faux-tab monstrosity to normal tabs
- Core panel rework to improve scrolling and resizing behaviour (courtesy fjk)
- Add .xlsx export option
- Disable/enable export and clear buttons depending on whether current tab supports them
- Minor tweak to prevent popup notification text fringing on light backgrounds
- Suspend window draw during resize to improve drag smoothness
- Added settings to start monitor and read all on launch
- Allow plugins to provide ApplyTheme method when registering controls for theming
- Fix some reliability issues with native voice notifications
- Reduce internal http request timeout from 100 seconds to 10 seconds (will fail faster when API is down)
- Fix issue with incorrect native voice rate range
- Clear button works now
- Should no longer attempt playback of empty notifications causing plugin to cease functioning
- Update to latest NLua package
Last edited:
Just a shower thought moment... is there any coding in core or plugins to alert you of something really anomalous - i.e. something never seen before in the journal files - by anyone, for example a biology or geology or signal source type not recognised -- let's take this to the most extreme situation I can imagine:
You jump into a system, do a honk, FSS scan, and something is recorded in the journal file utterly unlike anything else seen before... but core and plugins don't know what to do with it so it gets ignored, and it turns out it was the "Dark Wheel" sitting quietly in orbit around the 8th moon of a planet - and because of this we don't go anywhere near it to stumble upon eyeballing it.
Ridiculous hypothetical I know, but it would be good to know that if there was something really weird picked up in the journal files, we get the equivalent of Spock saying, "It's a lifeform/energy source I have never seen before!" as he did so many times in the show, lol.
You jump into a system, do a honk, FSS scan, and something is recorded in the journal file utterly unlike anything else seen before... but core and plugins don't know what to do with it so it gets ignored, and it turns out it was the "Dark Wheel" sitting quietly in orbit around the 8th moon of a planet - and because of this we don't go anywhere near it to stumble upon eyeballing it.
Ridiculous hypothetical I know, but it would be good to know that if there was something really weird picked up in the journal files, we get the equivalent of Spock saying, "It's a lifeform/energy source I have never seen before!" as he did so many times in the show, lol.
It depends on the nature of the anomalous journal entry really. Some types of "never before seen" data could produce strange output, some could cause a plugin to throw errors, some might just be silently ignored.Just a shower thought moment... is there any coding in core or plugins to alert you of something really anomalous - i.e. something never seen before in the journal files - by anyone, for example a biology or geology or signal source type not recognised -- let's take this to the most extreme situation I can imagine:
You jump into a system, do a honk, FSS scan, and something is recorded in the journal file utterly unlike anything else seen before... but core and plugins don't know what to do with it so it gets ignored, and it turns out it was the "Dark Wheel" sitting quietly in orbit around the 8th moon of a planet - and because of this we don't go anywhere near it to stumble upon eyeballing it.
Ridiculous hypothetical I know, but it would be good to know that if there was something really weird picked up in the journal files, we get the equivalent of Spock saying, "It's a lifeform/energy source I have never seen before!" as he did so many times in the show, lol.
v0.3.24200.1233 - UI Overhaul
Release versions:Bugfixes
- Update AudioHandler to ignore zero-length audio (fixes a silent failure where audio stops working for remainder of session)
- Added volume control slider to Core settings, no longer controlled per-plugin
- Fix crash on exit that was possible if Core tab was never selected during a session
Odd one. I click continue and it seems to be fine
The only thing I can see a problem with is that Start Monitor on launch didn't work, and window sizing did not honour previous set (if that's a thing yet) -- or maybe an issue is caused by ultrawide screen? Sometimes the message says '20' cannot be greater than -274 --- and sometimes different values as below
Message from second relaunch
The only thing I can see a problem with is that Start Monitor on launch didn't work, and window sizing did not honour previous set (if that's a thing yet) -- or maybe an issue is caused by ultrawide screen? Sometimes the message says '20' cannot be greater than -274 --- and sometimes different values as below
Message from second relaunch
Last edited:
Okay, I see where this "cannot be greater" error is happening. Something has crushed the height value of the splitter on the core tab down to extremely low (negative?!) values. Can probably handle that, but unusual that you could cajole the window dimensions into a size that would cause it.
What version of windows are you using? That window styling doesn't look like any version I'm familiar with.
Just vanilla windows 11 - dark mode. I don't think I have anything else odd set.
Could having resized the previous release version carry over a value that would cause that on this version? Spitballing ideas
Last edited:
AHA!!!
Figured it out, turns out the Run properties for the app had been set to "minimized" rather than "normal window" that's what caused all the problems. I'm guessing I'd set that previously for some bizarre reason for an older version. Might be something to cater for.
EDIT: Although this fixed the issue running it manually via a double click, it still happens when it launches via MinEdLauncher which I typically use for starting up ED and a couple of 3rd party tools. (its never easy right? lol)
Last edited:
Just got this:
Log says: [27/07/2024, Sat 14:43:56]:
Error in Observatory Botanist while handling ScanOrganic: The given key 'Frutexa Acus' was not present in the dictionary. - { "timestamp":"2024-07-27T13:43:34Z", "event":"ScanOrganic", "ScanType":"Analyse", "Genus":"$Codex_Ent_Shrubs_Genus_Name;", "Genus_Localised":"Frutexa", "Species":"$Codex_Ent_Shrubs_02_Name;", "Species_Localised":"Frutexa Acus", "Variant":"$Codex_Ent_Shrubs_02_G_Name;", "Variant_Localised":"Frutexa Acus - Emerald", "SystemAddress":541043707586322, "Body":25 }
Last edited:
Ah ha, that does a lot to explain it, thanks! Should be able to fix that without much trouble.
Huh, interesting. Seems like you got an "Analyse" event without Observatory seeing any previous "Sample" events that session, so there was no record of the species you were analysing for it to reference. Can gaurd against this certainly. Did you log out and back in while on the planet? There's a setting in observatory to pre-read current system context that should also prevent this if enabled.
Possibly, I'm not sure. I only installed the whole caboodle today, including the main program and plugins, and was trying out the "read all" earlier so might've logged out of the game to reset things (so I didn't have a huge list of previous bodies and biologicals). And I've been fiddling with settings, turning things on at various points like the check current system. I won't be logging out much, so if I get a similar message again I should be able to be more informative.
I'm enjoying using this immensely! Especially useful with the voice.
I could go on quite a rant about the custom rules syntax (it's not even the XML, it's how it's used...) but I'll skip that, and instead just ask for help (because I am unable to come up with the proper syntax for these things, and that's even though I'm a programmer by profession):
Could someone provide me with the syntax for getting a notification for these things:
Could someone provide me with the syntax for getting a notification for these things:
- A previously unmapped earth-like world, water world, ammonia world, or terraformable planet.
- A green gas giant (whether it has been previously discovered or not, a much more noticeable notification if it has been previously undiscovered).
- A previously undiscovered/unmapped planet/moon with locations that are not "none".
- A planetary body with a radius smaller than 350 km. (Should not notify about stellar bodies, ie. black holes and neutron stars, although I suppose there's no harm if it notifies of those too, if doing it for planetary bodies only is too cumbersome.)
- A planetary body with more than 5 biological signals.
Here's an interesting one that just happened:
I'd done the first sample of a Tussock Propagito on foot, then boarded my ship(did not launch) and got in my SRV to go the minimum distance (just over) and do a second sample.
I'd done the first sample of a Tussock Propagito on foot, then boarded my ship(did not launch) and got in my SRV to go the minimum distance (just over) and do a second sample.
If you're using XML then it very much sounds like you're using an old version of Observatory. I'd strongly suggest upgrading to current latest release of ObservatoryCore from here. It uses Lua, not XML, and is much more readable. For example, some of your requests:
Code:
::Criteria::
if (scan.TerraformState == 'Terraformable'
or scan.PlanetClass == 'Ammonia world'
or scan.PlanetClass == 'Water world'
or scan.PlanetClass == 'Earthlike body')
and scan.WasMapped == false then
return true, 'Unmapped body of interest', 'Body type: ' .. scan.PlanetClass
end
::End::
::Criteria::
if scan.PlanetClass and scan.Radius > 0 and scan.Radius < 350000 then
return true, 'Small radius body', 'Body has a radius of ' .. string.format('%.2f',scan.Radius / 1000) .. 'km'
end
::End::
::Criteria::
if biosignals > 5 then
return true, 'Multiple bio signals', 'Body has ' .. biosignals .. ' bio signals'
end
::End::You can't detect a GGG with custom criteria. You can test for known temperatures of GGGs, but it wouldn't work for the majority of cases. You can write your own plugin and handle CodexEntry events but even that isn't a guarantee if it's a GGWL or a region you al;ready saw that type of GGG. If you don't want to write your own, you can grab CodexEntries plugin from here which will announce any new Codex Entry.
You also can't do anything with Locations on a body as it's not written to the journal unfortunately.
There's documentation for Lua custom criteria here
Last edited:
That one doesn't look like Observatory at all, don't recognize any of those hierarchies. Looks like a Hud Manager issue, maybe?
Sounds like you're using the latest pre-release, in which case you should have a light theme too - check on the Core tab for Theme and select Light instead to see if it's any better. You can also create your own theme, see here for an example.