Tsakali wrote:k the obvious question is why would they release a shitty beta that is known to have issues that are supposedly already fixed?
It's simple to answer that: Creating any sort of release for a game takes time. It takes
a lot of time. People always assume that, for instance, demos of a game can be released "just like that" [imagine someone snapping his fingers here] but it's not. I guess that at some point they made a snapshot of the codebase and assets and built a release out of that. While they were doing that, the rest of the development team continued fixing bugs and issues which didn't end up in the beta code because that would delay the beta again.
Tsakali wrote:Ignoring that, why would they not release and continue to update a comprehensive list of KNOWN and already RESOLVED issues that plague the beta? Seems to me most of the frustration could be avoided in this way. Looks like there are morons on both sides of this.
Creating updates and patches takes time as well and I bet they'd rather spend that time actually fixing bugs rather than making patches. The goal of a beta is not to deliver a smooth experience, it is to identify the problems that prohibit players from getting a smooth experience. If you've detected them, there's no need to fix them in the beta because that's not what the beta is for.
On the other hand, players seem to be complaining about such serious show stopper bugs that it could be argued that an updated beta that irons out the most obvious problems would allow players to dig deeper into the game and find more obscure bugs more easily.
The third thing here is that, especially with the whole MW3 vs BF3 thing going on, EA and DICE can't really afford such bad exposure. I think some suit at EA thought a public beta would be a good way to promote the game, so I imagine some people at EA thought of this as a glorified demo. If so, then that seriously turned against them and bit them in the ass.