Indeed. The developers broke the cardinal rule of beta testing: "only fix bugs, don't add new functionality". And then they didn't do a second round of beta testing to see if there were any widespread issues introduced by the fixes done to fix the bugs found during the first beta test. I hope this is a lesson that they take to heart: whenever you make drastic changes to functionality, do a large scale alpha test and only fix bugs found. Then do a beta test to find the bugs introduced by the fixes for bugs found in the alpha test and finally do a gamma test for the fixes for bugs found in the beta test. NEVER introduce new functionality after the alpha test phase, or if you do start a new alpha test!
ANNOUNCEMENT January Update - Patch 1 Announcement
Indeed. The developers broke the cardinal rule of beta testing: "only fix bugs, don't add new functionality". And then they didn't do a second round of beta testing to see if there were any widespread issues introduced by the fixes done to fix the bugs found during the first beta test. I hope this is a lesson that they take to heart: whenever you make drastic changes to functionality, do a large scale alpha test and only fix bugs found. Then do a beta test to find the bugs introduced by the fixes for bugs found in the alpha test and finally do a gamma test for the fixes for bugs found in the beta test. NEVER introduce new functionality after the alpha test phase, or if you do start a new alpha test!
That's very true - but after developing a game for weeks most people will want to play something else in their own time.
Something where they don't know exactly how it works, and aren't going to be presented with that little bit of animation they were never quite satisfied with every time they open a menu that no-one else even knows isn't supposed to look like that.
I don't have any stutter issues but i explore in Acheron
I didnt see the stuttering in beta either, but saw it within minutes of playing today, after my 2nd jump. I would definitely have noticed this bug if the beta had had it.
Having the beta back was welcome but it really it was a half arsed beta at best. And I dont think they've ever used their whole for beta testing.
The final stage of the beta test should be to beta test the actual code that is going live but clearly FDev are modifying it between beta and release. This should stop as it's bad QA.
Paige Harvey
P
Instancing is super bad, some people just popping up and disappearing when traveling in SC.
You see them all the time with status [NOW] in history but in social they are randomly blinking.
After some time I got this twice:
Hello Commander, have you reported these issues on the Issue Tracker? If not, please do so we can investigate properly! https://issues.frontierstore.net
Paige Harvey
P
Hey Commander, this is an issue we're aware of and currently looking into!
Then after the last phase of testing announce when the new software will be released.
Unfortunately the real world is rarely this way due to customers wanting new stuff now, target dates and financial issues as well as many other things.
Sadly I have to agree. The deal Frontier gave us was that FCs will be delayed by half a year but for that they will double down on bug fixing and beta testing. Unfortunately the December beta didn't feel sincere, more like a token. Just the Thanksgiving weekend was way too short to really test everything, especially since there was new BGS stuff and afaik there was no accelerated "tick".
Furthermore, Frontier has a history of doing this: "Currently the game works like this (A), we'd like you to test option B." Then after a period of silence: "We've decided to release option C."
In the case of the FSS I think they went for the right compromise and people are happy with it, but the point is that it is untested again. The beta test loses a lot of value if the released version turns out to be something completely different again.
And (DANGER - speculation ahead) I don't think the stuttering was due to server load. It seems to me that was just an error in programming. I thought the intended behavior was that the FSS resolves the planet it is currently scanning, not that all planets immediately get resolved when entering the system.
Sorry for the rant.
Please no!!! Do not fix that!!! This is a nice change!!! I do want endless non-stop cz! This will help pass massacre 90 enemies missions in cz faster!!!111
They have not solved the black rectangle in the chat, nor have they fixed the offset icons in the muti crew menu...
We have an error since 2016, the year the class 4 multichannels were introduced and the gimballed have an error, they use the fixed assembly.
We have an error since 2016, the year the class 4 multichannels were introduced and the gimballed have an error, they use the fixed assembly.
Ooh, that takes me back to when Ashley Barley was community manager and they were using Beta 2 and similar as release version strings shown on the overlay instead of 0.6.2 as something meaningful for bugreporting. I think I posted something like yours then, too.
Oh, I see the new anti-gank feature has been introducedLOL that must be aggresive targoid, Now I get it whenever I do interdiction on cmdr
4 this in a row. Congratulation Frontier, SUPERB patch!
StefanOS
Volunteer Moderator
I really hope that this is not the new way for more realistic pricing for comodities ....
We had a beta of less than a week, the 'bits' I tested were actually good improvements in general, particularly the 'bugged' Neutron/White Dwarf cones which I thought were much nicer than the live ones...
What I don't understand is why, after having a beta, 'new' features were added to the very 'bit' we were testing (even though the change is overall better) and introduced some 'unforseen consequences' to the 'tested' image.
Oh well, I'l look forward to seeing what today's fix brings
What I don't understand is why, after having a beta, 'new' features were added to the very 'bit' we were testing (even though the change is overall better) and introduced some 'unforseen consequences' to the 'tested' image.
Oh well, I'l look forward to seeing what today's fix brings
Nope.
Those issues tend to fix themselves to a degree a few days or week(s) after any bigger update, after "everybody" has downloaded the updates and "many" dormant users have put their E: D play on hold again.
In other words: the servers are hammered with crazy amount of traffic, you'll be bound to have more disconnects & lag than usual until the traffic returns to "normal" levels.
This just implies that we do not want beta.We had a beta of less than a week, the 'bits' I tested were actually good improvements in general, particularly the 'bugged' Neutron/White Dwarf cones which I thought were much nicer than the live ones...
What I don't understand is why, after having a beta, 'new' features were added to the very 'bit' we were testing (even though the change is overall better) and introduced some 'unforseen consequences' to the 'tested' image.
Oh well, I'l look forward to seeing what today's fix brings
We do expect quality product.
Obviously not everything can be tested internally by product owner.
Idea of beta does not fit the goals properly because revealed issues must be tested once fixed. One more beta required?.. Oh common, this way we'll deploy one change for year.
Eventually I am ok with testing things in production without beta.
Console players are second class citizens? Ok. I will remember this.
PC update is available. 17MB.
It just always will be next January.