Failure Developments at it again

Easy - all it takes to stop this stuff happening is someone whose job it is to say - “No. you cannot release this code until it works.”

And don’t tell me testing didn’t reveal all these huge, obvious and in your face from the get go bugs. If they were missed then it wasn’t tested in any meaningful sense of the term.

It’s been standard practice for any games I’ve tested for developers to simply ignore even the most serious of reported and confirmed problems and then act all surprised when the release goes pear-shaped.
Unless the bugs weren't present in the RC. 🤷‍♂️
 
Software engineers know however much you test, its impossible to catch all the bugs. You can't afford the number of testers to do it. When Elite user community is a x1000 (you guess the right number) more than the testers they have available, then you know users will find the bugs you've missed.

That's not excusing the blindingly obv ones, of course. But what is blindingly obv to you may not be to the testers.

I feel for them.
 
Dead behind the eyes, emotionless, don't give a cr*p etc..
I can see the similarities

On a separate note do all you dev. types take a vow to defend each other no matter what? "All for one, and one for all" type stuff.
I am a builder type and if a house fell down I don't think I would be saying "well you don't understand bricks and mortar me ole mate!"
 
Last edited:
While this situation is indeed annoying, especially because it's likely to continue for the weekend, I quite believe in a few weeks this will already be forgotten and there's no need to close the game, demolish FD's offices and chase the devs with pitchforks...

That being said, maybe it's high time for FD to finally get a QA department... Or if they do (which by now I find hard to believe), then it's time to re-evaluate the pre-release QA process because after so many botched updates, it clearly isn't working and makes for a terrible impression especially for new players.
 
Software engineers know however much you test, its impossible to catch all the bugs. You can't afford the number of testers to do it. When Elite user community is a x1000 (you guess the right number) more than the testers they have available, then you know users will find the bugs you've missed.

That's not excusing the blindingly obv ones, of course. But what is blindingly obv to you may not be to the testers.

I feel for them.
And that's why you do (or should do) a public betatest. Thousands of players, eager to test, not asking a single penny for it, at your fingertips. And the final build should be the same as the last beta build that is at last working, and not get more again untested changes.
 
And that's why you do (or should do) a public betatest. Thousands of players, eager to test, not asking a single penny for it, at your fingertips. And the final build should be the same as the last beta build that is at last working, and not get more again untested changes.
That would work if FD acted on Beta testers findings rather than treating it as an 'exclusive pre-release build' for the hype train. The number of bugs that went to the live releases after numerous reporting of bugs on previous private and open Beta's, makes it look like a solid (or as near as) release was not the main concern: Hype it up; rush it out.
 
And that's why you do (or should do) a public betatest. Thousands of players, eager to test, not asking a single penny for it, at your fingertips. And the final build should be the same as the last beta build that is at last working, and not get more again untested changes.
I don't disagree, but if the majority of bugs are caused by the patching process or the live servers no amount of beta testing would help.
 
Software engineers know however much you test, its impossible to catch all the bugs. You can't afford the number of testers to do it. When Elite user community is a x1000 (you guess the right number) more than the testers they have available, then you know users will find the bugs you've missed.

That's not excusing the blindingly obv ones, of course. But what is blindingly obv to you may not be to the testers.

I feel for them.
Which is why you should have an open beta before you release an update. There's quite a large number of players, myself included, willing to spend some time in release candidates in the hopes of stumbling upon the game breaking bugs. We know that bad bugs will appear once an update is released into the wild. Better to find them during a beta where there's no risk of losing progress, as opposed to in the live game.

I'd rather spend two weeks messing around in the beta,
trying stuff I'd never do normally, than spend two weeks not playing the game at all, because I can't log into the game, or the game's too unstable to play in VR comfortably. Granted, I'm making good progress on advancing my Martian colony, but I'd been hoping to advance my main a little closer to civilization!
 
I chose a real bad time to get back into this game!

There's always been issues with updates in my experience though this one in particular seems to have affected more than the usual.

Hopefully up and running properly soon.

o7
Still watching from the sideline, not getting back until I get some gameplay updates. I pop in and look around and then naag! back to Arma3
 
That's an interesting statement! I had always thought that 'dead' was an end state. So assuming that to be true I'd really like to find out from you, how something could be "even more dead" than Dead ?

Seems a little wierd as a statement.
With the indifference, incompetence and avarice Frontier demonstrated in this patch, i have complete confidence in them being able to reach yet new levels of dead.
 
Which is why you should have an open beta before you release an update. There's quite a large number of players, myself included, willing to spend some time in release candidates in the hopes of stumbling upon the game breaking bugs. We know that bad bugs will appear once an update is released into the wild. Better to find them during a beta where there's no risk of losing progress, as opposed to in the live game.

I'd rather spend two weeks messing around in the beta,
trying stuff I'd never do normally, than spend two weeks not playing the game at all, because I can't log into the game, or the game's too unstable to play in VR comfortably. Granted, I'm making good progress on advancing my Martian colony, but I'd been hoping to advance my main a little closer to civilization!
^^ This and open beta should be pushed to pc and consoles!
 
I mean, the moving arrow is a nice thing, but only if it shows the direction of your thrust, otherwise it's a totally useless gimmick with no positive effect.
Of course that is waaaaaaaaaaaay down the list of things to fix and I'm not entirely sure if I did right (I reversed thrust and the arrow kept moving forward, but I was still moving forward too due to
momentum shrugs literally unplayable…)
I have to amend here, I was mistaken. The arrow really switched to backwards when the momentum is gone and you fly reverski.
I stand corrected - this one is really nice (y)
 
And it is laughable that people actually believe broken and sub-par work is acceptable. Most jobs (in MURICA) fire folks that turn out broke stuff. Participation trophies for Everyone!

498-4982218_black-emoticon-twitch-kappa-emote-no-background-hd.png

I'm not sure if we Americans get to lecture anybody on dysfunctionality these days...
 
Last edited:
Back
Top Bottom