Tissue sampling actually matters to the Thargoid war effort now.
So any word on when this bug will get fixed? @sallymorganmoore? @Bruce G?
tl;dr Research limpets are meant to work 100% of the time. They don't.
The last report about this was marked as fixed, but no note of a fix in patch notes, and no effect in-game; success rates still vary greatly.
The bug means successful sampling can vary anywhere between virtually nothing up to almost guaranteed success. The most consistent variable is simply who does it; the rest-point of success rate varies greatly based on the individual doing it... the only other time I've seen this sort of behaviour occur is with old-style USS generation, which seemed to be a lag/latency issue.
But Jmanis! Surely if it's been around this long it's intended behaviour!
- Two CGs have now been cancelled as a direct result of this bug, the first five years ago, and the most recent just last year. I cannot think of a reason FD would cancel two CGs, citing this bug as the cause [1] [2], if it were intended gameplay mechanics.
- There's a resolution state of "by design" which was not used for this bugreport. If it was marked "by design" that would be the end of this, regardless of what transpired in the past. But it's marked as "fixed"... when there's plenty of current observations that it's definitely not 100%.
If it's genuinely by-design not meant to be 100%, then so be it, but it needs to be made clear because all other actions suggest this is very much not by-design.
So any word on when this bug will get fixed? @sallymorganmoore? @Bruce G?
tl;dr Research limpets are meant to work 100% of the time. They don't.
The last report about this was marked as fixed, but no note of a fix in patch notes, and no effect in-game; success rates still vary greatly.
The bug means successful sampling can vary anywhere between virtually nothing up to almost guaranteed success. The most consistent variable is simply who does it; the rest-point of success rate varies greatly based on the individual doing it... the only other time I've seen this sort of behaviour occur is with old-style USS generation, which seemed to be a lag/latency issue.
But Jmanis! Surely if it's been around this long it's intended behaviour!
- Two CGs have now been cancelled as a direct result of this bug, the first five years ago, and the most recent just last year. I cannot think of a reason FD would cancel two CGs, citing this bug as the cause [1] [2], if it were intended gameplay mechanics.
- There's a resolution state of "by design" which was not used for this bugreport. If it was marked "by design" that would be the end of this, regardless of what transpired in the past. But it's marked as "fixed"... when there's plenty of current observations that it's definitely not 100%.
If it's genuinely by-design not meant to be 100%, then so be it, but it needs to be made clear because all other actions suggest this is very much not by-design.
Last edited: