Prinz Eugn
Member
That's not what Frank and others have said at all though. They said everything was hunky dory in the internal tests and it was only when released to the public that the problems arose. My point is, a deadline is only unrealistic depending on when development starts. If they started working on MCC in, say, 2011 then a Novemeber 2014 launch is very realistic. Seeing as nobody here knows when the development started, I think it's fair to challenge Ryn's statement.
That's what they've said. There is no way, with the internal politics of any organization like Microsoft or any major corporation, that we are going to get anything but a vague blame-less response, that "no one could have forseen". Someone made a bad call, and we are probably not going to find out for years who did, if ever. I can't blame Frankie or anyone else at 343i for not wanting to get fired over this, but it takes a considerable amount of naivete to take them at their word.
The sort of test environment you would need to miss the kind of un-subtle bugs MCC had is basically unimaginable. Any human with eyes and/or ears, plus an off-the-shelf Xbox One, is all you needed to tell you the game was not ready for prime time.
The deadline was unrealistic in the sense that regardless of when they started, what we got needed more development time- several months if the patches to date are anything to go by. It makes more sense that they started ridiculously late, than Microsoft, with all its resources available, and with this being one of their flagship franchises, spent several years on it and gave us MCC.