[Video] January update, was this what we ASKED?! & Fleet carrier delay...

This patch is utter trash. I have a high end PC and never before have I EVER had issues with stuttering. Patch my game today and start playing - stuttering all over the place especially when jumping into system. This game is becoming more and more of nightmare as time goes on unfortunately which is a real shame. The whole idea of this patch was to FIX bugs not create a ton of others..............
Damn right, people should be fired for this patch, they should never work in the industry again. We, the customers have RIGHTS, we demand perfection of everything, no half measures, no excuses, everything perfect for everyone - even if what I want is diametrically opposite to what you want - both options need to be perfect. No excuses, no patch to fix a patch, no hollow promises, everything needs to be perfect, on or before the promised time, free to the user and works 100% perfectly on every variation of PC, every iteration of PlayStation, every edition of X-Box and under every type of internet connection known to humanity.

Yes, what I wrote was just a load of biowaste, line up to start calling me names ...
 
I think you're missing my point. My point was betas happening and new bugs appearing regardless despite the betas.

That wasnt a beta... yes they called it a beta but:

1) after a beta you do not touch the code again before the release... or you touch it and then do a second beta... FDEV clearly touched the code afer the beta and before the release.
2) What they called a beta was really a product demo / focus group.
 
I think you might be on to something with your assertion that Fleet Carriers were kind of thrown out there at the expo.

But I don't think they were created for the expo.

I think Fleet Carriers might never have been intended to be space winnebagos, but instead were meant to be flyable capital ships that required multiple people to crew them to be flown. This would have been targeted as New Era stuff.

So basically, squadron ships. Starship Enterprise type stuff. But maybe somewhere along the way this was determined to be too difficult and perhaps too niche and therefore canceled, which resulted in them being announced at the Expo as something else.

However, time passes, and rather than release something that might be perceived as lacklustre; and perhaps also wheels have been turning behind the scenes and intent is now to try to capture more of this original "New Era"-style vision for them, or lay a foundation that could possibly be realized later post-New Era-1, they are being witheld.

I gotta say though. If you were Frontier, and you had this major update cooking, and you were looking around and saw you had currently the only space game (I don't think Bethesda's thing is ready), aside from NMS, which already kind of had its day (but could very well possibly do the re-release thing too I guess), and you were staring at that future console-generation launch, you would want to hold it all for that, too. In fact you'd probably feel stupid for not doing that.
 
That wasnt a beta... yes they called it a beta but:

1) after a beta you do not touch the code again before the release... or you touch it and then do a second beta... FDEV clearly touched the code afer the beta and before the release.
2) What they called a beta was really a product demo / focus group.

So, the betas we paid for as backers or some people paid $10 to access, were not actually betas? That's false advertising then! Quick, someone start a refund sub!
 
So, the betas we paid for as backers or some people paid $10 to access, were not actually betas? That's false advertising then! Quick, someone start a refund sub!

Thats not what the poster said. A beta should be for testing, you find things and then test again to see if they are gone. The last beta had issues that were new and not in the test.
 
Bug fixes and mending things was very much needed! Obviously a lot of the current features are required for fleet carriers and 2020 addon to work. No complaints here! Would be nice to get a small amount of content leading up to carriers maybe a new ship or new mission type poss?
 
Thats not what the poster said. A beta should be for testing, you find things and then test again to see if they are gone. The last beta had issues that were new and not in the test.
But wouldn't that end up in a never ending cycle of Beta releases because (especially this community) nothing will be perfect, there will always be something someone will not like so the BETA will always get changed. And if you change a Beta then you need to re-issue the Beta to test it, otherwise what is the use of issuing a Beta right!

Hmm just think I discovered C. Roberts business plan ….
 
But wouldn't that end up in a never ending cycle of Beta releases because (especially this community) nothing will be perfect, there will always be something someone will not like so the BETA will always get changed. And if you change a Beta then you need to re-issue the Beta to test it, otherwise what is the use of issuing a Beta right!

Hmm just think I discovered C. Roberts business plan ….

It is up to FD to call time but what happened to the two or three beta phases of the past? All of the nasty problems are easily spotted by people- within minutes people had spotted SC stuttering, and had identified all the problems in Septembers patch. You test on one build and then when you are happy you release it. You do not fuse that beta with a new, untested branch.
 
I think you might be on to something with your assertion that Fleet Carriers were kind of thrown out there at the expo.

But I don't think they were created for the expo.

I think Fleet Carriers might never have been intended to be space winnebagos, but instead were meant to be flyable capital ships that required multiple people to crew them to be flown. This would have been targeted as New Era stuff.

So basically, squadron ships. Starship Enterprise type stuff. But maybe somewhere along the way this was determined to be too difficult and perhaps too niche and therefore canceled, which resulted in them being announced at the Expo as something else.

However, time passes, and rather than release something that might be perceived as lacklustre; and perhaps also wheels have been turning behind the scenes and intent is now to try to capture more of this original "New Era"-style vision for them, or lay a foundation that could possibly be realized later post-New Era-1, they are being witheld.

I gotta say though. If you were Frontier, and you had this major update cooking, and you were looking around and saw you had currently the only space game (I don't think Bethesda's thing is ready), aside from NMS, which already kind of had its day (but could very well possibly do the re-release thing too I guess), and you were staring at that future console-generation launch, you would want to hold it all for that, too. In fact you'd probably feel stupid for not doing that.

Flyable carriers was never a thing, executive control as in jump to system X.
 
It is up to FD to call time but what happened to the two or three beta phases of the past? All of the nasty problems are easily spotted by people- within minutes people had spotted SC stuttering, and had identified all the problems in Septembers patch. You test on one build and then when you are happy you release it. You do not fuse that beta with a new, untested branch.
So how many times do you test that ONE build, until what percentage of the player group say they are happy? Or do you rely on the influencers to give their tick of approval, or is the voices on Reddit say go or try again? And who does FD listen to, which specific focus group gets precedence, gets their voice heard above all others?
 
So how many times do you test that ONE build, until what percentage of the player group say they are happy? Or do you rely on the influencers to give their tick of approval, or is the voices on Reddit say go or try again? And who does FD listen to, which specific focus group gets precedence, gets their voice heard above all others?

You test, look at feedback on performance (i.e. what did people find wrong / not working) and once the major problems and listed fixes seem to be fixed in follow up feedback / build then you release. You don't release yet more untested code because you are then undoing your testing phase and making it redundant. The stutter is an excellent example of this- it would have been instantly commented on, but was not because it was a new problem introduced in a new build. I found severe (i.e. CZ breaking) bugs in my testing, I can't know until live if they sorted them out.

And who does FD listen to, which specific focus group gets precedence, gets their voice heard above all others?

The official feedback area, i.e here: https://forums.frontier.co.uk/forums/january-update-beta.409/
 
Lets call it 'Beta-Bashing'. I mock it, because it's true. I can't remember a patch from any game, that went off without a few hot-fix type situations. Having a bone to pick and a axe to grind has a dissatisfying ring to it.

Outrage for the outrage god. Oh, yeah and, never satisfied.
Yep, the morally outraged, the 'I don't know what I am upset about but I have to be upset otherwise nobody will take me seriously' crowd.

Not sure of your vintage Commander but I would love to see some here have to deal with what some of us old timers had to put up with regarding fixes to games. Way back when, we would buy a game and cross our fingers it would work the first time. If it did, you smiled and did a little happy dance. If it worked 'most' of the time, you smiled, put up with the bad bits and continued playing. If it didn't work at all you hoped like hell the shop had a refund policy on software because a lot didn't due to piracy issues.

If there was a problem, you prayed that the developer was important enough to get their patch included in one of the various computer game magazines that were popular back then. So you waited for each monthly issue to drop, hoping that your game was listed on the cover. If you were really lucky, the patch was in the form of a file included on the disk attached to the magazine (if Rob Stevens*, the newsagent son hadn't stolen the damn disk yet, god I hated that kid). If not, the fix was inside the magazine, normally several pages of assembly code to type in and hope beyond all hope that the game publisher got the code right, the magazine publisher printed all the code, in the right order and didn't leave a segment out to put another advertisement in and that your assembly language program was compatible. If all worked according to play, you got to fix your game several months after buying - if you got to fix it at all.

Yeah, it is terrible there are problems with a patch that may be fixed within 24 hours, the world is going to end !

*Not his real name of course
 

Viajero

Volunteer Moderator
But wouldn't that end up in a never ending cycle of Beta releases because (especially this community) nothing will be perfect, there will always be something someone will not like so the BETA will always get changed. And if you change a Beta then you need to re-issue the Beta to test it, otherwise what is the use of issuing a Beta right!

Hmm just think I discovered C. Roberts business plan ….
Precisely. Resources are not unlimited. At some point a developer or project manager needs to decide to launch its product or service, warts and all.
 
Precisely. Resources are not unlimited. At some point a developer or project manager needs to decide to launch its product or service, warts and all.
You recognise that, I recognise that but others are under the impression that FD must continue to issue beta's until their specific problem/concern is fixed. After that they just don't care!
 
You recognise that, I recognise that but others are under the impression that FD must continue to issue beta's until their specific problem/concern is fixed. After that they just don't care!

I know the difference between actual fixed testing and lip service.
 

Viajero

Volunteer Moderator
Then why is it the beta that was tested was not the release candidate? The beta had fixed goals, you then need one more test to make sure they are gone and release. You then repeat for the second patch coming this year.
That, I am afraid, is precisely the prerogative of the developer. They have full control on their own development process. Their money and resources, their game, their rules. By all accounts, in addition to the stutter, many bugs have been actually addressed aswell. If they want to do an open beta and then add code to it internally it is their choice to make and their risks to take.

You are of course free to judge the result as a gamer, and as a consumer you are fully free to act accordingly going forward. Such is the magic of the free market.
 
Back
Top Bottom