I know what he is saying, and i know it will be slower, but i dont think it will be that slow(depending how one solve it), and if i have to make a shoise, to ether load graphic for 5sec and have a feazed lockdown the hole time(showing some static booring looading screen), or load for 7-8sec and be able to do fully graphical representation of what is loaded and how, i think i whod prefer that, extra so if i want some sort of graphical consol showing evrything loaded by engine and still be able to render it smothly.
shure, this solution might not be soutibel for all types of massive data, but im shure it whod be usable still.
i dont care mutch about performence during a loading screen, what i realy want it to know the system havent locked down or freazed, somthing that might be hard to tell with a static loading screen, shure one can do that after each LoadImage/sound or whatever, but it still feals a bit static to me.
shure, this solution might not be soutibel for all types of massive data, but im shure it whod be usable still.
i dont care mutch about performence during a loading screen, what i realy want it to know the system havent locked down or freazed, somthing that might be hard to tell with a static loading screen, shure one can do that after each LoadImage/sound or whatever, but it still feals a bit static to me.