for example- according to luke timmens (bungie engineer) when halo reach was shown to gameinformer it was in a public alpha state while internally they where far beyond that in content. like wise when the halo reach public beta came out the studio was at internal delta. The nomenclature can be confusing but to be honest i wouldn't worry this time last year Halo Reach was at the same state of completion and it is fantastic, it also released months earlier in September...
i would say Beth is right on track
It would make little sense for them to release really old screenshots if you ask me. You want your game to look good on its first appearance to the public.
As for my opinion on the topic.. being pre-alpha or after-omega or whatever doesn't really concern me. They set a date. If they think they can do it, who am I to argue? They know how much there is to be done, not me. But even if they don't make it in time, I still wont mind, so..
As for my opinion on the topic.. being pre-alpha or after-omega or whatever doesn't really concern me. They set a date. If they think they can do it, who am I to argue? They know how much there is to be done, not me. But even if they don't make it in time, I still wont mind, so..
thats another thing GI played a demo so they needed to have the most stable build possible for them, this means they probably played a version of Skyrim a month or 2 old so those screens are almost 5 months old. You cant have screenshots of a build that isnt stable it would look worse than the old stable builds. To finalize a build you have to reach a certain content point then you move on from there its the same as writing a basic program. The smart way is to implement something to the code environment then compile and recursively test before adding more rinse and repeat. On a game this process is alot more complicated as compiling could take days and then bugs occur