Newsletter suggests that we are not close to launch.

Status
Thread Closed: Not open for further replies.
They want to release 3.0 for both pc and platform on the same day. If you remember the platform version wasnt ready yet. Plus the bug fixes. It will be some time.
 
Last edited:
I don't see anything in that Newsletter that implies we are a long way away from launch, nor close to one lol.

What I do see is this silly error ...

TYPE-10 DEFENDER SQUADRON PACK

Form a wing and fight together in a squad of uniformed heavy fighters with these Military Stripe paint jobs for the Vulture.


Available in six colours, this paint pack is available on the Frontier Store for PCCommanders and the digital store for console Commanders.

Does anyone read the Newsletter before release ??? :rolleyes:
 
Last edited:
Actually, I'm going to give them some points for how they're handling this release. Normally they have a Beta, it finishes, and 3 days - week later it goes live, often without any of the things fixed that were discovered to be broken in the Beta. This time we had a Beta, it's done, and now they're working on polishing it up based on the feedback/testing. So that is an improvement.

A bigger improvement would have been to not shut the Beta down, at least not completely. Maybe shut it down for a week or two while they put major changes in, then bring it back up again for us to continue testing, see if it all (or mostly checks out) and then release it to live.


Personally, I'm conflicted on this release - normally I would want them to take as much time as they need to polish it up. But in this case, I'm very, VERY eager for the new mat/data inventory system. Also going through Chieftain withdrawal... ;)

Still, I'd say the way they are handling this release is better than what they did with 2.1, 2.2, 2.3, and 2.4.

well I guess you should not make this conclusion before you know how the release version actually looks ;)
 
If it isn't out on March 1st, then you can start worrying about a delay. I saw nothing in that sentence in the Newsletter that would indicate a slip beyond the usual 2-3 weeks after a beta closes before we get the actual release.
 
Also, this is just chapter 1 as there are supposed to be a few more chapters to the end of this year of Beyond.

This. The coming year should see the release of two major updates, two minor updates, and at least one paid expansion.

That's a release every ten weeks on average. FDev need to get 3.0 out quickly so that they can move onto the next release. I originally thought the release date would be March 1, but on further reflection I wouldn't be surprised if it dropped next week.
 
I'd doubt it'd be as long as horizons. I think a major reason it dragged out longer was unforeseen extra challenges due to the ps4 port. Everytime they had a beta, the section update release was soon after as in no more than a month. It was the time that dragged before a 2.x beta announcement and its testing period, not the time after a beta until section release. Also, this is just chapter 1 as there are supposed to be a few more chapters to the end of this year of Beyond.

From what I can tell.it was nothing to.do with the PS4 port. Most of the code will be the same anyway and they have a separate team that works on the Xbox and PS4 parts. The biggest issue was probably getting stuff to work on 32bit and 64bit machines. Now that the 32bit is gone hopefully things will speed up a bit.
 
Yo,

I always enjoy the "let them take their time" threads. Let them rush, I dabbled in the beta, I'm looking forward to it. So much so, that I'm not going back to 2.4. So let them rush. They shouldn't have released any type of beta if they weren't ready for a launch.

Let them rush because it's going to be released with balancing issues and bugs! The quicker we get to it, the better (hopefully) it will be. Also, we will still see 90% of the posters here complain, whine, cry, yell, insult and kiss up. So, I'd rather get that all out of the way as well.

Rush it! Get it out the door!

Thanks
 
They could at least up the material limits in the live game while we wait for the release.. Or the next ice age, whichever comes first.
 
Hasn't the release come three weeks or so after the betas this year?

Some people are so melodramatic around here.

If they release right immediately after the beta is bad, because they don't fix. If they release after a longer time it is bad, because then they introduce new bugs with the new code. The point is complaining, didn't you get the memo?
 

He had it right.

There is nothing more enraging as a developer than being told, after a beta test, to tweak some stuff *before* a live release with no further testing inbetween.

You end up with unforseen bugs in production every time, only now it's not QA filing bug reports, it's the people playing your games having a fit.
 
the problem is, they're going to make a ton of additional changes that span from bugfixes to feature changes _AFTER_ the beta test.

This is why everyone knows ED's beta test periods are a joke. The entire point is to test the product before release. You completely miss the entire point of a beta test when you go and make additional changes after the final beta test.

This man knows what he's talking about... I worked at a company that used to make random changes to their product at the producer's whim AFTER the beta was finished. As you can imagine, the products were littered with regressions and completely new bugs, causing numerous (valid) complaints by the customers who effectively received untested "final" software.

I don't work for them any more.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom