Le 01/04/2011 14:47, Warp a écrit :
> scott <sco### [at] scottcom> wrote:
>>>> Why should loading the scenery from disc slow down the game?
>>>
>>>    Odd question. Because the disc is really, really slow?
> 
>> The CPU and GPU can carry on working whilst a file is loading, you don't 
>> have to block everything whilst the file loads (thankfully!).
> 
>   It's hard to work on something that has not been loaded.
> 
Right.
But you can usually split the scenery in areas. You only need the
current area and its neighbour in memory.
New area could be loaded when changing the list of neighbour (in fact,
you could just keep the current area, its neighbour and its neighbour's
neighbour. When the neighbour become current, there is still plenty of
works for CPU & GPU while loading the new neighbour's neighbours.)

That's the difference between games that put you in a tunnel/corridor,
and the ones which don't: the former only manage a 1D of areas, usually
as a basic list... the latter is more complex.

-- 
Software is like dirt - it costs time and money to change it and move it
around.

Just because you can't see it, it doesn't weigh anything,
and you can't drill a hole in it and stick a rivet into it doesn't mean
it's free.

Post a reply to this message