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
Rather than trimming visibility on the history tab try reducing what's loaded via the 'Memory' box on the Settings panel.
Journals on HDD might make contention a bit worse compared to SSD but we should still be talking about tenths of a second at worst. It is, as you say, weird.
I've already got it set to >7 days.
It's weird, it's not the fact that the app is just slow reading the journals, it's slow as if it's using 100% CPU all the time and isn't responding to standard UI requests (such as moving the window, clicking elements on the UI etc).
It's weird, it's not the fact that the app is just slow reading the journals, it's slow as if it's using 100% CPU all the time and isn't responding to standard UI requests (such as moving the window, clicking elements on the UI etc).
That's very strange. I'm definitely not doing anything that should have an impact on another application's UI thread. I'll keep an eye open for any weirdness while I'm using it myself, but currently have no idea at all what might be causing it.
And with that word I realised who you are.
That information is not contained in the scan event, sorry.
Got fixes for changing the default sort causing duplicate fsd boost mat and "uninteresting" items. Should also improve performance of "read all logs" slightly. Will degrade performance of event processing during monitoring with a worse degradation the more items are currently in the list, but I haven't heard any reports of it being anything other than "instant" thus far, so I'm not too worried.
Not going to release a build yet as I've done zero testing, on account of being fully engrossed in The Outer Worlds this weekend. Expect it early this week.
Not going to release a build yet as I've done zero testing, on account of being fully engrossed in The Outer Worlds this weekend.
Expect it early this week.We've been asking for it from the word go, with the current length of the process to give us the counts I'm not sure it's workable without a separate journal event (which would be good) or reworking how that process works (give us a pair of boolean flags immediately and leave the calculation of number and location of sites running in the background until we map, for example).
I do not believe for an instant that performance has anything to do with what does and does not make it into the journal, or that it would even have any kind of performance impact in the first place.
Could you maybe add a "Hide Uninteresting" setting for those of us who don't want to see them ?
Pretty please ?
Pretty please ?
They should remove themselves as soon as you scan anything else. I added them so that you can be sure Observatory is still working if you haven't found anything interesting in a while. If you're seeing more than just your last scanned object then it's because of the sorting issues, which will be fixed soon.
If that's still not acceptable then I'll see about adding a setting.
If that's still not acceptable then I'll see about adding a setting.
Ah ok, I had about 100 of them yesterday If they remove themselves then that's fine. Will it go back to the original design where there was only ever 1 Uninteresting line, and it was just replaced each time ?
If they remove themselves then that's fine. Will it go back to the original design where there was only ever 1 Uninteresting line, and it was just replaced each time ?Bugfixing and a surprise new feature!
New settings for automatically reading logs and starting monitoring when launching Elite Observatory have been added courtesy of iain666. A welcome change, and I'd like to thank him for being my very first contributor!
A few bugfixes bundled in here as well. The following issues have been hopefully addressed:
New settings for automatically reading logs and starting monitoring when launching Elite Observatory have been added courtesy of iain666. A welcome change, and I'd like to thank him for being my very first contributor!
A few bugfixes bundled in here as well. The following issues have been hopefully addressed:
- Duplicate entries appearing when monitoring after list has been sorted.
- "Read All Logs" skipping items that have been recently scanned if monitoring found some objects before reading all logs was started.
- Text-To-Speech incorrectly prefixing "body" for "all boost materials in system" event, which is not body specific
- Log monitoring spamming user with several simultaneous announcements of previous found objects if continuing to monitor after clearing list of other items found in the current session.
- Monitoring state desync with text of start/stop monitoring button, and failing to correctly resume if started before reading all logs.
A welcome change, and I'd like to thank him for being my very first contributor!
Never been one to make a feature request if I can just implement it myself, the joy of open source
Assuming this release settles in as being largely bug-free (or at least doesn't contain anything particularly egregious), the next thing I want to work on is custom criteria. Primarily I'm interested in adding:
- Logical operators (AND/OR/NOT(/XOR?))
- Access to properties of parent/child bodies so that custom criteria can be driven by relationships between objects in the same way that some of the built in checks are
- A way to grab a single value without needing to multiply by 1 or add zero or whatever
- Add a "between" criteria so people don't have to do things like this.
Ooohhh, I like this! Gives me a nostalgic, warm and great feeling for the future of this tool - on top of the good feeling I already had about it
@Vithigar: Do you prefer to get feature requests in this thread or as an issue over at Github?
Personally I'm fine either way, though looking back over the thread earlier I noticed a request I had forgotten about, and I have already forgotten what it was again now, so GitHub might be the safer bet for record keeping purposes.
