Failure Developments at it again

I am curious to understand the change for VPN usage... I see what you have done but don t understand the reason.
 
Always here on forum for damage control I see....
Still making pointless and random accusations I see. Sorry that being reasonable somehow hurts your feelings.

Anyway, FD doesn t test their changes, it is not something new. It just their coding is getting worse...
Maybe, maybe not. It's possible that some of the issues weren't present in the development builds because they sound like server issues. Which also explains how something seemingly unrelated breaks something else. Doesn't stop FDEV from being pretty good at implementing bugs, don't know if it's due to complexity, incompetence or lack of testing though. Pretty sure we can rule out bad luck since there seems to be a pattern... ;)
 
Always here on forum for damage control I see....

Anyway, FD doesn t test their changes, it is not something new. It just their coding is getting worse...
How dare you, sir. Of course they test their changes. They release the changes to their customers and wait for us to . That's testing done SMART. If they don't have to make sure their product ships in a competent state, QA guys can spend their time psychoanalyzing their client base and pontificating about their prospects for a career as a coder.
 
Considering that the things that are broken did not appear to have any relationship to the new features, one really does have to wonder...How bad is their code that something can go this wrong...

I'm sure there are issues in the code considering how big the codebase must be. There is probably lots of spaghetti code in there.

But i guess the main problems don't come from the code directly but from their processes for the build system. It would certainly explain why regressions are common and how things that were apparently not touched get broken. It only takes one dev with an unstable or broken bit of code on their local repository merging it with the master to break a previously working feature.
 
I'm sure there are issues in the code considering how big the codebase must be. There is probably lots of spaghetti code in there.

But i guess the main problems don't come from the code directly but from their processes for the build system. It would certainly explain why regressions are common and how things that were apparently not touched get broken. It only takes one dev with an unstable or broken bit of code on their local repository merging it with the master to break a previously working feature.
As said above, I wouldn't be surprised if the issue with displaying engineered, stored modules correctly is somehow related to the servers. Information about our module storage and engineering is server side. Considering the bug goes away as soon as we install the modules it could just be a transaction error.
 
So happy new snowflake players can fly through lighted circles while veterans can't mine one ton of ore. Perhaps a patch that adds things without breaking stuff that already works? Edit: melted the snowflake for the snowflakes

giphy.gif
 
Last edited:
This was neither major or bigger minor update it was using content that was already in game including arc's ( just fronier points renamed) all they done was move a few things...
You got absolutely no idea what they done behind the scenes to get ready for future updates.
 
I've been playing this game for years now but have only been active on the forums (lurking and then registering) for a couple of months. I have to say that some of the criticisms on here following the update have been fine (it would be disingenuous to pretend things haven't gone wrong) but others have gone way over the top.

These things will get sorted. There's a team of dedicated developers working their backsides off so we can spend a few hours escaping from reality for our own entertainment and a team of dedicated community managers having to deal with the criticisms. Let's not lose sight of the fact that these are people trying their hardest to do their jobs.

ps I do realise I sound proper sanctimonious in this post
 
Im glad to see no one is overreacting.

Yep, because we got used to these things over the years (which doesn't make it better ofc). IMHO the introduction of ARX required major internal changes which lead to most of the problems atm. And whenever they touch the UI, uh oh. VR didn't get tested at all again ofc.

That said, the worst update I remember was the 3.3 one which left little hope for betterment at the time it came out. But then, they did fix about everything critical in two or three patches. Just two days ago I thought 3.3 in its April release has developed into the best ED version ever, so here's hope this will also be true for the September version in a few weeks. We just have to be patient, it has always been so.

O7,
🙃
 
My guess, given that most the problems seem to be database related, that databases for whatever reason didn't update or the reuploading of all data didn't take. May be the save they use was corrupted, may be the upload was interrupted, may be the game is trying obtain the data from a database that doesn't exist anymore or perhaps some mistype the name of the database they were trying to receive the data from.
 
I dont think Frontier or anyone else finds it acceptable but its the nature of the beast when dealing with mmo game with a million moving parts.

I will accept though that buggy updates seem to be the norm now and it should be communicated by FDev that they will do better in the future instead of coming out with another mealy-mouthed apology.
They won't communicate anything - they find it acceptable. :)
 
Back
Top Bottom