Failure Developments at it again

This is all perfectly normal. Some minor bugs occur, people claim the sky is falling. I say cool your boots a bit there old chum and do something else for a bit if it bothers you.

Where I work this would make a rollback necessary within 5 minutes of detection. A hard rollback with DB and code and everything.
After that a
message to all users with details, a meeting call and further planning.

Bugs happen. But there are
development, testing, prelive and final approvement environments in place to sieve the gravest bugs out - FOUR stages before going live - and in the gaming industry you can add private and public betas to add more specific tests. All with a full regression testset, all with a full new feature testset.
 
Ok lets look at this logically.

These events have all happened...
FDeV charge people a lot for the privilege of .Beta testing their product...
FDeV charge people a little for the privilege of .Beta testing their product...
FDeV charge people nothing for the privilege of .Beta testing their product...
FDeV Dont do Beta testing of their product...

Same disastrous result in all cases...have you spotted the common denominator in all this yet FDEV ?

I still can't understand how to try an incomplete videogame became a privilege :(
 
Where I work this would make a rollback necessary within 5 minutes of detection. A hard rollback with DB and code and everything.
After that a
message to all users with details, a meeting call and further planning.

Bugs happen. But there are
development, testing, prelive and final approvement environments in place to sieve the gravest bugs out - FOUR stages before going live - and in the gaming industry you can add private and public betas to add more specific tests. All with a full regression testset, all with a full new feature testset.

I'm not in the software industry .....and I don't believe you, that this actually happens.
 
Where I work this would make a rollback necessary within 5 minutes of detection. A hard rollback with DB and code and everything.
After that a
message to all users with details, a meeting call and further planning.

Bugs happen. But there are
development, testing, prelive and final approvement environments in place to sieve the gravest bugs out - FOUR stages before going live - and in the gaming industry you can add private and public betas to add more specific tests. All with a full regression testset, all with a full new feature testset.
Ok now make it so i can read it without having a stroke
 
Have folk not learned anything?
After any major (or bigger minor) patch, things tend to be broken in game. Some because of the patch (and the bugs in it, both old and new), some because the servers are being hammered by thousands of downloads & concurrent players, player numbers being way above regular.
If the 'things are more than usual broken' state of game irks you bad, give it a week or two rest - in that time a couple of fixes will have been applied and highest user peak will have abated.
Oh, if you absolutely must play all the time, first few days have much less problems in solo in my experience. Rubberbanding & many other instancing related issues aren't present then.
I only play in solo ...so thats not a fix.
 
By having to pay for testing. Instead of being paid. I know, the mental bending over is quite hilarious, but there we are: People pay now money to debug someone else's software, it's stupid but what can you do.

And these are the results of these methods...makes you think doesn't it...
If it were me; I would be asking is it really worth putting our reputation on the line by allowing people we do not know to test our software?

nb. it could be a time pressure issue that creates these problems, but then they are in control of their own clock
 
Ok now make it so i can read it without having a stroke

i guess the arcane typography is because what he's saying is just generally accepted good business practice, but seems to look like alien stuff or black magic for some diehards around here :ROFLMAO:
 
By having to pay for testing. Instead of being paid. I know, the mental bending over is quite hilarious, but there we are: People pay now money to debug someone else's software, it's stupid but what can you do.

stop doing it, and don´t create alternate pages or applications to make your job easier. I mean, to use inara to know how many secondary modules my ship has? the elite world is really crazy,although I love him
 
Lets be honest at the moment frontier are no better than the above mentioned thought better of frontier but their no different!

I think this fine person put it best:

Edit: forgot the
new text format!

I'm not a defender of FD, far from it but there is a world of difference between what FD are trying to do with the store and ARX and what that other game space game company are and have done for years which I consider nothing more than an elaborate scam. IMO of course.
 
Last edited:
i guess the arcane typography is because what he's saying is just generally accepted good business practice, but seems to look like alien stuff or black magic for some diehards around here :ROFLMAO:

Actually...

the weird highlighting is a response to FD's new STORE button in the station menu

For some it's immersion breaking, for others the blue button is just too prominent.
Also some get this impression:
Source: https://www.youtube.com/embed/ciPqHMBSNwk


And I agree.
 
Not in the programming industry here.
But in my job.
We have checkups before we start on the project. and we do finalizing tests before we call it complete.

plus. if we change a module. we do checklists of tests on that system and systems that are critical to it.

It is just common sense, if others depend on what you are doing.

(ps, also planing on waiting til 2020 to play again)
 
Is this an excuse for releasing a game with in-your-face broken features, especially headline features, even those that are directed at new players? What kind of image does that create of FDev?


It is one thing to make a mistake, but releasing the built anyway, fully aware that your customers will waste their time due to that?
Often not the programmer, we tell our bosses something isn't ready but often launching on time is more is more important than launching something that is working.
 
Back
Top Bottom