Originally Posted by lattyware
They won't be using uncompressed sound.
The cut scenes are pre-rendered. The best example of this, that I can think of, is Halo 3. Halo 3 savegames are simply saves of what happens (player moves left, shoots, etc..), not video recordings. The files are only a couple of megabytes.
Storing a series of instructions uses very little space in comparison to storing thousands of frames of video.
A video is literally a series of images, displayed fast after each other. Each frame takes up an amount of space.
With a cut scene rendered in real-time, they literally only need some numbers and instructions to make the characters do what they want, and it's done. Textures are re-used throughout the game, each individual thing does not have a new texture.
As to places that are not in the game, they still make the map, you just never play in it. It's just there for the cut scene.
Overall, it'll take drastically less space. It's similar to storing an audio file of a program synthesizing speech, as opposed to storing the text, and putting it into a synthesizer. The audio file will be a megabyte or so, the text document will be a hundred or so kilobytes.
I think your confused. Pre-rendered is, its already been rendered and saved as a video file. Which is not the same as your Halo example.
The sound files will still be very large, since you can't just save some instructions for audio, but the rest will be rendered real-time to save on space and since the newer gen systems have enough power to produce beautiful CG movies in real-time.
Originally Posted by IcedEarth
Could you explain that to me in a little more detail please Dillard?
I understand it won't take up as much space because it doesn't have to store the cut scenes as a whole.
But it would still have to store everything else, from character movement to sound and all instructions for the cut scene. How would one 90 minute piece take up so little space regardless of textures? Especially when they are using uncompressed sound.
And also, won't there be parts in the cut scenes that you *may* not visit in-game. Which would mean those have to be stored and pre-rendered? Maybe i am looking at it wrong. Just need a bit of a clarification how this real time rendering differs from pre-rendering. It seems to me that all information and instructions for real time render would still have to be stored
Anyways, i have no objections to 90 minute cut scenes as long as they are entertaining and descriptive.
Well, the textures are already there no matter what, since they are needed for gameplay, same with the enviroments etc. So if its rendered in real-time, all that needs to be saved is the audio, and just a few commands about how the characters move. The movement is just a script of co-ordinates so it is relatively small.
And even if its a environment not visited in-game. A few textures and some co-ordinate geometry is still much less data then 90 minutes @ 30 or 60 fps.Edited by pheoxs - 5/24/08 at 12:43pm