MattG's Observatory plugins
- Thread starter MattG
- Start date
Go to CORE, BioInsights, "show legend" down the bottom, the crosses mean it's possible according to the requirements of the bio but not actually present on the body.
Thanks , for some reason i didn't have it so thought it was an add on =-)
That fixed it, silly me!
Since I can't attach anything to PM's, here you go:
After I scan the planets in the system when I first enter it:
After I land on the planet and sample each one it adds it:
After I scan the planets in the system when I first enter it:
After I land on the planet and sample each one it adds it:
Journals have been uploaded.
For info - Program Files has special properties and permissions. You run an auto-update service. If the web service you run it from is ever hacked and malicious code is injected into the download, the system has a far better chance of detecting and causing any exploits to fail if it is in Program Files than another folder the user has full permissions on, providing you use the built-in security that comes with the OS (and don't turn it off for convenience!)
That's one of the major problems with inserting non-bypassable security systems on consumer devices, because 99% of the time that's exactly what happens.
I just don't get how it has always worked perfectly on my system, which has always been on Windows 11, until update 14. It hasn't worked since. (bio insights, that is.)
Everything else works as it always has.
Everything else works as it always has.
Strange indeed, any windows updates since? Also remember that BI is doing some stuff other plugins aren't, like marking new codex bio's and etc, so it's keeping those stored in a database and they need to be accessed each time you scan a system and that database is updated as you scan bio's, whereas explorer for instance is just comparing planet data to an existing set in the program itself. Question, did it stop working exactly when update 14 was installed or when OBS was updated to .net6, because when update 14 was released the OBS main program was updated to support new journal features. So did it happen with the OBS update or the 14 update?
Actually here's something you could try, can you drop right back to the previous .net5 version of OBS and BI and see if they still work? Because if they do then it would indicate it's something to do with the OBS update and not the 14 update for ED.
Nothing has updated but the game and the app and only one part of that app isn't working, so it's either something the game did or something in that one part of the app.
Could you please open regedit, navigate to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders and screenshot it, also HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\Personal if it exists.
Nah. Not going to butcher my system over one part of one app when everything else runs perfectly on it. I'll just use EDD for that instead.
That doesn't butcher anything, it would just help rule something out. But it's your decision...
Yes the APP, a new version of Obs to .net6, and the plugins have all been updated to .net6, and also BI has changed and now does stuff that previously was done by CodexCompanion so you don't need run that when running Obs, it runs fine on everyone else's PC. I don't know if anyone else is running Win 11, but it would be useful to work it out before large numbers of people start changing OS and start having problems.
Lazy programming - or developers that don't want to pay to get it done properly are the problem, not the OS design. Quality enthusiasts like MattG I'll happily help out to get it done properly.
I looked at this and as far as I can tell it should've flagged - it's fairly simple requirements and they all look to be met. It is another that is determined by star type though, I wonder if you've possibly visited this system in the past which stopped the Scan event for the star on this visit?
Again you are correct, after checking my logs it seems I visited this system in 2017, what a coincidence, I will have to make a check each time I get a "not predicted" message if this keep happening...lol, nearly exactly 6 years ago, 14/1/2017!