There is mass reports of Commanders losing their Claimed Systems.
- Thread starter Einar Donarsson
- Start date
And If the problem only becomes apparent under live conditions?
Some of the problems are in that category, sure. Can't legislate for those and that's what you expect in a live beta, indeed. (Note "beta" does not imply "live beta" but on the other hand as a friendly mod reminded me, FDev have said what they meant by "beta," in the official Trailblazer announcement, so we can't really complain.)
However, the defect, for example, where two Cmdrs make a claim near-simultaneously in two different instances, with hilarious results, is something you should test in an assembly/pre-release/pre-prod/alpha environment or environments; you don't need real end customers testing that one out. You only need two test Cmdrs and two instances for that and I would think there's even a test harness to simulate that traffic, so you don't even need two PCs with GPUs to run the actual client.
Noticed in the right upper box when I jumped in to the area of my installation I get a System Link Error ; Security Response Not Available.
Was fine all day now as maybe 10 min ago its not showing me as architect again. I'm one load away from finishing my Agricultural installation
Have a Relay Installation in place I was gonna start bringing resources to after the Agricultural installation was finished.
Tried reloading didn't help.
Was fine all day now as maybe 10 min ago its not showing me as architect again. I'm one load away from finishing my Agricultural installation
Have a Relay Installation in place I was gonna start bringing resources to after the Agricultural installation was finished.
Tried reloading didn't help.
There's a patch tomorrow morning. Look at the announcements forum.
Problems can be found in a live production system after having done testing in a beta environment, but at least then you can still say that you gave it an honest attempt to find the problems in an isolated beta test before throwing the new system into the wild. But here they're just being reckless by prematurely pushing the content to live, and then as a footnote they said the magic B-word that somehow makes being irresponsible ok.
They mentioned the magic B-word pretty much everywhere, it doesn't help you making your point.
His point was that a vendor needs to behave like it's a beta, not just call it a beta. The magic b-word is not actually magic, it does not compensate for skipping earlier phases of testing.
How do you know they skipped earlier phases of testing ? everything was fine until reports of cheating started appearing on the issue tracker and Fdev shut down colonisation straight away.
The in house testers probably don't know all of the exploits, they know of one now.
He said they only mentioned it in a footnote and I said that this claim doesn't help him making his point because it's made up. You don't need to tell me what his point was, I already knew that. If someone has a point he doesn't need to imagine random things, that was my point.
The one person in this thread with reading comprehension.
Everything was not fine. I even gave an example of the exact bug I was talking about