Listing Codex bugs

marx · Apr 3, 2020

So the FC beta 1 patch notes are up, and it turns out we're getting a Codex fix... one that's so small I didn't even think to include it. Namely, that some entries show wrong pictures.

Meanwhile, none of the issues above are getting fixed yet apparently. @Stephen Benedetti , most of these are reported on the issue tracker, perhaps you could forward them to the dev team, so they'd know there's more to do than the one cosmetic fix in the upcoming beta?

Shnyrik · Apr 10, 2020

I guess, I have one more to report. The Codex shows proto-Lagrange cloud in Outotz LI-O c21-0 (Sanguineous Rim region). However the cloud is not there. And it is not just a regular situation when you can relog multiple times and NSP would eventually spawn. The system has only a pair of red dwarves and no planets at all. Just no possible orbits for Lagrange cloud to spawn in. So this must be a false entry.

marx · Apr 10, 2020

Yep, that one is listed already. It always makes me wonder what happened there, whether the system changed somehow or NSP generation did. Thanks for confirming it though!

Shnyrik · Apr 10, 2020

marx said:
Yep, that one is listed already

Sorry. I searched for "Sanguineous Rim", not for the exact name of the system

By the way, speaking of this very same region. This might be actually already mentioned by the record "Metallic crystals and Solid mineral spheres not registering in the Sanguineous Rim region", but still.

There are a couple of systems right on the border with IOS: Outotz DW-W b43-0, Outopps EW-L c21-2 and Oochost PE-D b46-0. They have NSPs with metallic crystals, mineral spheres and gourd mollusks. The ingame map says those systems belong to Sanguineous Rim. Metallic crystals there really fail to register. However mollusks and spheres not fail to register in the Codex, they just register for the IOS region.

marx · Apr 10, 2020

Mm, interesting. So I guess it's a bug with the galaxy map then, it determines the region of the system wrong. (There was a thread about mapping out the region borders recently, but I can't seem to find it.) When you start to jump into them, what region does the in-cockpit message say?

Shnyrik · Apr 10, 2020

marx said:
When you start to jump into them, what region does the in-cockpit message say?

That is a good question, I even had to return to check

Yes, despite the map says "Sanguineous Rim", the message says "IOS".

Qumfur · Apr 16, 2020

Maybe I'm doing something wrong, but is it actually possible to "confirm" the supermassive black hole in Sagittarius A*, if you already went there and discovered it before the codex was a thing?
I'm currently there again but I can't get it to confirm the discovery because I can't scan it again.

marx · Apr 16, 2020

Does the Composition Scanner work on it? It probably won't, but if it does, then that'll be the way to go.
Otherwise, I think it's time for another bug report then.

Qumfur · Apr 16, 2020

Nope, tried that too. Didn't work.

Mrrshal · Apr 16, 2020

Albumin worms still reset. All dozens codex bugs are still present. This is so sad

Shnyrik · May 5, 2020

marx said:
Wrong or missing information

Well, I have some more to report

I've just checked the newly discovered Q-type anomaly in Aiphaisty YE-A d130 and it looks, the Codex gives slightly wrong information about it's traits.
The only trait says "releases destructive shockwave when approached". And it is wrong.

When approached, the anomaly drains shields slowly. When approached really close, it also starts turning the ship randomly. And none of that scans for the Codex.

And, finally, when approached with lights on, the anomaly releases the shockwave. And that shockwave heats ship up very fast. That event scans for the Codex, but gives the mentioned wrong text.

Chrismasterski · May 5, 2020

Scanning a single type of sinuous tuber returns multiple different types in the codex. For example, if you scan one prasinium tuber, it could be counted as roseum, caeruleum, albidum, or prasinium in the codex, then the next tuber in the same site would return a different type. Believe that's also the reason why albidum tubers disappear from the codex after relogging, they aren't supposed to spawn in that specific region so fdev implemented a quick fix that would prevent it from sticking.

Eahlstan · May 5, 2020

marx said:
Mm, interesting. So I guess it's a bug with the galaxy map then, it determines the region of the system wrong. (There was a thread about mapping out the region borders recently, but I can't seem to find it.) When you start to jump into them, what region does the in-cockpit message say?

Just in case you still didn't find it: https://forums.frontier.co.uk/threads/determining-the-region-of-a-system.537845/

Shnyrik · May 8, 2020

marx said:
If you find any that are missing from here...

Well, I've just recieved a strange report from cmdr. trotus, that the Codex has an entry about a terraformable ammonia world in Xibalba region in Dryeae Aec TP-G d10-9, however the only ammonia world in the system turned out to be not terraformable (do they even exist?). And the entry didn't get confirmed after scanning with FSS and DSS and stayed reported.

I looked through my Codex and found out that I myself have one confirmed entry about terraformable ammonia world in Inner Scutum-Centauris Arm in Skaudai ZZ-G b56-7. However both system map and EDSM show that ammonia world #A5 there is not terraformable.

marx · May 9, 2020

Shnyrik said:
Well, I've just recieved a strange report from cmdr. trotus, that the Codex has an entry about a terraformable ammonia world in Xibalba region in Dryeae Aec TP-G d10-9, however the only ammonia world in the system turned out to be not terraformable (do they even exist?).

Nope, they don't exist. It's another of the Codex's weird quirks. I forgot to add it though, so thanks!

marx · Jun 10, 2020

So the patch notes listed that there were some partial fixes to stuff not registering in the Codex, which might or might not show up for players. Because of this, I didn't remove the entries that were fixed, but struck them out instead (~~like this~~), so that people can check if it's fixed on their end too or not.
On my end, it looked like there were four entries fixed.

Shnyrik · Jun 18, 2020

I guess, I have one more to report. The Codex mentions proto-lagrange cloud in Hypao Broae RO-Z d13-2, which is supposed to be the only system with PLC (and thus some NSP life) in The Trojan Belt region. However, the cloud is not there, Codex entry appears to be wrong.

MaultierColt308 · Jun 19, 2020

I recently tested some Fumarole/Gas Vent Combo sites in the Sanguineous Rim region (Messier 67, to be exact), as those tend to be bugged in previously visited regions.

Silica Vapour Fumaroles and Gas Vents both scanned and registered properly.
Sulphur Dioxide Gas Vents couldn't be scanned. Fumaroles scanned and registered properly.

Mrrshal · Jun 19, 2020

MaultierColt308 said:
I recently tested some Fumarole/Gas Vent Combo sites in the Sanguineous Rim region (Messier 67, to be exact), as those tend to be bugged in previously visited regions.

Silica Vapour Fumaroles and Gas Vents both scanned and registered properly.
Sulphur Dioxide Gas Vents couldn't be scanned. Fumaroles scanned and registered properly.

But does Codex Entry persist after relog?

MaultierColt308 · Jun 19, 2020

Mrrshal said:
But does Codex Entry persist after relog?

Yes, it does

at least for Silica Vapour, for Sulphur Dioxide, they're still not scanning after relog.