I have never seen that. I have entered many systems that are undiscovered and it listed everything out to the last body. Usually, after the honk of course. It will not give any info, just that there is a body unexplored at say 250kLS out. If it doesn't work, it has never been an issue for me.
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
That means that you have not explored the body. Someone else has, and has sold the data.
FSS, and System Map if you don't use FSS will tell you who was the body discovered by.
So no other CMDR was listed as "First discovered by..." in the system map after your proximity scan, and you got the tags after turning in your exploration data? To be frank I don't believe that is the case.
True, shows me. I am not going to argue about it. I could be wrong, just that it has never been a problem. Even the systems I entered that I discovered populated the left panel and I flew out to everything on the list. I may have not noticed stuff missing, or popping when I was flying... just that I have never entered any system that showed NOTHING in the left panel, and yes, even newly discovered ones. Whatever, no worries.
If you're happy with it then you do you.
That doesn't happen, I can assure you. Systems out here where I am that haven't been visited previously show only the stars and asteroid belts even if the honk says 50 or more signals. It doesn't appear like you have ever been to a really newly discovered system, if you are anywhere near the bubble most will show planets in the panel, I will post screenshots for my next new system.
Screenshots, first is a system already discovered by someone else that I have never visited myself;
As you can see, all bodies listed in the left panel as unknown, just as you see, when I click on a body in the system map it shows me the details and the name of the original discoverer.
Completely unexplored system, me the first visitor;
6 bodies listed in the honk, none showing in the panel except the star. Sometimes you will see close planets if they are within auto-discover range, but in this case none, and nothing showing in the system map;
Now you are indeed free to explore as you want, and I am not going to object if you continue to do so, but just keep in mind my discovery of KOI 1701 1 would not have happened exploring the way you do, it was only by using the FSS that I found that body, and that would have been a great pity. The FSS is really important because without it you could miss that big discovery!
Wow, I appreciate all the info and attention you all put to this. I understand that you would want me to be properly informed and equipped. The issue is, I still dislike the FSS and the way it functions. Unless it is completely necessary for a specific task, I will probably never use it. It breaks immersion for me.
Thanks again all for the help!
Thanks again all for the help!
You're welcome, as long as you are aware of the pluses and minuses.
LMAO, well, if and when I can get up, walk to another station, activate the FSS and operate it like he is, I will be sure to check out what I might be missing...
[Parallax dot-hunting intensifies...]
I missed this when I initially read your message. I am actually planning to add a version check as well.
Barycentres, buttons, and waiting your turn
github.com
Please note that this is a partially breaking change for plugins, so old versions of plugins may cause issues.
I've been pretty busy lately, so it's quite likely this list is complete or I've missed adding a fix or feature entirely, but here we go.
As before, two versions are supplied. ObservatorySetup.exe for the installed version, ObservatoryCore.zip for the larger but more portable standalone. This time I managed to build them close enough together for them to have the same version number.
The headline feature for this release for most users is probably support for the new ScanBaryCentre event, which will allow binary bodies to finally trigger several checks that they slipped through before, such as close orbit and shepherd moon. They are also available to custom criteria as normal scans, no changes to existing criteria should be necessary if a barycentre also qualifies for them.
Another big one for many people is voice notifications now waiting their turn to talk, rather than all yelling at once. In addition the Explorer plugin now supports the use of SSML for speech, as described in the next paragraph, and should finally stop talking about "body 3 grams".
This release also starts a pretty major rework of how notifications are handled internally, with the largest improvements being the ability for plugins to specify where and for how long a notification persists, as well as adding the ability to use SSML to tell the speech synthesis exactly how to pronounce a given string. Originally planned for this release, but pushed back to later, is functionality to allow plugins to update or dismiss an existing notification.
The Core tab sees a minor visual change in this release. It was not intentional and is simply a result of some default dark theme changes between AvaloniaUI 0.10.6 and 0.10.7. Let me know if you hate it and I'll see about tweaking it back to the old look.
Finally the last change I want to call out here is the addition of a new button in the Core tab to open the plugin folder. Several people asked for this one, and it was a pretty easy addition, so enjoy!
Release Barycentres, buttons, and waiting your turn · Xjph/ObservatoryCore
Please note that this is a partially breaking change for plugins, so old versions of plugins may cause issues. I've been pretty busy lately, so it's quite likely this list is complete or I've misse...
github.com
Please note that this is a partially breaking change for plugins, so old versions of plugins may cause issues.
I've been pretty busy lately, so it's quite likely this list is complete or I've missed adding a fix or feature entirely, but here we go.
As before, two versions are supplied. ObservatorySetup.exe for the installed version, ObservatoryCore.zip for the larger but more portable standalone. This time I managed to build them close enough together for them to have the same version number.
The headline feature for this release for most users is probably support for the new ScanBaryCentre event, which will allow binary bodies to finally trigger several checks that they slipped through before, such as close orbit and shepherd moon. They are also available to custom criteria as normal scans, no changes to existing criteria should be necessary if a barycentre also qualifies for them.
Another big one for many people is voice notifications now waiting their turn to talk, rather than all yelling at once. In addition the Explorer plugin now supports the use of SSML for speech, as described in the next paragraph, and should finally stop talking about "body 3 grams".
This release also starts a pretty major rework of how notifications are handled internally, with the largest improvements being the ability for plugins to specify where and for how long a notification persists, as well as adding the ability to use SSML to tell the speech synthesis exactly how to pronounce a given string. Originally planned for this release, but pushed back to later, is functionality to allow plugins to update or dismiss an existing notification.
The Core tab sees a minor visual change in this release. It was not intentional and is simply a result of some default dark theme changes between AvaloniaUI 0.10.6 and 0.10.7. Let me know if you hate it and I'll see about tweaking it back to the old look.
Finally the last change I want to call out here is the addition of a new button in the Core tab to open the plugin folder. Several people asked for this one, and it was a pretty easy addition, so enjoy!
- Barycentre support added
- Voice notifications now queue instead of all playing at once
- Improvements to control of notifications by plugins
- Plugins can now optionally specify location and duration on a per-notification basis
- Added ability for plugins to use SSML to better control voice notifications #16
- Fix for plugin string type settings not appearing or saving correctly
- All text field settings (currently string and FileInfo) will now save content when manually edited
- Added button to open plugin folder #19
- Updated to AvaloniaUI 0.10.7
Last edited:
still crashing but MattG has released new versions so I will download those now and see what happens, if it still crashes after that will pull the error report.
Pleased to report after updating MattG's plugins all working fine now!
Well... it's not wrong.
Except for the fact that it very much is. Will get that into a quick bugfix release before next weekend.