Need help. A filter is required by the name of systems with coordinates greater than + 3k or -3k.
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
Exactly, it's like you say,
Versions that were downloaded and that I have used without problems, now Bitdefender sends them to quarantine.
if I try to download them again it intercepts them directly.
View attachment 170209
View attachment 170208
I have tried them and the first one that does not consider Bitdefender ant it is the one with the Update link,
View attachment 170210
this version I can download and run it
it's maddening, it bothers me because I love this tool
If I can find out the reason, or find a solution, I communicate it in the thread
I have submitted the most recent observatory exe to bitdefender in a false positive report. Maybe that will sort it out.
I'm not really sure what you're asking. If you mean the system x,y,z location within the galaxy being outside a particular bound that's not a piece of information Observatory currently can check.
BAG
I visited
Regardless of whether you're looking for realtime monitoring or scanning your old logs, it's simply not data that Observatory currently reads since it's not part of the body-specific scan event.
I can look into adding it in a future version though.
Do not worry, I just hoped that I could find the old data. It’s just that I deleted all the tags and searched manually by sectors for a very long time. I didn’t even get the name to speed up the process.
Using Notepad++'s "Find in files" function (or something similar) you should be able to find them with this regex:
StarPos":\[-?\d*\.?\d*,-?[3456789]\d{3}\.edit: Assuming you're asking for 3000Ly above or below the galactic plane.
Last edited:
resolved issue,I have submitted the most recent observatory exe to bitdefender in a false positive report. Maybe that will sort it out.
I tried to report it to Bitdefender but I couldn't find how
thank you very much
Great tool, I've been using for some days. Few suggestions (are really simple modifications) that would greatly improve the quality of life (at least for Console players):
Thank you!
- Could you add an option to automatically reperform the "retrieve logs" action? Maybe every 10 - 30 seconds (or let the user specify the time)
- Once the logs are retrieved, it asks via a dialog if the already present logs have to be re-retrieved. Could be disabled this popup?
- The second time you click the "read all logs" it reminds that the currently displayed log list will be cleared. Could be disabled this option?
Thank you!
Why would you want to perform 1 every 20-30 seconds?
Because I don't know how often are the journal updated server-side for console users. I don't know if they are available at once when a user visits a new system. A higher update rate should avoid the user to be leaving the system without getting the updated info in time.
However, it could be defined even as 60 seconds... The important thing is that it could be automatically done
P.S.
It could be useful to have a visual feedback (a timer) that let the user know how much misses for the next automatic update
Hey, thanks for this! I've gotten very little feedback from console users, so this is some valuable insight.
An auto-refresh is certainly possible, though it would make sense to limit it to only the current day's log. The only real reason it wasn't implemented right from the beginning is that I don't really know what the refresh cycle of the log availability from Frontier's API is. There's not really any point in doing it if it only ever updates when you log out from the game, for example. If you can give me some idea what the window for that it like than I certainly don't mind implementing something.
As for asking if you want to re-retrieve, yes, I can add an option to disable that. There are some edge cases where you might want to, but for a normal use-case you're correct that it's probably not necessary.
I can probably disable the warning about clearing the window when reading all logs for users with cAPI enabled as well, since that's the only way they can update the displayed items.
Thanks again for the feedback!
What I do is:
- If the system is already known: I usually refresh Elite Observatory after I've performed the "honk". The process is the following: It usually takes me 50 seconds to travel from a system to another (fuel scoop, FSD charge, jump animation) and 10 - 15 second for the "honk" (this operation could be overlapped the fuel scoop process, but for simplicity let's assume it is performed before that process).
- If it is not known: is like the previous, but after the fuel scoop, I perform the discovery via the FSS and then refresh Elite Observatory
Regarding the other 2 points (the dialog showing), the options to not show them will save me a lot of time
Thank you!
Deleted member 38366
D
Lots of pages, so I just wanted to re-check : has there been any Update to show Green Gas Giants yet?
Interesting, so the data is available pretty quickly. Certainly sooner than some suggestions I saw elsewhere.What I do is:
And usually, I always get the info by Elite Observatory updated in time before leaving the system. So, I think that a good minim refresh value could be 70 seconds ( I don't know if the API has a sort of limit per request in time). The important however would be to give visual feedback (a timer, progress bar ... ) to the user to let him allow when the next refresh will happen in order to organize the jump
- If the system is already known: I usually refresh Elite Observatory after I've performed the "honk". The process is the following: It usually takes me 50 seconds to travel from a system to another (fuel scoop, FSD charge, jump animation) and 10 - 15 second for the "honk" (this operation could be overlapped the fuel scoop process, but for simplicity let's assume it is performed before that process).
- If it is not known: is like the previous, but after the fuel scoop, I perform the discovery via the FSS and then refresh Elite Observatory
Regarding the other 2 points (the dialog showing), the options to not show them will save me a lot of time
Thank you!
Visual feedback shouldn't be a problem. I don't have an ETA for when these changes will be available, but they've definitely been noted, thanks!
No, there has not. Until someone figures out a way to determine if a planet is a green giant from the scan event journal data it won't be possible.
This sounded interesting, another explorer told me about this so i could track shepard moons i may of come across.
Trying to check my data however causes problems.
Error occurs, interesting system , actually its two systems share the same name.
Cocoon nebula, has the system ,, also 120 lyrs or so eastward another 2Mass system.
2Mass have had a few problems i've come across with duplicate system name but different systems.
Edsm has problems, it does list both systems with different coords but does not have the correct system data.
i'm wondering if this is also causing a problem with Observatory.
2MASS J21532669+4714025
Odd also that both of the systems were not visited by myself, although i have been to the main one before. long ago
Jumped out there just earlier to check on both systems for oddities.
The Green gas giants, well they do have a seperate codex entry i guess, so might be findable by the codex composition scan reference rather than the gas giant API data?
Trying to check my data however causes problems.
Error occurs, interesting system , actually its two systems share the same name.
Cocoon nebula, has the system ,, also 120 lyrs or so eastward another 2Mass system.
2Mass have had a few problems i've come across with duplicate system name but different systems.
Edsm has problems, it does list both systems with different coords but does not have the correct system data.
i'm wondering if this is also causing a problem with Observatory.
2MASS J21532669+4714025
Odd also that both of the systems were not visited by myself, although i have been to the main one before. long ago
Jumped out there just earlier to check on both systems for oddities.
The Green gas giants, well they do have a seperate codex entry i guess, so might be findable by the codex composition scan reference rather than the gas giant API data?
Last edited:
The rotation period of "inf" is what's causing the problem in that screenshot. I actually thought I'd already filtered out all the logs that were old enough to cause this sort of issue but I guess that one snuck through. I've got a couple of other minor issues starting to stack up so I'll see about doing another minor bug fix soon.
As a work around you can move logs for the dates that show up in that error out of your journal folder or rename them so that they won't be processed.
As for green gas giants, yes, they have a codex entry, but that's not really useful since it will only ever pop once per region. You can look up where your GGG codex entry came from with the in game codex already, and it doesn't help with scanning your logs for any that you may have found prior to the codex being a thing.
thank you very much for the fantastic tool,
I've been resting for a period of time separated from exploration, but will be back after the FCs are released
I would like to use it with the FCs to facilitate the mining of Tritium:
Is it possible to configure the current version for this task?
I've been resting for a period of time separated from exploration, but will be back after the FCs are released
I would like to use it with the FCs to facilitate the mining of Tritium:
- some kind of warning on gas giants with rings that are candidates for Tritium
- confirmation of the presence of Tritium in the ring (after surface scan)
- Other interesting deposits: Voids Opals and LT Diamonds
Is it possible to configure the current version for this task?
That information is not available in the logs. If that changes then I can certainly add it, but it's out of my hands until then.