I dont know if this is intended behaviour but the scroll bar is only like 5 pixels wide on startup, it expands to full width if you put the mouse there but as soon as you do something else the bar goes back to ultrathin. You never know if the list is actually at the bottom if you cant see the scroll bar. Please change that.
As with bangermsuk's issue, if you can supply your logs then I can probably track down exactly what's happening. If not then it will probably take a while to resolve.
I dont know if this is intended behaviour but the scroll bar is only like 5 pixels wide on startup, it expands to full width if you put the mouse there but as soon as you do something else the bar goes back to ultrathin. You never know if the list is actually at the bottom if you cant see the scroll bar. Please change that.
I am having a really strange issue with Observatory Core - it shutdown itself during play and am unable to find why.
I play in VR, start EDDiscovery and Observatory before ED and after few minutes in game if i remove my HMD i can see that Observatory is closed.
Is there a debug mode/log which i can review to see what is happening?
Not sure if this is the right place for feature requests, but is it possible to configure Elite Observatory to also include simple terraformables that are not landable? I haven't tinkered with a custom file yet, but I think that's the only way to accomplish this. Or am I missing something?
That sounds pretty easy for a custom criteria, however MattG's plugin evaluator will list terraformables in its output but not put up a notification. It depends whether you want it to be a visible notification or just a list you can check after scanning the system.
I have found if there is a distant Ammonia world, the app will crash midway through announcing it... e.g. "Body C1..." how would I troubleshoot this?
I have a custom criteria to alert me to these - just as I have for distant earthlikes etc., but for some reason Ammonia worlds crash it.
NVM, found out what was wrong.
The Bioinsights came with their own deps folder, containing CodexLib.dll. I had to copy this dll into the main deps folder and now it works. Possibly a small installation bug?
Not sure if this is the right place for feature requests, but is it possible to configure Elite Observatory to also include simple terraformables that are not landable? I haven't tinkered with a custom file yet, but I think that's the only way to accomplish this. Or am I missing something?
I have found if there is a distant Ammonia world, the app will crash midway through announcing it... e.g. "Body C1..." how would I troubleshoot this?
I have a custom criteria to alert me to these - just as I have for distant earthlikes etc., but for some reason Ammonia worlds crash it.
I was trying to see how many planets with three rings I have discovered, using the new Observatory Core thingy.
I thought, I'd start simple and just see all rings I'd found, using a modification of criteria from post #1216 of this thread. My attempt resulted in uncontrollable cascade of plugin errors.
This is OC installed with the .exe installer:
and this comes using the .zip version:
There's obviously something very wrong in my custom criteria...
Here's the content of my ObservatoryCriteria.lua in its entirety:
Code:
::Criteria::
if scan.Rings then
for ring in rings(scan.Rings) do
return ring.name
end
end
::End::
I was trying to see how many planets with three rings I have discovered, using the new Observatory Core thingy.
I thought, I'd start simple and just see all rings I'd found, using a modification of criteria from post #1216 of this thread. My attempt resulted in uncontrollable cascade of plugin errors.
This is expected, since you're processing at the planetary scan level and there aren't individual events per-ring it will return results upon seeing the first ring and return. Using the rings iterator doesn't change that.
If you want to report on additional rings you'd need multiple criteria, one per each level of ring you want reported. Something like this (untested, may not work):
Code:
::Criteria::
if scan.Rings then
-- There is always an A ring if there are any rings
return true, "A Ring found", scan.Rings[0].Name
end
::End::
::Criteria::
if scan.Rings then
if scan.Rings.Count == 2 then
return true, "B Ring found", scan.Rings[1].Name
end
end
::End::
-- And so on...
Didn't plan on making a release today, but Frontier changed their journal file naming convention, which stops Observatory from working. Very little testing was done, in the interest of getting this...
github.com
Didn't plan on making a release today, but Frontier changed their journal file naming convention, which stops Observatory from working. Very little testing was done, in the interest of getting this out rapidly.
Observatory will now read alpha and beta jounals as well. If this is an issue then delete or move them to a different folder.
Find the following hodge-podge of fixes in this release:
Handle Odyssey Update 11 journal files
Under-the-hood overhaul of journal monitoring status
Default journal location on linux to path used by Valve's Proton compatibility layer
After both updates (the game and the Observatory) I do get my notifications (so the files are read properly) but they arrive with a delay. I get them either on the next body that triggers the notification or on exit from FSS. Like the game adds a delay while updating journal files?
An example:
Body 4 notification arrived when I scanned body 8 a.
Body 8 a notification arrived when I finished scanning the system and closed FSS.
After both updates (the game and the Observatory) I do get my notifications (so the files are read properly) but they arrive with a delay. I get them either on the next body that triggers the notification or on exit from FSS. Like the game adds a delay while updating journal files?
Depending on how quickly you grabbed the new version you may have missed the updated release that corrects exactly that issue. Do you have version 0.2.74.1551?