Justin Couch wrote: > Unfortunately, for the majority of the applications that have to be > general, there is no real ability to optimise the file format before the > application gets to display it. I have to load a generalised DTED or DEM > file. They don't have any of the luxury of preprocessing to build grids. > In fact, some files are many tens of megabytes in size.
I think that this could be a problem of how much time this preprocessing takes. If we are talking about quake-like stuff, BSP, PVS etc, with some recomputations taking up 10+h, this is out of question. But if it could be done, let's say, in 5 seconds ? This would mean 5 seconds delay after loading new data/piece of terrain, with some 'recompute' progress bar, but it would speed execution later. As for the many-megabytes height grids, this is of course out of question. Unless you split them in smaller ones... So my question is, how much time, does this preparation take ? Certainly too much to do it dynamically between frames, but is it also too lengthy to do it on level/area load/switch ? Artur =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
